Skip to main content
Skip table of contents

Preflight Image Sync for priint:comet | FAQ

SDZeCOM Preflight Image Sync for priint:comet enables the automated exchange of preview images and original image data in both directions.
This ensures that the layout always uses the latest image status from Centric PXM™ - without the need for manual path maintenance.
The result is an efficient, media-break-free workflow between PIM/MAM and publishing.

1. What is Preflight Image Sync for priint:comet?

Preflight Image Sync is an extension for priint:comet developed by SDZeCOM that automates image synchronization between Centric PXM™ and Adobe InDesign.
It ensures that designers and media creators always work with the correct image version - whether it's a quick preview in the layout process or the print-ready original.
This eliminates manual follow-up work, incorrect images, and redundant imports.

2. How does the solution work?

The priint:comet plug-in establishes the connection between InDesign and Centric PXM™.
Images in the layout are not linked via classic file paths, but via placeholders that point to the corresponding MAM objects.
Preflight Image Sync offers two automated methods:

  • Sync to Preview – replaces all original images in the document with current preview images, e.g., for performance and layout construction.

  • Sync to Original – replaces all preview images with the original image data, e.g., before export or printing.

Both methods access the latest image version from Centric PXM™ directly, ensuring that no outdated assets remain in the document.

3. Which systems are supported?

Preflight Image Sync is compatible with:

  • Centric PXM™ | SaaS

  • Centric PXM™ | On-Premise, provided images are linked via HTTP links

  • priint:comet (in conjunction with Adobe InDesign)

4. Are there any technical requirements or dependencies?

An existing integration of priint:comet in Adobe InDesign and a connected Centric PXM™ instance are required.
The solution uses existing asset links (HTTP-based) and does not require any additional server components or scripting extensions.
For operation in on-premise environments, access to the image URLs is to be ensured.

5. What are the advantages of this solution?
  • Automated image matching between Centric PXM™ and InDesign

  • Quickly switch between preview and original images without changing paths

  • Always up-to-date assets, regardless of when they were last downloaded

  • Reduced manual effort and fewer sources of error in the layout process

  • Performance optimization through preview images during editing

  • Production reliability through reliable use of the final original images

6. What are some typical use cases?
  • Designing extensive catalogs, price lists, or data sheets that require the synchronization of numerous images

  • Layout phase: Working with preview images for smooth scrolling and quick placement

  • Production or print approval phase: Automatic replacement with original images for maximum quality

  • Quality assurance prior to publication: Ensuring that all assets used correspond to the current status in the MAM

7. How is the solution used in Centric PXM™?

Preflight Image Sync is provided directly as a function within priint:comet.
Users can select whether the document ist to be synchronized to preview images or originals via a menu command or automation job.
This is done across the entire document without having to manually replace individual images.
This allows layouts to be updated with just a few clicks – efficiently, securely, and in a time-saving manner.

8. Can image matching be triggered automatically in the publishing workflow?

Yes. Using priint:comet workflow automation or CometBridge scripts, Preflight Image Sync can be performed automatically prior to certain actions, such as PDF export or print approval.

9. How are errors or unavailable images handled?

Unreachable or incorrect image URLs are logged. The affected images remain marked in the layout so that they can be easily identified and corrected in PXM.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.