Managing an Environment for Subsetting › Apply Effective Project Management Techniques › Subsetting Considerations › Protection Subsets

Protection Subsets

Protection subsets are used to prevent inadvertent deletions, modifications, or both. They also enable the subset owner to perform required modifications without having to check out a subset, because the protection subset is typically checked out and has been granted the correct protection. For example, the DA/DBA would typically be the owner of the ERD/TD protection subset and use it to change the data model or data structure.

Protection subsets are defined as follows:

• The data model and associated data structure
• Global exit states
• Business system defaults
• Shared the objects such as common action blocks and work attribute sets

Project model managers own or assign protection subsets. These subsets are the first checked out from the model following any full check-in or model maintenance activity. They are organized into logical subset groupings to minimize the time that is required to override checkout status and redownload as new objects are added.

To protect or modify the data model and its associated data structure:

Note: If the database is scoped, it must have Delete protection to do transformation. Expansion of the root subject area by itself automatically provides the database with Delete protection and enables transformation.

To protect or modify stable global exit states:

To protect or modify:

• Business system defaults/Existing commands
• Existing business system exit states/Existing templates, video attributes, and edit patterns

This subset definition does not prevent the addition of new exit states or templates, because any number of users can still have Access protection on the business system while it is checked out with Modify.

To protect/modify shared objects, such as common action blocks and work attribute sets: