Workflow Launch Exception Rules

In Anjana Data it is possible to configure which changes do not trigger the launch of modification and/or versioning workflows on governed objects when they are made by a specific role.

These rules make it possible to identify the template attributes that, when edited and submitted for validation by certain roles, do not generate an approval workflow, so the object is validated automatically.

Edition Submit Rule Table in the Configuration Panel (Administrator view)

The rules that make it possible to identify the template attributes that, when edited and submitted for validation by certain roles, do not generate an approval workflow are stored in the Edition Submit Rule table.

Structure of the Edition Submit Rule table

Each registered rule is characterized by the following fields:

• Id: unique identifier of the record. It is assigned automatically from the Configuration Panel.

• role: name of the role for which, when editing the attribute indicated in templateAttribute, the record of that change does not go through a modification workflow, but instead goes directly to APPROVED.

• templateAttribute: reference to the template attribute to which the rule applies.

Creating a workflow launch exception rule in the Edition Submit Rule table

Creating a new workflow launch exception rule involves adding a new record to the Edition Submit Rule table that defines the template attribute and the role for which an approval workflow will not be triggered when that attribute is edited.

To add a new rule:

1. Click the New button in the top right corner. This will open a wizard with the fields defined in the Structure of the Edition Submit Rule table section.

2. Fill in the fields according to the structure described:

   • role: enter the name of the role that will not trigger a workflow when editing the attribute (e.g.: Chief AI Governance Officer).

   • templateAttribute: select the template attribute to which the exception applies (e.g.: 10371-nivelRiesgo-AI_MODEL).

3. Click Save to save the rule or Cancel to discard it.

Modifying a workflow launch exception rule in the Edition Submit Rule table

Modifying a rule in the Edition Submit Rule table makes it possible to adjust the workflow launch exception parameters for a specific role or template attribute.

To modify an existing rule:

1. Click the Edit button (green pencil icon) in the row corresponding to the rule you want to modify. This will open a wizard with the fields defined in the Structure of the Edition Submit Rule table section.

2. Fill in the fields according to the structure described:

   • role: update the role that will not trigger a workflow when editing the attribute, always consistent with the name field of the Roles table (e.g.: change from Chief AI Governance Officer to AI Risk Officer).

   • templateAttribute: update the template attribute to which the exception applies (e.g.: change from 10371-nivelRiesgo-AI_MODEL to another template attribute).

3. Click Save to save the changes or Cancel to discard them.

Configuring workflow launch exception rules via direct database access (Developer view)

Workflow launch exception rules are stored in the anjana.edition_submit_rule table.
These rules make it possible to identify the template attributes (configured in anjana.template_attribute) that, when edited and submitted for validation by certain roles (configured in zeus.role), do not generate an approval workflow, so the object is validated automatically.

The following example defines a rule that assigns the Chief AI Governance Officer role authority over the template attribute with identifier 10371- nivelRiesgo of the AI_MODEL template:

INSERT INTO anjana.edition_submit_rule
(id_edition_submit_rule, "role", id_template_attribute)
VALUES (2, 'Chief AI Governance Officer', 10371);