Cascading Activation or Inactivation of an Object
Using the CascadeInactiveToggle system preference set to
TRUE, you can inactivate or activate any object with multiple hierarchy
levels below it, such as a Business Component with child objects such as Fields and
Scripts.
The cascading inactive or active state applies from the level at which you set it to its child objects. You do not have to set it at the top level of an object; you can set it at any level. The cascade applies only to the object at the level at which you set it and to its children within that workspace.
For example, for the A Portfolio Account List Applet object, if the developer sets
the Inactive Flag to Y at the parent Applet level, the inactive status
cascades to all object levels below the current level in that workspace only. In this
case, because the top-level object is inactive, the entire object is inactive. If you
inactivate the List property of the Applet, the List and its children become
inactive, while the parent Applet remains active.
If the development workspace is delivered to its parent integration workspace, the delivered object in the parent workspace shows the object and all its children as inactive, just as in the delivered child developer workspace. If another child developer workspace exists under the same parent workspace and you rebase from the parent workspace to the child workspace, that child workspace also shows the object and all its children as inactive.
| CascadeInactiveToggle Value | Result |
|---|---|
| TRUE | Inactivates/Activates the entire object (parent and children) from the level you set it down. |
| FALSE/System Preference does not exist | Inactivating an object at parent level will not have any effect at child/grandchild/great grandchild levels of that object in the Workspace. |