...
Digizuite has a very powerful automation engine which allows customers to construct business logic in a drag & drop fashion (no- or low-code). The logic consists of a number of steps that can either be a trigger, an action, a filter or for-loop (iterating elements). So an automation could be triggered based on metadata changes on an asset, or an asset arriving at a certain state in a workflow, and then the steps can filter if that change is relevant and if it is then perform certain actions within the DAM or externally. Full docs are here: DC 5.6 7 Automations.
We allow any customer or partner to add own actions via our SDK from 5.6.0. We also have a public example on how to do that using our SDK (https://github.com/Digizuite/integration-api-examples/tree/main/AWExternalAction ) and documentation is also here DC 5.6 7 API & SDK - Register external action in AW (webhook)
...
To the Invoke Endpoint as made above then simply take the URL and add it here (remembering to add the right asset ID parameter):
...
PIM & DAM
...
Please read here for more: DC 5.6 Integration PIM and DAM is a typical use-case for Digizuite. The below gives a high-level view.
...
Digizuite automations are key and will be used to push assets to an external service, which will handle the data exchange. The automation in Digizuite will define when to trigger (for instance, on approval and when a product id has been added) but also what metadata fields are required. When all requirements are met, then the trigger will send the asset id to an Integration Service which can create or update it in the PIM based on the product ID, but will also set the initial product values on the asset.
The integration service is a custom piece handled by a partner which can facilitate the data exchange.
...
To summarize the push flow from Digizuite.
Asset is approved and gets product ID which triggers a message to the integration service
The integration service will look up the asset based on its ID, see all the metadata and attach (or update) the asset to the right product. It will also add relevant metadata to the asset in PIM (such as description) if desired.
The integration service will also (based on the product id) set metadata back to the asset in DAM if desired.
Data must also flow the other way into Digizuite. The relevant data:
Synchronizing the Product Hierarchy from PIM to DAM
This is important because it can be used to select the relevant product directly from DAM. And since it is synced from PIM, you know that those products exist.
Updating Product Data when it changes in PIM. Either this can be handled by a scheduled job within Digizuite automations which will get updated products at certain intervals, or it can be webhooks from PIM to the Integration Service layer which will then update on the relevant assets in PIM.
Important decisions for PIM and DAM
What should trigger an asset to be added or updated on a product
Approval steps, required metadata and so on.
What asset metadata should be added to the asset in PIM
What product attribution should flow back from PIM to DAM
What happens when an asset is expired? Should it be removed immediately in PIM or what is the process?
Decide on how to approach the data from PIM to DAM. Should it be scheduled job which pulls data from PIM in intervals or should it be webooks.
Ensure that there is clear responsibility for the partner who develops the Integration Service.
Relevant examples on how to communicate with the DAM can be found in our GitHub API examples: https://github.com/Digizuite/integration-api-examples/
It shows a full Azure Function service and how to use it with the SDK.
Custom Integration using our API or SDK
Please read here for more: DC 5.7 API & SDK