|
Feature
|
Support Level
|
Notes
|
|
Life cycle template definition
|
Full
|
Organization administrators may create, edit, move, and delete life cycles for their organization.
|
|
Life cycle-managed object support
|
Partial
|
Only document and part items are supported.
|
|
Phases
|
Full
|
|
|
Gates
|
Full
|
|
|
Default life cycles
|
Partial
|
The following default life cycles are supported out-of-the-box: Default, Basic, Approval, Review, and Release.
|
|
Workflow association
|
Full
|
Workflow templates must be defined in the organization and are available for reference at a life cycle phase or gate.
|
|
Roles
|
Partial
|
Roles must be defined in the project or program context.
When routing a life cycle managed object in Windchill ProjectLink, only the members of the context team roles that match the life cycle phase roles are included in the life cycle team. The entire context team is no longer pulled into the life cycle team.
This is the default behavior as defined in the following property:
wt.team.addEntireContainerTeam
A message appears thrown if a user tries to create an advanced life cycle template using the Life Cycle Template Administration utility and does not associate a workflow template to the life cycle phases or gates. In this case, the message requests the user to change the life cycle template from advanced to basic for better performance and scalability.
|
|
Role-based access control
|
None
|
Access rules defined for objects in the project or program context take precedence. By default, members of the project or program manager group have full access to all objects in the project or the program. The life cycle access rules by role for each phase and gate are additive. This means access rights can be added for each role only at each phase and gate.
|
|
Life cycle template import export
|
Partial
|
There is no organization association with the imported or exported template so the life cycle import and export folder should be cleared between uses.
|
|
Access to current life cycle state
|
Partial
|
The life cycle state is provided on the information page for the object.
|
|
Set life cycle state
|
Full
|
Object owners and project managers can set the life cycle state for a document or part with the Set State action.
|
|
Access to maturity history
|
None
|
The maturity history for a part or document is not available.
|
|
Queries based on life cycle state
|
None
|
|
|
Access to running process through life cycle
|
None
|