Assignments: who does each task
Sytex doesn't make you pick the person task by task. The template defines named assignments —process roles— that are resolved once when the workflow is created and propagate to every task that uses them.
Named assignments
Think of assignments as process roles: "Contractor," "Field technician," "Quality supervisor." Each has a type: staff (person) or supplier. Tasks point to the assignment, not to the person.
When the workflow is created, each assignment is resolved once to a specific person or supplier. From there:
- Every task pointing to that assignment is assigned.
- Changing the assignment re-propagates the change to every linked task, in a single operation. Swapping a contractor mid-build is one change, not fifty.
Create them before the tasks: that way they're ready to pick as you configure each task.
Ways to assign a task
- Automatic staff assignment: who executes the task.
- Automatic supervisor / requester assignment: who supervises and who is listed as the requester.
- Automatic supplier assignment (+ executed by supplier ): which supplier runs it.
- Role assigned to the task: assigns by role instead of by person; it lands in the inbox of whoever holds that role. There are also a supervisor role and an acceptance role .
- Assign to the site's responsible role: resolves the person from the workflow site's owner.
Which to use
- Fixed person: only if it truly is always the same one.
- Role: when the work belongs to a team.
- Named assignment: when the person changes per workflow but is the same across several tasks of the same workflow. It's the most common and most powerful case.
To keep supplier users from moving statuses, use Restrict status change for suppliers on the task.