VPM Document Modeler Description & Customization |
| Technical Article |
|
This article presents the VPM Document modeler, and explains how to customize it. |
This section first presents the objects representing the VPM Document modeler. Then it describes how this object model view has been translated towards PLM objects based on PLM Core Modeler objects.
The VPM Document model is as follows:
|
The VPM Document model is implemented with PLM Core Object as follows:
 |
The following array shows the links between the conceptual and PLM Core models
| Model Object | PLM Modeler Type | PLM Core Type | Modeler PLM Package |
|---|---|---|---|
| Document | PLMDMTDocument | PLMCoreRepReference | PLM Document |
Customization starts with the PLM package customization [2]. First a new package containing new PLM classes for each "Customizable" PLM class of the modeler PLM package. Then, the UI mask should be customized by either creating a new security mask file or by updating the default one [3].
The PLM Document package is described as customizable since its unique PLM classes is "customizable". However, you should not customize it. In your application only use the provided customization : Document Model sample document package.
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.
No specific rule to customize UI mask file.
|
Version: 1 [Oct 2008] |
Document created |
| Version: 2 [Sep 2009] | Document updated |