Breadcrumbs

Module Creation (MCM)

Previously, creating new Modular Content meant working directly in your DAM (such as Veeva Vault). Activator now includes a built-in workspace for creating Content Modules without leaving the platform. Modules created in Activator are pushed to your DAM for approval through your standard review workflow, then become available for import into slides, emails, and briefs through the existing Importing & Using modules flow.

[Screenshot to add: Content Modules workspace overview]

Content Modules creation is not enabled by default. This capability is activated per customer and per tenant. Contact your Anthill administrator if you need it enabled for your account.

How creation works

A Content Module is created inside Activator and then published to your DAM, where it enters your organisation's standard MLR review and approval flow. Once approved in the DAM, the module becomes available for import into slides, emails, and briefs through the standard Modular Content flow.

Key characteristics of module creation:

  • Author inside Activator. Modules are built in a dedicated authoring canvas in Activator, separate from the slide/email/brief editor.

  • Autoscan from PDF (optional). You can pre-populate a module by uploading a PDF source document. Autoscan extracts text and structure into the module so you don't have to start from a blank canvas.

  • Publish to your DAM for approval. Each module is its own publishable artifact. Modules publish to the connected DAM (Aprimo or Veeva Vault) and enter your organisation's MLR review process there.

Creating a Content Module

The high-level flow:

  1. Open Content Modules. Click Content Modules in the Activator left navigation. The Content Modules workspace loads in the main frame.

  2. Create a new module. Start a new module from the workspace.

  3. Optionally autoscan a PDF. Upload a PDF source document to extract text and structure into the module.

  4. Edit in the authoring canvas. Refine the content, manage fields, and adjust as needed.

  5. Publish to the DAM. Push the module to the connected DAM (Aprimo or Vault) for approval.

After publish, the module enters your organisation's MLR review workflow in the DAM. Once approved, it becomes available for import into other documents.

[Screenshot to add: creation workflow]

A note on autoscan and source languages

Autoscan currently supports source documents in Latin character sets. English, German, French, Spanish, Italian, and Portuguese are supported by the underlying OCR service; Danish is also supported. Non-Latin scripts (Chinese, Japanese, Korean, Arabic, Hebrew, and others) are not extracted by autoscan. For modules sourced from non-Latin language content, use manual text input in the authoring canvas instead of autoscan. All other module functionality is unaffected.

Publishing to your DAM

When you publish a module, it is packaged and sent to the connected DAM:

  • To Aprimo: the module publishes as a document, with an MLR report generated automatically as the source file. The MLR report is produced using Activator's native compile function. Bidirectional lifecycle sync is in place — state changes in Aprimo update back to Activator.

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

The publishing wizard guides the publish run and reflects the connected DAM's specifics. The published module then enters your organisation's standard MLR review workflow within the DAM.

User access and roles

Content Modules respects the standard Activator role and permission model. In the current release, user creation and Content Modules role assignment are handled by Anthill support during onboarding and through the customer lifecycle. To add a user, change a role, or deprovision an account, contact your Anthill support contact. A self-service administration UI is on the product roadmap.

In this section