Know what you plan to do with a subset before you define it. Create each subset to support a specific set of toolset tasks.
Define the smallest subset possible.
Smaller subsets result in:
Lower cost for checkout
Reduced protection conflicts between users of a model
Minimum impact of current access to the encyclopedia
Minimize potential conflict over objects that may be shared across subsets by requesting the minimum protection and expansion that is required to accomplish your task.
After creating a subset, review the expansion and protection of each scoping object from the Subset Definition Summary.
Remove unnecessary objects.
If you have scoped both the procedure and the procedure step, remove the procedure if possible, or if not, remove the individual procedure step that is already part of the procedure expansion.
Lower the protection levels where possible.
Never request Delete protection for a scoping object unless you delete a component that requires this level of protection. Any other subset that needs the object can get it with only Read protection.
Avoid requesting Modify protection when Access works too.
Lower the expansion levels, where possible.
For example, Scope only the needed procedure step instead of the whole procedure.
To maintain a procedure step action diagram, scope the procedure step.
To maintain the dialog flows between two or more procedure steps, scope only those steps with short expansion and subset type Design.
Avoid requesting full expansion when it is not required for the task.
If an object you delete is selectable through the Delete Object function, use this means of deleting the object rather than scoping the object with delete protection in a subset.
If the object you delete is not selectable through the Delete Object function, determine how to define your subset for this object deletion by running the Delete report from the Host Encyclopedia Reports menu named Object Cross Reference Reports. This report lists the objects that you must include in your subset with the object you want to delete.
To delete an object and references to it, explicitly select for inclusion all references to the object in the subset. Otherwise, you receive a message that the subset is incomplete. Do not assume that asking for Delete protection of an object automatically brings in all usages of the object.
If you create a reference to an object, be sure that you request Access protection, not only Read.
For example, to create an action diagramming information view, you must have Access protection of an entity type. You cannot create views when the entity type has Read protection.
