PTC recommends that you use a basic life cycle for improved performance and scalability. Any particular context can have a mix of basic and advanced life cycles associated with objects. Ideally, an object is associated with an advanced life cycle only when necessary, such as when you route an object in Windchill ProjectLink. |
Life Cycle Feature | Basic | Advanced | ||
Configure life cycle properties, including: • Name • Where the template is stored and is therefore accessible. • The object class to which the life cycle applies. | ||||
Life cycle phases to represent object states. | ||||
Transition rules to define how an object can move from one life cycle phase to another. | ||||
The option to make the life cycle available for routing. When this option is selected, you can include the life cycle in the Route action that is available for packages and from Windchill ProjectLink contexts. | ||||
The ability to configure roles for each life cycle phase, and map participants to these roles. | ||||
The ability to configure access control permissions for any defined role. The rules apply to the primary business object.
| ||||
The ability to associate a workflow process with a life cycle phase or gate. |