Configuration
Configuration
Breadcrumbs

Exception Rules for Workflow Launch

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

These rules allow identifying the template attributes that, when edited and submitted for validation by specific roles, do not generate an approval workflow, and the object is automatically validated.

image-20250910-170050.png
Example of how a risk level modification made by the Chief AI Governance Officer does not generate a validation workflow

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

The rules that allow identifying the template attributes that, when edited and submitted for validation by specific roles, do not generate an approval workflow are stored in the Edition Submit Rule table.

image-20250910-170323.png
Edition Submit Rule table where workflow launch exception rules are configured

Structure of the Edition Submit Rule table

Each registered rule is characterized by the following fields:

  • Id: unique identifier of the record. Automatically assigned 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 status.

Note: The value must match the name field of the role table

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


If you want to prevent a validation workflow from being triggered when dataset fields of a dataset are modified, it is necessary to configure an exception rule for the datasetFields attribute in the dataset template.

With this rule:

  • The changes made to the dataset fields will be checked.

  • If those changes match the conditions defined in the rule, the validation workflow will not be triggered for the dataset.

  • Additionally, the rule covers both the modification of values and the addition or deletion of dataset fields in the dataset.

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

Adding 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.

image-20250910-171419.png
Example of adding the rule that allows the Chief AI Governance Officer role to modify the Risk Level attribute of the AI_MODEL subtype without triggering a workflow

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.

Note: After adding new rules, it is necessary to run the Clear cache action from the Configuration Panel (Actions > Clear cache) for the changes to be applied and become visible in the Data Portal.

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

Modifying a rule in the Edition Submit Rule table allows adjusting 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 in accordance 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.

Important considerations

  • Rules can be modified at any time, regardless of whether governed objects exist or not.

  • If you want to modify both the role and the attribute while maintaining consistency with previous configurations, it is recommended to evaluate whether it is more appropriate to delete the existing rule and create a new one.

  • After modifying rules, it is necessary to run the Clear cache action (Actions > Clear cache) from the Configuration Panel for the changes to be applied and become visible in the Data Portal.

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 allow identifying the template attributes (configured in anjana.template_attribute) that, when edited and submitted for validation by specific roles (configured in zeus.role), do not generate an approval workflow, and the object is automatically validated.

Column

Type

Constraints / Notes

id_edition_submit_rule

int4

PRIMARY KEY. Unique identifier of the rule. Managed manually or through a sequence.

role

varchar(255)

NOT NULL. Name of the role to which the authority is assigned.

id_template_attribute

int4

FOREIGN KEY to anjana.template_attribute(id_template_attribute). Defines the template attribute to which the rule applies.

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

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

Important:

  • Once the insert has been executed, run the sequence update for the table. (From the Configuration Panel at Actions > Reset DQ sequences you can update the sequences for all tables, including this one).

  • The entire responsibility for the configuration logic falls on the developer executing SQL queries directly against the tables. It is strongly recommended to carefully review the Structure section.