Please Share your Product Ideas with us!

All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.

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.

  • John Munkberg
  • Feb 23 2023
  • Attach files
  • Pedro Cardoso commented
    4 Feb 05:43pm

    Agree. A user with a "Change Review Board (CRB)" authorization should be required. This would ensure visibility also to the project lead when there are "changes" made to an object where transparency is not always provided by team members...syniti or especially non-syniti. It happens.