Reference Allowed

If you set the flag to Yes, objects of that subtype can inherit their classification values for that hierarchy level from their container: the Domain, Application Area, Work Area, Report Set, or Workflow where they are located.

You must also assign the same hierarchy level to the parent object subtype.

To make this happen automatically when each object of this subtype is created, you must also set the default classification for the hierarchy level to Inherited (see Setting a Default Classification).

Allowing classification by inheritance can save time during object definition, especially if your organizational structure and classification systems are compatible. For example, if your Application Areas contain applications for a single study, you can assign the hierarchy level Project > Study to Application Areas and to Programs, Tables, Report Sets, and the other primary objects that are contained directly in Application Areas. Then when you classify a particular Application Area to a particular study, such as Project01 > Study01, all the objects contained within it are automatically classified to Project01 > Study01 as well.

In addition, if you change the classification of the Application Area, all the objects it contains for which inheritance classification is allowed are automatically reclassified to the new value for the same hierarchy level. For example, if you copy the Application Area classified to Project01 > Study01 (with all the objects it contains) to serve as the basis for the Application Area for Study02, and change the classification of the copy to Project01 > Study02, the objects it contains are automatically reclassified to Project01 > Study 02.

You can define several levels of classification by reference. For example,

Figure 5-2 Example of Classification by Inheritance

Description of "Figure 5-2 Example of Classification by Inheritance"