Task Modeler Description & Customization

This section first presents the objects representing the Task 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.

Task modeler provide task capabilities within CATIA V6 environment with ability to reference PLM objects.

This is summarized in the following UML schema:

Fig.1 Task, Model

Only object of this modeler is the task object.  A task can be break down into sub-task (also called child task). All PLM object needed to perform a task are referenced by it. Several kind of referencing are available:

• Attachement attachement are objects manually "attached" to task. Attachement are not affected by the task; they are merely there for reference.
• Inputs objects that need to be modified They are manually associated to the task.
• Output modified objects They are manually associated to the task.
• Peer Related Tasks (nut not Parent-child)

The Task 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 objects:

This section lists and describes the PLM Opening ID implemented by the following PLM classes of the Task modeler.

PLMTaskAction, Implemented Business Logic

This part consist in to create a new package when the modeler PLM package must be customized.

Package PLM Task for CATIA V6 must be  fully customized.

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.

For each customized Modeler PLM package, at least one UI mask file must be created (for the default security mask ), since it must contain the new PLM Attributes. When you use the tool to create a customization, a default UI mask file is provided taken into account the added PLM attributes. You can modify  the default file to introduce your change .>

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.

You can yourself integrate your business logic for each customization of:

• PLMTaskAction

PLM Opening ID
PLMAttributesValuationCheck
PLMIdentificationInitialization