When you publish a content module to Aprimo, an MLR report is generated automatically as the source file for the module document. This page describes what the report is and how it's used in MLR review.
Why the MLR report exists
Aprimo stores content modules as documents, and documents require a source file. The MLR report serves as that source file — a review-friendly rendering of the module's content and metadata that MLR reviewers can open directly from Aprimo.
How the report is generated
The MLR report is produced using Activator's native compile function. When you publish a module to Aprimo, the report is generated automatically as part of the publish flow — you don't need to trigger it separately.
What the report contains
[TBC: specific report contents — module fields, metadata, references/claims, formatting. To confirm with product design and against a real generated report.]
[Screenshot to add: Example MLR report]
Veeva Vault (no MLR report)
The MLR report is specific to Aprimo publishing. Vault stores content modules as objects rather than documents, so no source-file report is generated during Vault publishing. Reviewers work with the Vault record directly.
Related
-
Publishing a Content Module — where the MLR report gets generated.
[Draft skeleton — content of the MLR report itself needs confirming against a real generated report.]