PLM Knowledge Template Modeler Description & Customization |
| Technical Article |
|
This article presents the PLM Knowledge Template modeler. |
This section first presents the objects representing the PLM Template modeler. Then it describes how this object model view has been translated towards PLM objects based on PLM Core Modeler objects.
The PLM Template modeler is not customizable itself but is dependant from modelers it manipulates and that have to be customized. A business logic is used in the PLM Template modeler to adapt to manipulated modelers customization. We also detail here some conditions that have to be fulfilled so that the PLM Template modeler works smoothly.
The PLM Template modeler is a modeler that enables the user to reuse designs in a very productive way. It defines a duplication specification that will later enable the user to duplicate existing designs with modifications of the duplicated PLM components.
As of today, only the PRODUCT modeler is integrated into PLM Templates. It will evolve in coming releases.
The PLM Template modeler duplicates some PLM Components defined in its specifications. This duplication is done on the server side. One has to ensure that new identifiers are unique. A business logic has been defined to handle the modification of the identifiers during this duplication.
To find out more about the associated Business Logic, see the How to Implement the PLM Template Naming Business Logic? topic.
The PLM Template instantiation command duplicates components on server side. If the user wants to cancel the command or if he does not want to save the instantiation result, the new components created in database should be deleted from the database. So the user must have the right to delete components he owns for the proper behavior of this command.
No customization is possible
| Version: 1 [July 2010] | Document created |