...
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.7 8 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.7 8 API & SDK - Register external action in AW (webhook)
...
Integration PIM and DAM is a typical use-case for Digizuite. The below gives a high-level view.
...
Digizuite automations Integration Endpoints are key and will be used to push assets to an external service, which will handle the data exchange. The automation integration endpoint in Digizuite will define when to trigger provide asset changes (for instance, on approval and when a product id has been added) but also what metadata fields are required (note: if you have a lot fields to trigger on, then we do ask you to use Integration Endpoint to receive only one event rather than multiple per changed metadata field which would be the case in automation**). 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 assetOn your end, you will receive item ids from the integration endpoint which can be used to look up relevant metadata (using our SDK or API). These metadata contains the product ID, relevant channel and all information needed to be carried to the resource in PIM, and for linking it to the right product.
| Note |
|---|
**if you have a lot fields to trigger on, then we do ask you to use Integration Endpoint rather than automation triggers to receive only one event (as opposed to multiple events per changed metadata). |
Digizuite is responsible for the Automation Engine Integration Endpoint which defines all triggers for asset changes (described further up). The integration service is a custom parthandled by a partner which can facilitate the data exchange. Custom development is required.
...
Please read here for more: DC 5.7 8 API & SDK