When you get many shared objects in your subset that you, do not need for your current task, it is helpful in a teaming environment to check in the subset right away, rescope it, and check it out again.
The following table shows that an example about the subset contains more objects than necessary:
|
Task |
To correct the spelling of the company name on a Screen Template. |
|---|---|
|
What was scoped |
Screen Template, default expansion and default protection. |
|
Resulting subset |
The resulting subset contains all screens that use the template with Modify protection. Some team members are upset because they cannot work on the screens they need. |
|
What to do next |
Upload the subset with check in as soon as possible to relinquish control of everyone's screens. Determine why the screens were included, by checking the expansion table for Template at default. Short expansion of the template is what you need. It lets you change fields on the template without monopolizing all the screens that use the template. Use the Subset Definition Summary function to specify short expansion for the scoped template. Check out the subset again. With short expansion, your subset receives the template and all its screen items without tying up the screens that use the template. |
The following table shows expansion table for template high‑level:
|
This Template expansion |
Includes the following additional objects for all subset types |
with this default protection |
|---|---|---|
|
Short and Default |
Screen Template and Bilingual Text |
|
|
Short and Default |
Business System and System Defaults |
|
|
Default |
Screens, Procedure Steps, Action Blocks, Windows, and Procedures |
|
|
Default |
Referenced Entity Types and Parent Subject Areas |
|
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|