Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Introduction

The Review 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.

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.

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

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

image-20240810-035712.png

This illustrates an business architecture domain data changes requiring review.

Changes awaiting review

image-20240810-034002.png

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

image-20240810-034706.png

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

image-20240810-034637.png

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.

  • No labels