Folders act as a logical grouping of model entities.
A folder does not own its member entities. Entities contained in a folder continue to be owned by the folder's parent entity. This effectively means that an entity can be a member of more than one folder.
Adding a new entity to a folder is essentially the same as adding the entity to the folder's parent.
Entities that are members of the folder's parent can be added as existing entities to the folder.
Note: Agile Business Suite folders are not the same as the virtual folders that can be added outside the model hierarchy using the New Folders button on the Class View toolbar.
The default window is Members. Refer to Group Properties for properties applicable to Folders.
If you delete a folder and it contains other elements, you can optionally delete the folder's members at the same time. If you do not delete the folder's members, they are placed under the model when the folder is deleted.
The IsUnique model property of Folders ensures all members do not exist in other folders. This is a Boolean value where true applies the uniqueness constraint. A nested Folder assumes the setting of the owning Folder. This property does not apply to Diagrams.
For MCP, any folder with IsUnique property set to True must have a name that does not exceed 27 characters in length.
MCP runtime applies a build rule to cluster all non-persistent, generic or primitive attributes contained within the Segment Folder into a block. All persistent Segment attributes are made a part of a GLB-WORK block, and all other Segment attributes will be a part of a GLB-SDS block.
If the segment folder does not have the unique property set or the folder is not under the segment, it is not treated as a GSD block.