What output files are generated?
A finalized run produces per-slide HTML ZIPs, a shared resources ZIP, and a Vault Loader CSV aligned with configured manifest fields.
Frequently Asked QuestionsFAQ
Quick answers for the most common CLM Forge workflow questions.
I have an interactive presentation with links, embedded videos, and hidden slides (popups/extra slides). Will these be converted automatically?
Yes, in most cases. The converter extracts PPTX links/hotspots and embedded video assets (MP4/H.264), and it handles hidden slides through PPTX+PDF mapping. Important caveats: hidden slides must also be included in the exported PDF to render, and external (non-embedded) video links are not packaged automatically.
Do you support different slide formats/aspect ratios?
The pipeline preserves page aspect ratio from the uploaded deck/PDF, so any common formats like 4:3 and 16:9 can be processed. Best results require PPTX and PDF exported from the same source deck.
Why do I need to upload both PPTX and PDF?
The PDF is used for browser rendering of preview images, while the PPTX is used for extraction of structure and metadata (for example hotspots, hidden slides, and navigation data). Both are required for a complete finalize step and they need to share the same amount of pages/content. I.e. unhide any hidden slides before creating the PDF.
What content quality/resolution is used?
Preview generation renders pages at high resolution (target width 2048px per default, but configurable) and creates thumbnails at 1024px. Final CLM packaging uses those generated assets together with extracted PPTX metadata.
Can preview render quality be configured?
Yes. Account-level settings can control preview width/quality and thumbnail width/quality within configured bounds.
Why can large files take longer to convert?
Larger decks take more time because each PDF page is rendered in the browser, preview files are uploaded, and finalize packaging processes more assets and ZIP content.
Why can preview feel slow sometimes?
Initial preview requests may be slower because slide/shared ZIP artifacts are loaded from storage and parsed server-side before assets are served. Very large PDFs can also slow browser-side page rendering and upload.
Hidden slides disappeared from my conversion. Why?
If hidden slides should be converted, make sure the exported PDF also includes them. The pipeline maps visible PDF pages to PPTX while hidden PPTX slides are tracked as off-slides in navigation metadata.
Are native PowerPoint animations and transitions converted automatically?
Not fully. Page transitions are not supported. For PowerPoint animations, the sniffer can detect fade and fly-in animation metadata, and it can also detect simple visibility-based reveals. The PDF should represent the initial visual state of each slide, so content that is meant to appear later on click or on a timer should not be included in the PDF export. The animated graphics themselves still need to be available as separate assets. If an object should appear later, export that object from PowerPoint as an individual image, then import it after conversion in the slide editor (as an overlay element) and attach the animation there.
Should I place links directly on text in PPTX?
For best reliability, avoid placing links directly on text. Instead, put a transparent hotspot shape on top of the text and apply the link to that shape.
Can hotspot shapes be rotated in PPTX?
No. Avoid rotating shapes that carry links/hotspots, since rotated hotspot geometry can cause conversion inaccuracies.
Any known pitfalls with links and hotspots in the PowerPoint?
Shape/image links and many text hyperlinks are extracted, but complex PPTX constructs can still require validation. Always QA converted output for edge cases (for example grouped objects, complex link placements, or unusual transforms).
Do you support update workflows?
Yes. The app supports full-deck and partial-deck updates. Partial updates can map changed/new slides against a base run and preserve existing content where applicable.
How do we keep slide IDs stable across updates?
Slide IDs are controlled by presentation external ID and update settings (including ordered slide IDs for full updates). This helps preserve stable IDs between runs when updating existing CLM content.
What is the unique Presentation External ID?
This is the unique name of the presentation in Veeva Vault (you need to create a unique identifier). It is used as a stable identifier to link runs and generated content to the correct presentation in Veeva, and it controls the output filename of the generated ZIP. It also controls the saved user stories so that they only appear for the correct presentation. On updates, the old Presentation External ID is used as the base reference to preserve stable slide IDs and metadata where possible. Otherwise, a new one should be generated.
Can I include custom shared resources?
Yes, for update workflows. The shared-resource ZIP is uploaded as update context (`shared_resource_zip`). In partial update mode, if no base run is available, this upload can be used as the base reference. The finalized shared-resources output ZIP is still generated during finalize (not a blind passthrough merge).
Why is there so much metadata in the form?
Those fields drive Vault Loader manifest values, lifecycle settings, language/product defaults, navigation options, and run behavior. They are saved as project defaults so each run can be reproducible and auditable.
How is Custom Story Builder data scoped?
Story Builder state is stored in browser localStorage with a presentation-scoped key to avoid cross-deck bleed. Bookmark state is also scoped so users can return to their last in-story slide.
Are uploaded files and outputs publicly accessible?
No. The platform is designed for private, authenticated access. Preview routes validate run access, and output downloads are provided through signed URLs.
Is data stored within Europe?
Hosting region is deployment-specific. Confirm your account's configured region with your administrator/support team.
Who owns the uploaded data?
Ownership and usage terms are defined by your organization's agreement and policy. The app stores uploaded files and generated outputs to process conversions and provide downloads.
What is the retention policy?
Current defaults are approximately 21 days for preview/intermediate files, 60 days for source files (PPTX/PDF), and 180 days for final deliverables. Run records can remain visible after files are auto-cleaned. Authorized users/admins can delete run and project data.
I deleted a project or run by mistake. Can it be restored?
No. Deleted projects/runs cannot be restored. The platform does not maintain long-term archival backup of customer-uploaded content beyond defined retention windows.
How do we end an account or remove data?
Project and run data can be deleted by authorized users or admins. Full account closure is performed by admin/support in accordance with the customer’s agreed data-retention and deletion policy.
I keep forgetting the shortcuts when viewing a slide. What are they?
They are: `m` for menu, `b` for black screen, `w` for white screen, `alt+n` for speaker notes. The extra shortcuts are `°`for showing hidden hotspots and `^`for showing visual navigation – buttons back and forth.