MM 6.0 Automation

With this feature, the user can build custom automations that automates repetitive work.

Automations consist of the following elements:

1. Triggers
   A trigger defines the start of the automation and there can be more than one trigger, i.e. possibly multiple entry points to the automation. A trigger can be one of the many events in the solution, such as an asset being uploaded, metadata being changed or on a timer interval.

2. Filters
   Filters are used to narrow down possibilities and ensure the action is taken only for the desired case and multiple filters can be applied. A possible filter could be for example validating that a certain value is selected in a combo, or validating the user provided value against a RegEx, or even validating the date against a predefined date.

3. Actions
   Actions are automated work steps that the system can perform and there can be more than one action in the automation. Actions that can be taken range from publishing or unpublishing assets to setting access rights and executing searches.

Automations are created and modified by user with high level of clearance (usually a consultant at Digizuite). Specifically, it is the user with the role Can_Edit_Automation_Workflows.

Options available for automation, such as creating or modifying them, are available in the Automation section under Settings menu on the right side of the top bar.

Open

The overview of events (information and errors) related to active automations can be accessed in Logs section under the same Settings menu.

More information can be accessed in the DC User Guide: https://digizuite.atlassian.net/wiki/spaces/DD/pages/3804631246/DC+6.0+Automations .