Question: How are teams assigned to Product Lifecycle Management tasks?
Answer: The workflow definition is the primary source of team assignment. You can assign teams at the task level (highest priority), section level (next highest priority), or tab level (lowest priority).
A team can be either:
Definition-assigned
A team can default for a task/section/tab when defining a workflow definition (as defined in Lifecycle Task Maintenance)
A team can be manually overridden for a task/section/tab (during workflow definition setup).
Rule-assigned
A rule can be defined for a task/section/tab (defined in Lifecycle Rule Entry).
When reviewing a workflow definition, you can see the origin of the team assignment. The following hierarchy is used for team assignment:
Team is assigned to the task in the workflow definition.
Team is assigned to the section associated with the task in the workflow definition.
Team is assigned to the tab associated with the task in the workflow definition.
Team is assigned to the task in a workflow rule.
Team is assigned to the section associated with the task in a workflow rule.
Team is assigned to the tab associated with the task in a workflow rule.