A typical reason to use "Assigned" instead of or alongside resources is when a resource represents a team, but it's important to know who on the team is handling a job for that team.
"Assigned" functions like a resource, but it is linked only to a single instance of the job and is therefore not automatically associated when a scheduled job is repeated. In other words, it acts as a temporary resource.
Example
We have three technicians and a job linked to our "Technician" resource. However, we want to assign one of the technicians to the job. To do this, we link the "Technician" resource as a "Resource" and assign one of the three technician resources as "Assigned."
In this example, we expect Technician Jørgen to handle the task. However, we can use this specification for purposes such as Analytics and Dashboards. For instance, we might want to ensure that all our technicians have an equal workload or that tasks are not assigned to technicians when they are on vacation or otherwise unavailable.
Comments
0 comments
Article is closed for comments.