erwin Evolve 2023.1.0 - General

Review and Approval Workflow

The Review and Approval workflow enables you to manage data quality by forcing changes to your model to be approved before they are committed to the repository.

The process covers all changes made to existing data, including the creation of new objects or the deletion of existing objects, as well as changes to associations data.

The workflow does not cover the following:

• Questionnaires

• Social features - Comments, Ratings and Favorites

Who Approves What?

The Review and Approval Workflow has two levels, which can be combined in your Site:

• Page level

• Object Instance level

Page Level Review and Approval

Page Level Review and Approval works by linking a Role to Index Pages and Object Pages in your Site.

Any changes to the data made via these pages, whether creating new objects, editing existing objects or deleting objects, must be reviewed and approved by members of the Role before those changes are applied.

Role members can approve or reject all, or merely some, of the proposed changes.

See how the Page level process works in detail

These steps assume there are no Object Instance level Approvers which would take precedence over the Page level approval process.

The Page Level process works as follows:

1. A User (who is not a member of the Approver Role) uses one of the associated Pages to create, edit or delete an object.

2. All members of the Approver Role linked to that Page are assigned a new Task informing them of the changes and prompting them to review them.

• If Evolve Workflow is configured to use SMTP, an email is sent to the Role members notifying them of the Task, including a direct link to the Task in the Site.

• The User is also able to view their change request - and can even delete it, discarding their changes, as long as it has not already been approved.

• If the change request relates to the deletion of an object, that object is highlighted with a strike-through wherever it appears in the Site and the UI makes it clear the object is 'marked for deletion'. It cannot be edited while it is in this state.

3. Any one of the Approver Role members reviews the changes and either approves or rejects them.

• The Approver can accept some of the changes and reject others.

• The Task is cleared when one of the Approver Role members approves or rejects the changes.

• The Approver can enter comments explaining their decision which the User can see.

4. The approved changes are submitted to the repository and any rejected changes are discarded.

5. The Task is marked as 'Completed'.

6. A notification is sent to the person who made the changes informing them whether they have been approved or rejected.

• If Evolve Workflow is configured to use SMTP, the notification is sent via email as well.

• The User can also see the outcome of the Task, including any comments, by viewing the Task in the Site.

Object Instance Level Review and Approval

Object Instance Review and Approval works by linking a Role or User to a specific object instance in your model. If another user edits or deletes the object, then it must be approved before the change is committed to the repository.

See how the Object Instance level process works in detail:

1. A User (who is not an Approver for the object) edits or deletes a governed object.

2. All Approvers linked to that object, whether individual Users or in a Role, are assigned a new Task informing them of the changes and prompting them to review them.

• If Evolve Workflow is configured to use SMTP, an email is sent to the Approvers notifying them of the Task, including a direct link to the Task in the Site.

• The User who made the change is also able to view their change request - and can even delete it, discarding their changes, as long as it has not already been approved.

• If the change request relates to the deletion of an object, that object is highlighted with a strike-through wherever it appears in the Site and the UI makes it clear the object is 'marked for deletion'. It cannot be edited while it is in this state.

3. Any one of the Approvers reviews the changes and either approves or rejects them.

• The Approver can accept some of the changes and reject others.

• The Task is cleared when one of the Approver Role members approves or rejects the changes.

• The Approver can enter comments explaining their decision which the User can see.

4. The approved changes are submitted to the repository and any rejected changes are discarded.

5. The Task is marked as 'Completed'.

6. A notification is sent to the person who made the changes informing them whether they have been approved or rejected.

• If Evolve Workflow is configured to use SMTP, the notification is sent via email as well.

• The User can also see the outcome of the Task, including any comments, by viewing the Task in the Site.

Precedence

If you combine Page level approval with Object Instance level approval, there is an order of precedence to determine who must approve what.

The rules are detailed as follows:

• If an object has both levels of approval, then the Object Instance level takes precedence.

• If a user who is in a Page level approval Role edits an object on one of their governed pages, but the object has Object Instance level approvers (Users or Roles) - then the Object Instance approvers take precedence.

What do you want to do?

Set up Approver Roles and Users, and assign them to the pages or objects they must approve

Work with Tasks