Role Resolution Example

Basic Administration > Managing User Participation > Team Template Administration > Team Roles Resolution > Role Resolution Example

This section contains an example of how roles might be resolved for a document object that is associated with a team and a life cycle.

The life cycle template contains the following roles:

	1st Phase	2nd Phase	3rd Phase	4th Phase
Submitter	Creator	Not in this phase	Not in this phase	Not in this phase
Promoter	Not in this phase	Not in this phase	Not in this phase	Not in this phase
Reviewer	Design Engineer	Project Manager Prod Marketing	QA Engineer Pubs	Jane Design Engineer Project Manager QA Engineer
Observer	Not in this phase	Team Leader	Not in this phase	Not in this phase

The team template contains the following roles/participants:

• Design Engineer--Kristin

• Project Manager--Dave, John

• QA Engineer--Sean, Sachin

• Team Leader--Tom, Beth

The context team contains the following roles/participants:

• Design Engineer--Kristin, Flavio, Bill, Galen

• Project Manager--Dave, John

• Prod Marketing--Chris

• QA Engineer--Sean, Sachin, Iyrena

• Pubs--April, Diane, Muriel

• Team Leader--Tom, Beth

First Phase

An object is created by Jeff and assigned to the life cycle template and team template above. The context team is listed above. The team resolves to the following participants for the first phase when the wt.team.re-resolveRoles property is set as shown in the table below:

	Default (property set to false)	Property set to true
Design Engineer	Kristin, Flavio, Bill, Galen	Kristin, Flavio, Bill, Galen
Project Manager	Dave, John	Dave, John
QA Engineer	Sean, Sachin, Iyrena	Sean, Sachin, Iyrena
Team Leader	Tom, Beth	Tom, Beth
Reviewer	Kristin	Kristin
Submitter	Jeff	Jeff
Promoter

Observations:

• Participants are added during the team template/life cycle role resolution.

• Participants (Flavio, Bill, and Galen) were added to the design engineer role from the context team.

• Roles from the context team that do not exist in the team are not added (in this case, Prod Marketing and Pubs).

• The life cycle Reviewer role is mapped to Design Engineer, but since the context team roles are not added until after the team template/life cycle role resolution is completed, the people in the Design Engineer role are not members of the Reviewer role.

Second Phase

The object is promoted to the second phase.

	Default (property set to false)	Property set to true
Design Engineer	Kristin, Flavio, Bill, Galen	Kristin, Flavio, Bill, Galen
Project Manager	Dave, John	Dave, John
QA Engineer	Sean, Sachin, Iyrena	Sean, Sachin, Iyrena
Team Leader	Tom, Beth	Tom, Beth
Reviewer	Kristin	Dave, John
Submitter	Jeff	Jeff
Promoter
Observer	Tom, Beth	Tom, Beth

Observations are the same as for the first phase.

Third Phase

The team templates and context teams are modified.

The team template contains the following roles/participants:

• Design Engineer--Kristin, Flavio

• Project Manager--Dave, John

• QA Engineer--Sean, Sachin, Dan

• Integration--Mark

The context team contains the following roles/participants:

• Design Engineer--Kristin, Flavio, Jeff, Michelle

• Project Manager--Dave, John

• Product Marketing--Chris

• QA Engineer--Sean, Sachin, Iyrena

• Pubs--April, Diane, Muriel

• Team Leader--Tom, Beth

• Observer--Jane, Lynn

	Default (property set to false)	Property set to true
Design Engineer	Kristin, Flavio	Kristin, Flavio, Jeff, Michelle
Project Manager	Dave, John	Dave, John
QA Engineer	Sean, Sachin, Iyrena	Sean, Sachin, Iyrena
Reviewer	Kristin	Sean, Sachin, Dan
Submitter	Jeff	Jeff
Promoter
Observer	Tom, Beth	Tom, Beth, Lynn, Jane
Team Leader	Tom, Beth	Tom, Beth

Fourth Phase

A set state sets the object to the fourth phase.

	Default (property set to false)	Property set to true
Design Engineer	Kristin, Flavio	Kristin, Flavio, Jeff, Michelle
Project Manager	Dave, John	Dave, John
QA Engineer	Sean, Sachin, Iyrena	Sean, Sachin, Iyrena
Reviewer	Kristin	Jane, Kristin, Flavio, Dave, John, Sean, Sachin, Dan
Submitter	Jeff	Jeff
Promoter
Observer	Tom, Beth	Tom, Beth, Lynn, Jane
Team Leader	Tom, Beth	Tom, Beth

Observations:

The Design Engineer and Observer do not exist in the life cycle template for the fourth phase, but they do exist in the team template and context team. So even if the property is set to true, these roles are not removed from the runtime team.