Breadcrumbs

Publishing a Content Module

Once your module content is complete, publishing pushes it to your DAM for approval. Publishing runs as a three-step wizard: build, verify, and publish.

Step 1: Build the module

You do this in the authoring canvas, populating the fields defined by your content module type. Manual entry, manual marking, and Autoscan are all valid ways to fill in the module's content.

When the module is complete, click Publish in the canvas to move to step 2.

Step 2: Verify the module

The wizard shows the metadata fields that apply to your module.

  • Pre-filled fields — some fields are already populated from selections you made when creating the module (for example, the content module type and any metadata set at that point).

  • New fields — some fields are only asked for at publish time and need to be completed here.

  • Optional fields — some fields don't need to be populated.

Review the pre-filled fields, complete the required ones, and adjust anything that needs updating.

[Screenshot to add: Step 2 — verify metadata wizard]

Step 3: Publish

Click Publish to run the publish process. The system:

  1. Packages the module and pushes it to AOM (Anthill's asset layer).

  2. Pushes the module from AOM to the connected DAM (Aprimo or Veeva Vault).

A spinner in the Publish button indicates progress. The DAM the module publishes to is preconfigured for your tenant — you don't choose it at publish time.

When publishing completes, the wizard confirms:

  • What was published — the module identifier and its content.

  • A direct link to the DAM record — click to jump straight to the module in your DAM for the next step (MLR review).

[TBC: precise wording of the confirmation and exactly which fields are shown. Content of this section is pending Martin's completion of the wizard step 3 description.]

[Screenshot to add: Step 3 — publish confirmation with DAM link]

What happens in the DAM

Once published, the module enters your organisation's MLR review workflow in the DAM.

  • Aprimo: the module publishes as a document, with an MLR report generated automatically as the source file (see MLR Report for Content Modules).

  • Veeva Vault: the module publishes as an object, with module metadata and associations preserved. Underlying asset content (text strings and images) is stored in Anthill's asset layer.