"Assigned to" is not mandatory in Workforce

ErikaJimenez_Rivera1

The parameter "assigned to" is not mandatory. Therefore, when the dispatcher is assigning a task, he can create the assignment without assigning it to an user. I know he can assign to the user later. However, this is a problem for a client that is currently using Workforce. And he asked if it is possible that this parameter is mandatory so he does not forget to assign to the user before creating the task.

So, my question is can we configure workforce so this parameter is mandatory?

or is there a reason this should not be mandatory?

 

 

Anonymous User

I can think of a few reasons why this field would not be mandatory for all workforce projects:

- we have 50+ workers for a 24/7 operation and each individual does not receive their own device

- we pair Quick Capture with workforce and sometimes see 100+ assignments in a single day. The dispatcher can't spend their whole day assigning these to individual workers.

- sometimes we want field staff to use field maps to select and close (complete) multiple assignments at once rather than having to select them all individually in workforce