| Table of Contents | ||
|---|---|---|
|
Introduction
The Review
...
FAQs
What content changes are reviewed? All process ensures that all changes to the business architecture domain data are automatically added to the review process.What content changes are approved? Its the same as review content.All changes to business architecture domain data are automatically added to the review process.
Can an admin user review or approve their own review? Only in the case where they are the only admin user, Part of the reason for this is socialise changes.
Review users
Other users 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.
The process
Roles Involved
Review Users
Users in the same or higher business unit within the
...
organizational hierarchy can review changes made by
...
other users.
Approver users
These admin user roles can approve content changes:
Admins, Data Admins, Compliance Admins.
...
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 "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.
Reviews
...
This illustrates an business architecture domain data changes requiring review.
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.
Reject review
...
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.
Accept change
...
Approval
Changes awaiting approval
...
Approve changes
...
Reject changes
...
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.