CLM export and Veeva handoff
Understand package preparation, HTML5 review and native acceptance boundaries.
Check export availability#
Open Export on the saved CLM project. The panel separates Native Veeva CLM from HTML5 reviewer preview. Availability depends on the current service and the saved presentation.
Availability: preparing new native slide packages is currently unavailable. The workflow below explains the available panel and the steps used when package preparation is enabled. Existing authorized exports can still be checked and downloaded.
Prepare packages when enabled#
- Save the presentation and confirm the revision shown in Export CLM handoff.
- Select Native Veeva CLM and review Check presentation, media readiness and saved authoring requirements.
- Fix blocking findings, save and run the check again.
- When enabled, choose Prepare slide packages.
- Follow the saved export status. Use Check saved export for a progress update.
- After a verified publication is available, choose Download complete handoff ZIP or an individual slide download.
Understand the outputs#
The native handoff contains ordered slide ZIPs and an upload map. Download package manifest provides the saved revision’s document roles, metadata, relationships and local asset references. A manifest is not proof that a runtime package has been built.
Download PromoMats handoff creates a manual handoff from an available export. Tenant, binder and document mappings still need to be resolved for the destination.
For a generic browser review, select HTML5 reviewer preview and choose Open saved HTML5 review when a matching build is available. Choose Rebuild saved revision when you need a new preview of the current saved revision. Follow the build status and open the matching result.
Finish acceptance in the intended client#
A prepared ZIP does not establish Vault upload, approval, distribution or device acceptance. Your Veeva administrator and review team must handle the destination workflow and test the actual named client, device and offline behavior.
Review field access, navigation, media and context switching in that target environment. Browser sample data and saved native declarations do not establish a live selected-HCP connection.
Handle an uncertain export#
If the request is retained but its outcome is unclear, choose Check saved export. Use Retry exact saved request only when Studio offers it. An export for an earlier revision remains attached to that revision after the project advances.