Approvals

Introduction

The approvals process ensures that all changes to the business architecture domain data are thoroughly vetted and validated before becoming part of the official record. This process is crucial for maintaining the integrity and accuracy of your organization's data. Below is a step-by-step guide on how to use the process effectively.

It uses a structured workflow involving multiple roles within your organization. Each change submitted to the system is automatically queued for review and approval. This ensures that data modifications are evaluated by the appropriate personnel before they are finalized.

Review and approval requests

These are the actions that require review and approval.

• Uploads

• Manual node copy, add, edit, archive, un-archive, delete

The process

Steps

The approval process has two steps:

1. Review

2. Approval

Roles Involved

Review Users

• Users in the same or higher business unit within the organizational hierarchy can review changes made by other users.

• Review users are responsible for ensuring that the changes made align with organizational standards and policies.

Approvals

• After a change has been reviewed, it must be approved by an admin user.

• See Review and Approvals admin for a description of administering reviews and approvals.

Review Process

• Changes Awaiting Review
  Any changes made to the business architecture domain data will automatically be added to the Task list. Review users will be notified of pending reviews.

• Review options

The reviewer either approves or rejects the action.

• Review Options

  • Reject Review: If the changes do not meet the necessary criteria or standards, the reviewer can reject the review, providing feedback for improvement.

  • Accept Change: If the changes are satisfactory, the reviewer can accept them, moving the changes forward in the process.

• Approval statuses

After the approval step, the change is either in an approved or rejected status.

Reviews

Changes awaiting review

This illustrates the interface where users can see a list of changes that are currently waiting to be reviewed. Each entry typically includes details such as the date, the type of change, and the user who submitted it. The image emphasizes the organized queue system, ensuring that all changes are systematically reviewed by appropriate personnel.

Review request details

The review request details are available when you rollover a review or approval request summary.

Review confirmation comments

This overlay is displayed to reviewers a reviewer when they approve a review. Review rejection also requires a confirmation comment as well.

Approval confirmation comments

This overlay is displayed to an approver when they reject a change (after the review is approved). Review approval also requires a confirmation comment as well.