After a creative deliverable is complete in the Workflow app and uploaded to Acquia DAM, it typically requires users to manually search Project Numbers and Deliverable IDs to tag assets correctly.
The Workflow-to-DAM Metadata synchronization integration eliminates this manual re-keying of information. Upon upload of an approved deliverable, Acquia DAM identifies the Project Number and Deliverable ID in the filename. It then communicates with the Workflow app to pull all associated project values, such as Campaign Name, and maps them directly to the asset UI metadata fields. Optionally rename the asset in the DAM based on your configuration.
Key benefits
Automated synchronization: Eliminates the need for manual metadata tagging upon upload.
Single source of truth: Ensures that your DAM metadata matches your project management data exactly.
Standardized filenaming: Gives your teams the incentive to follow strict naming conventions, which enables Acquia DAM to identify the Project Number and Deliverable ID in the filename and accurately trigger metadata synchronization.
How it works
This integration is a Native Integration powered by Workato. It operates in the background without any new UI components to install or manage. Acquia creates, maintains, and supports the integration on your behalf.
Prerequisites and requirements
You must have active subscriptions to both Acquia DAM and the Workflow app.
Users must provide the Project ID or Deliverable ID in the filename to enable the integration to recognize and process the asset.
A Native Integration subscription (glossary term, activate to view definition) is required. You do not need to purchase a separate API feature, as Acquia manages the API calls through the integration service.
Limitations and considerations
Review the following limitations regarding how this integration interacts with Acquia DAM:
Triggering: The integration triggers on all file updates. It cannot be configured to trigger only on specific field updates.
Metadata types: The integration does not assign or change Metadata Types in the DAM. Your designated Upload Profile (glossary term, activate to view definition) must handle Metadata Types.
Asset groups: Changes to Asset Groups or Metadata Types in the DAM do not trigger the integration.
After a creative deliverable is complete in the Workflow app and uploaded to Acquia DAM, it typically requires users to manually search Project Numbers and Deliverable IDs to tag assets correctly.
The Workflow-to-DAM Metadata synchronization integration eliminates this manual re-keying of information. Upon upload of an approved deliverable, Acquia DAM identifies the Project Number and Deliverable ID in the filename. It then communicates with the Workflow app to pull all associated project values, such as Campaign Name, and maps them directly to the asset UI metadata fields. Optionally rename the asset in the DAM based on your configuration.
Key benefits
Automated synchronization: Eliminates the need for manual metadata tagging upon upload.
Single source of truth: Ensures that your DAM metadata matches your project management data exactly.
Standardized filenaming: Gives your teams the incentive to follow strict naming conventions, which enables Acquia DAM to identify the Project Number and Deliverable ID in the filename and accurately trigger metadata synchronization.
How it works
This integration is a Native Integration powered by Workato. It operates in the background without any new UI components to install or manage. Acquia creates, maintains, and supports the integration on your behalf.
Prerequisites and requirements
You must have active subscriptions to both Acquia DAM and the Workflow app.
Users must provide the Project ID or Deliverable ID in the filename to enable the integration to recognize and process the asset.
A Native Integration subscription (glossary term, activate to view definition) is required. You do not need to purchase a separate API feature, as Acquia manages the API calls through the integration service.
Limitations and considerations
Review the following limitations regarding how this integration interacts with Acquia DAM:
Triggering: The integration triggers on all file updates. It cannot be configured to trigger only on specific field updates.
Metadata types: The integration does not assign or change Metadata Types in the DAM. Your designated Upload Profile (glossary term, activate to view definition) must handle Metadata Types.
Asset groups: Changes to Asset Groups or Metadata Types in the DAM do not trigger the integration.
Versioning: Your standard DAM settings handle file versioning, such as when you upload a duplicate or new version.
Asset removal: If an asset requires removal, the integration can expire it or assign it to a separate Asset Group. The integration cannot permanently delete assets from the DAM.
Collections: The integration cannot change or manage Global collections.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Versioning: Your standard DAM settings handle file versioning, such as when you upload a duplicate or new version.
Asset removal: If an asset requires removal, the integration can expire it or assign it to a separate Asset Group. The integration cannot permanently delete assets from the DAM.
Collections: The integration cannot change or manage Global collections.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Acquia DAM