Define Additional Life Cycle Roles
Advanced life cycles can have a role associated with a particular life cycle phase.
When an object enters the phase, the associated role is assigned to a participant. You can populate life cycle roles in several ways:
• Map life cycle roles to groups, users, or organizations.
It is not often practical to map life cycle roles directly to participants. Using life cycles and teams together allows role participants to be identified when the phase is reached, rather than making this mapping an explicit part of the life cycle definition.
• Map life cycle roles to team roles.
For example, you can map the life cycle role Promoter to the Product Manager team role. At runtime, the Promoter role is populated with users assigned as product managers.
• Map a life cycle role to an actor. An actor is someone who performs a specific action.
For example, you can map the Creator actor to the Submitter life cycle role for a given life cycle phase. For that phase, the user who created the object would be assigned the Submitter role at runtime.
For more information, see
Team Roles Resolution and
Phase Roles.
Adding Roles
Windchill provides several predefined roles for life cycle templates. The roles object is an enumerated type.
To define additional states, edit the following file:
RolesRB.rbinfo
Newly defined roles are added to the existing roles when you recompile the resource files and deploy the class files to your production environment. For more information, see the following customization topics:
|
|
Removing a value you previously added to an enumerated type (for example, removing a state in the RolesRB.rbinfo resource file), could result in serious runtime error. Do not remove a role unless you are certain there is no reference to it within the system.
As with other resource bundles, roles might be marked as non-selectable to prevent their use in new instances.
|
