Review and Approval admin

Introduction

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

For the review process, see: Review and approval

The process

Roles Involved

Approver Users

• Admins, Data Admins, and Compliance Admins have the authority to approve content changes.

• Note: User Admins do not have the ability to approve changes.

Approval Process

• Changes Awaiting Approval
  Once a change has been reviewed and accepted, it is moved to the "Changes Awaiting Approval" queue. Approver users will be notified of pending approvals.

• Approval Options

  • Approve Changes: Approver users can approve changes, which finalizes the modification and incorporates it into the official business architecture domain data.

  • Reject Changes: If the changes are not suitable, the approver can reject them, sending them back for further review or revision.

Review approvals

Changes awaiting approval

Open

This illustrates changes that have been reviewed and are now awaiting final approval. Similar to the review queue, it includes details like the submission date, type of change, and reviewer comments. It underscores the role of approvers in maintaining data integrity.

Approve changes

Open

This illustrates the approval interface where an admin approver can give final approval to a change. The image shows the confirmation process and the impact of approval, such as the change being incorporated into the business architecture domain data. The approver can optionally provide reasons for their approval.

Reject changes

This illustrates the process of rejecting changes during the approval stage. The approver can optionally provide reasons for rejection, ensuring that the change rejection notification is commented.

Review and Approval admin

The table below illustrates the different stages of the review and approval process. It includes submissions of various types of business architecture domain data, each progressing through review and approval workflows managed by authorized personnel. The roles involved in this process include reviewers who assess the changes for alignment with organizational standards, and approvers who provide the final validation to incorporate the changes into the system.

This structured approach ensures that only thoroughly evaluated and approved data is recorded, supporting the organization's commitment to high standards of quality and compliance.

Reviewing and approving

Once a submission is selected, it opens the detailed review or approval process, where the admin reviewer/approver approver can assess the changes, provide comments, and make a decision to approve or reject the submission. This ensures that all data modifications are thoroughly evaluated and align with organizational standards before being finalized.

To review and approve changes:

• Select a submission for review or approval.

• This will open the review or approval process as shown in Review and approval

Bulk rejection and approvals

The Bulk rejection and approvals process for handling multiple submissions at once allows authorized users to approve or reject several changes simultaneously, streamlining the workflow and improving efficiency. This feature is particularly useful for large volumes of changes that require consistent approval or rejection criteria, ensuring that the process remains efficient without compromising the quality and accuracy of the data being managed.