The Review and 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.
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.
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.
Changes Awaiting Review
Any changes made to the business architecture domain data will automatically be added to the "Changes Awaiting Review" queue. Review users will be notified of pending reviews.
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.
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.
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.
This illustrates the option for a reviewer to reject a submitted change. It typically includes a dialog box or form where the reviewer can provide feedback or reasons for the rejection, ensuring that the submitter understands what needs to be improved.
This illustrates option where a reviewer can accept a change. Upon acceptance, the change progresses to the next stage in the approval process. The image may highlight how the interface confirms the acceptance and informs the user of the next steps.
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.
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.
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.