Caution

Removing a value you previously added to an enumerated type (for example, removing a state in the StateRB.rbInfo resource file), could result in serious runtime error. Do not remove a state unless you are certain there is no reference to it within the system.

Access Control for Life Cycle

Administration

The access control rules listed in the following table provide life cycle administrators with permissions needed to manage life cycles and teams, and to move them after they have been created. These rules need to be defined for the domains (or ancestor domains) associated with folders in which life cycle templates and teams will reside.

Best Practices

Site, organization, and application context managers manage life cycle templates.

•Site administrators create, modify, delete, and view life cycle templates in the site context.

•Organization administrators create, modify, delete, and view life cycle templates in the given organization context. Organization administrators can view life cycle templates from the site context.

•Application context managers create, modify, delete, and view life cycle templates in the given application context. They can view life cycle templates from the parent organization context and the site context.

Note

The Life Cycle Template Administration utility is not available to project or program application context managers.

The Life Cycle Template Administration utility displays a table that lists all life cycle templates belonging to the given context, in addition to those belonging to its parent contexts. A column in the table identifies the context owning each life cycle template.

When you create a life cycle template, the system saves the new life cycle template in the System cabinet or folder of the context in which it is created.

Note

When assigning a workflow template to a life cycle template, you see a list of valid workflows. The list of valid workflow templates includes the ones defined in the current context, plus those defined in any parent contexts. Workflow templates defined in a sub-context override and filter out the workflow templates defined in parent contexts having the same name.

The search scope used to locate user-defined groups is determined by the type of administrator doing the search. For more information about the search scope, see Searching for Participants in Administrative Clients on page 261

Life Cycle Support in Windchill ProjectLink

The following table shows the life cycle support in Windchill ProjectLink.

Managing Promotion Processes in Windchill

PDMLink

The decision to promote an object from one state to another often pertains to a business decision. As such, it is important to make sure that products and libraries are set up to allow for the proper approvals to be obtained prior to promotion. For more information, see Understanding Products and Libraries on page 175

For any process template used in the promotion process, users assigned to the particular tasks are obtained from the following:

•The process template itself (the process has a member defined for a specific task)

•The state of the life cycle of the promotion request

•The team instance of the promotion request

The out-of-the-box templates do not define users for the roles defined in the process templates or life cycle templates used by the promotion request.

The team template provided for the promotion request defines the roles Approver and Reviewer; however, no default users are assigned to these roles. The Approver and Reviewer roles should be populated by the context team. For more information, see the teams help.

If you are using a process template for the promotion process that defines roles in addition to Approver and Reviewer, add the roles to the team template used for promotion request creation. You can modify team templates through the Team Administration utility found on the Utilities page for each context. Create a copy of the team template (using the Save As functionality), edit the new template to add any new roles, and then modify the appropriate object initialization rule for the promotion request to point to the new team template in the appropriate context.