Configuring workflows in the rights module

Use the Rights info area to determine that workflows are initiated when certain events occur in the database.

The following events can initiate workflows:

  • Changes to data carried out by users, workflows, triggers, imports (only Hidden workflows) or in the Maintenance module (only Hidden workflows).
  • Merging companies or persons: Workflows are initiated when companies or persons are deleted when merging. No workflows are initiated for child records.
  • Functions in the business logic.
Note: Workflows are not initiated by changes to data caused by communication or importing templates with Aurea CRM cockpit.

These settings apply to all users (including the administrator) assigned these access rights as either their station, group or user access rights. For details on how workflows are affected by extended access rights and on inheriting settings, see Further Settings for Triggers and Workflows and Inheritance Properties per Element in the Core Administrator Guide.

When a database action initiates a workflow, the workflow is added to the stack, which stores all workflows yet to be executed. Workflows are added to the stack in the order they are entered in the list. The order in which you enter workflows can therefore be important.

If you want to execute both triggers and workflows in a specific order, enter both the triggers and workflows in the Triggers cell in the Rights info area instead. The triggers and workflows are then executed in the order they are entered in the Triggers table. For more details, see Triggers in the Core Administrator Guide.