Library Modeler Description & Customization

This section first presents the objects representing the Library 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 library model is as follows:

Fig.1 Library Model Objects

• A library is the root classification tree structure which cannot contain items
• A class is an object containing classes and items
• An item can be a PLM Reference or a PLM Representation Reference among a list of pre-defined modelers, or a feature inside a PLM Representation .  This list is available in the article "Library Attachable Object Types" in the Library Management section of the interactive documentation.

The library 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

The following array shows the links between the conceptual and PLM Core models of non customizable class

When a PLM attribute is defined (inside modeler PLM package) some features like its editability criteria, mandatory /optonal option, can be overwriten by UI  mask. You can say this PLM attribute is not writable in Query context, this PLM attribute is mandatory in Create context, this user PLM attribute is not never visible and so one. A set of UI masks form a security mask file. We say security mask because it is associated with these files security information. For a people, and a given context can be associated a security mask.

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.