Responsibility Rules

Responsibility rules are used to automatically define who will be responsible for a certain action or task within the system.

Scope of the Rules

Responsibility rules are created within types and can only be used within the type where they were defined. This ensures that responsibilities are always contextualized and organized.

Rule Structure

When creating a responsibility rule, the following fields must be filled in:

General Data

• Name * : Name of the rule, used for identification.
• Order * : Defines the priority of the rule when more than one is applicable. Rules with a lower order value are evaluated first.
• Description: Optional field to describe the purpose of the rule.

Start Conditionals The rule must contain a starting conditional, with two possible options:

• Conditionals * : Allows selecting one or more previously created conditionals.
• Form and Conditionals:
  • Form * : Selects one of the forms from the type.
  • Conditional: (Optional) Allows applying a conditional to the selected form.

This configuration defines when the responsibility rule will be activated.

Responsibility After defining the condition, you must configure who will be responsible. To do this, select the type of responsible party *, with the following options:

• Users: Opens a list with the workspace users.
• Groups: Opens a list with the groups defined in the workspace.
• Requesting User: Sets the user who originated the request as responsible.
• Everyone: All users in the workspace will be considered responsible.
• Based on Field: Opens a list with the fields of the type (usually used with email-type fields). The system will use the value of the field as responsible.