Lock the Dataset Design
Once the design is "Complete" it should not be possible to modify a dataset without a Scope Change and correct authorization to do so.
This is usually done on projects to prevent the SI from continuously changing the design which has a dramatic effect on the Migration and Testing teams. Locking it forces them to review the changes with the PMO and generate required Change Requests before the dataset can be unlocked by an admin.
Status: Future Consideration
Log in to comment and vote
No comments yet
Be the first to share your thoughts.