|
In many cases, it might be easier to use an existing template to create a new life cycle template.
You can use the Save As action available from the Life Cycle Template Administration utility to create a copy of an existing template. Once created, you can then use the life cycle template editor to modify the template properties.
|
Available for Routing | Select this option to include the life cycle in the Route action that is available for packages and from Windchill ProjectLink contexts.
| ||
Enabled | If selected, the life cycle is available for use. A disabled template cannot be assigned to a life cycle-managed object.
| ||
Type | Basic life cycles include a life cycle template, phases, gates, and transitions. Advanced life cycles also define access permissions, and can be mapped to team roles and workflow processes. For more information, see Basic and Advanced Life Cycles. | ||
Name | The life cycle name. Life cycle names must be unique per context. If you enter a name already in use, an error message appears. | ||
Location | The domain and folder in which this life cycle is stored. By default, Windchill stores the template in the System folder for the context in which the template is created. This field can only be modified when a life cycle template is created. To change the location, select Browse to view available cabinets and folders where the life cycle can be stored. | ||
Description | A brief description of the life cycle. | ||
Class | Select the object class to which this life cycle applies. Windchill classes are hierarchical. Therefore, the life cycle applies to the selected class and all of its subclasses. Because you can also directly associate a life cycle with a given subclass, a class can inherit more than one life cycle. |
New life cycles are not available to use until checked in. Use the actions available from the Life Cycle Templates table to check in the template. |