Folder Modeler Description & Customization

This section first presents the objects representing the Folder modeler. Then it describes how this object model view has been translated towards PLM objects based on PLM Core Modeler objects. You will see the description of each PLM package defining these PLM objects.

The folder model is as follows:

Fig.1 Folder Model Objects

• A root folder is a folder which does not have a parent and cannot contain items
• A folder is an object containing folders and items, it necessarily has a parent folder or root folder
• An item can be a PLM Reference or a PLM Representation Reference among a list of pre-defined modelers.  This list is available in the article "Folder Attachable Object Types" in the Folder Management section of the interactive documentation.

The folder model is implemented with PLM Core Object as follows:

Fig.1 PLM Core Objects

The following array shows the links between the conceptual and PLM Core models

Customization

When a PLM attribute is defined (inside modeler PLM package) some features like whether it is editable, and whether it is mandatory or optional, can be overwritten by UI  mask. You can specify that a PLM attribute is not writable in Query context, mandatory in Create context, or that this user PLM attribute is never visible and so on. A set of UI masks form a security mask file. We say security mask because it is associated with these files security information. A security mask can be associated to a person, and a given context.

 If you want create a new security mask file, you should provide a UI mask for all the "AsIs" modeler PLM packages and for each customization of the "Customizable"  modeler PLM package. 

Rules to respect for a new UI mask creation

No specific rule to customize UI mask file.

Folder does not support the change maturity command, therefore any policy change which apply to Folders and Root Folders should not forbid anything solely based on the status.