Selecting Life Cycle Templates and Initiating Workflow Processes during Received Delivery Import
A life cycle template is considered local to a Windchill installation where it defines and guides any workflow processes initiated on an object. With very few exceptions, it is not desirable to have a workflow process execute on an imported object. As a result, it is important to consider life cycle template mapping prior to importing a received delivery.
 |
Map imported life cycle templates to basic life cycle templates on the target system to avoid initiating a workflow process upon object import. You may consider creating a life cycle template for use with imported objects. While a life cycle template is considered local to the system, it is appropriate to select a life cycle template that maintains the business intent of the source life cycle state. For more information, see Life Cycle Mapping and .
|
If a life cycle state is associated with a workflow, then a package import can cause processes to be initiated in the target context for objects imported into that state. If a package being imported contains multiple iterations of an object revision, the system only checks the life cycle state of the latest iteration to determine if a workflow process needs to be initiated for that object revision.
If a subsequent import of the same object updates the life cycle state, any workflows initiated by a previous life cycle state are terminated. To prevent workflow processes from being automatically terminated, use the wt.workflow.engine.terminateObjectsRunningWorkflows property.
Imported workflow processes and tasks are static lightweight representations of processes and tasks that exist on the source system. The imported processes and tasks are not actionable in the target system. For example, it is not possible to edit or complete an imported workflow task or to suspend or terminate an imported process. You cannot search for an imported process or manipulate it using the Process Manager. Likewise, imported tasks do not show up in the Tasks table in the target context.