Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 (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**). 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.

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 which defines all triggers. The integration service is a custom parthandled by a partner which can facilitate the data exchange. Custom development is required.

...