Versions Compared

Key

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

If “Copyright Notification“ feature is enable, before the user downloads an asset, they will be shown a copyright disclaimer and be asked to accept it.

Setting the copyright disclaimer

The copyright disclaimer is set per-asset and can be set or updated from the metadata editor.

The disclaimer is set by opening the metadata editor and setting the desired values for the metafields designated to hold information about the copyright notification.

...

If both the predefined and custom values are set, the user will be asked to agree only to the predefined disclaimer.

If none of the values are set, the user will not be asked to agree to any disclaimer for that asset.

Agreeing to the disclaimer

When trying to download the asset, the user will be displayed the copyright disclaimer for the asset. After the user agrees to the disclaimer, they are able to download the asset. The user agreement is logged in an audit trail that can be reviewed.

...

When trying to bulk download multiple assets, the user will be presented with the disclaimer of all the assets selected and have to opportunity to individually review each disclaimer.

...

2.21.1 Automated Workflows

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

Automated workflows consist of the following elements:

  1. Triggers
    A trigger defines the start of the workflow and there can be more than one trigger, i.e. possibly multiple entry points to the workflow. 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 workflow. Actions that can be taken range from publishing or unpublishing assets to setting access rights and executing searches.

Automation workflows are set up by administrative user with he high level of clearance (usually a consultant at Digizuite).

More information can be found can be accessed in the DAM Center User Guide: section Digizuite™ DAM Center 5 → DC 5.3.0 → DC 5.3.0 4 Configuration → DC 5.3.0 4.10 Automation Workflows (DC 5.3.0 4.10 Automation Workflows ).

2.21.2 Business Workflows

Unlike Automation Workflows, the purpse of Business Workflows is to support different use cases of collaboration between users, and therefore they involve actions taken by the users to advance the workflow. A business process underlaying a workflow is presented in a graphic form.

This is an example of a Business Workflow:

...

All the options related to workflows (both automationa and business) can be accessed from Workflow managament menu in the top panel.

...

The Workflow management menu has the following sections:

  • Workflow overview: it shows the list of all created workflows, filtered by the type of workflow

  • Workflows: the space for viewing, creating and editing automation workflows

  • Logs: the overview of events (information and errors) related to active workflows

  • Job Status: the overview of jobs related to active workflows, with the possibility of filtering by such criteria as asset, status or user

  • Tasks: the overview of tasks assigned to the user.

Creating business workflows

...

Use cases

The following Business Workflows are currently supported in the system:

Request download

...