Pseudo files allow for the objects within the configurations to be logically organized into files. Pseudo file functionality is also useful for defining behavioral characteristics for those objects.
The following set of characteristics can be defined against a pseudo file and apply to all the objects within that pseudo file:
|
Characteristics |
Features |
|---|---|
|
Path |
Allows for the contents to be persisted to a file in another location. |
|
SuppressOutput |
Specifies that the contents of the pseudo-file are not to be included in a SaveAs file (XML). |
|
SuppressLoad |
Specifies that the contents of the pseudo-file are not to be loaded into memory. |
|
ReadOnly |
Specifies that the contents of the pseudo-file cannot be modified. |
|
ReadOnlyFile |
Indicates that the file for the pseudo-file is a read-only file. Similar to ReadOnly. Unlike ReadOnly, this value cannot be modified interactively and can only be changed by making the file writable (requires exiting and reopening the Schema Editor). |
|
IsObsolete |
Indicates the pseudo-file cannot be the active pseudo-file; therefore, new objects cannot be added to the pseudo-file. |
|
WriteDisabled |
Indicates that the file cannot be changed interactively. Similar to ReadOnly. Unlike ReadOnlyFile, WriteDisable has nothing to do with whether there is an external file for the pseudo-file and whether that file is itself read-only. |
|
Level |
Specifies the level for the pseudo-file. Level is used to define authoring objects (level 4) and is also used to define whether a pseudo-file can be missing (useful in development environment). |
|
Application |
Specifies the application for the pseudo-file. If this application is not specified to be included as part of the Set Active Configuration command, then the objects in this pseudo-file are not be parsed into memory. |
|
SuppressOutputGroup |
Indicates the group to which the pseudo-file belongs. If this group is flagged to be suppressed at the CMF level, then the objects in this pseudo-file are not included in the file created using a SaveAs command. |
-
Pseudo-file properties support a variety of workflows. For example, the properties that govern output suppression allow control over what is viewable versus what is included in a generated (SaveAs) file in a development environment.
-
The pseudo-file properties support workflows for which inadvertent additions or modifications of the existing objects within the pseudo-file can be prevented.
-
The SuppressLoad property allows for completely hiding those objects even from viewing.
-
The IsObsolete and the control modification properties, such as ReadOnly, ReadOnlyFile, and WriteDisable, are used to control whether objects can be added to the pseudo-file (IsObsolete) or whether existing objects can be modified or deleted (ReadOnly, ReadOnlyFile, and WriteDisable).