With ArcGIS Workforce retiring, and replaced with Tasks within the Field Maps App - what are we supposed to provide for our dispatchers for Task Assignment?! Is there an equivalent to Workforce for this? The documentation on this is super limited at this point.
I understand there is the Field Maps Designer for deploying this, however, this is for the technical GIS staff to deploy. The solution I require is something for dispatchers to assign and manage work assignments (tasks) for mobile crews.
Did Esri just abandon this component of ArcGIS Workforce and require users to develop it on their own?
Anyone in the know, please help!
Cheers,
Mike
Hi @MDBowser ,
Because Tasks work with a single hosted feature layer instead of the multiple layers needed for Workforce, the layer can easily be brought into a variety of editing clients for dispatching. You can use the Web Editor, Experience Builder, Map Viewer, ArcGIS Pro, Field Maps, or a variety of Instant Apps (such as Manager or Sidebar) to create a custom dispatching experience to suit your needs. This will also allow you to leverage forms and arcade to streamline and further customize your dispatching process.
If you have any specific dispatching needs you're trying to achieve let me know and we can offer some more specific guidance.
Chris
Hey Chris,
Thanks for your reply. I guess I understand the concept, however wouldn't it make sense for Esri to have put together a dispatching instant app or experience builder template to facilitate this transition for users that have been utilizing the workforce dispatching application? Something that can have a consistent look and feel, provide at least parity to the functionality of workforce, so they are not left hanging with a new project of developing their own? I think this is especially important when there is such a short timeline for deprecation. Perhaps there is something out there already you recommend or you can provide this feedback to the project manager of this functionality? Perhaps you can loop in Esri's Liz Armstrong into this thread?
Hi there,
Tasks is very flexible framework, as Chris mentioned, and we have a range of options for you to create custom dispatching experiences that match your custom tasks workflows.
We do have a great option to get up and running immediately. Our Instant Apps' Manager template provides a dispatching experience that you can very quickly spin up in less than 5 minutes to use for dispatching tasks.
Give it a try and see what you think. Happy to take down any specific feedback about your dispatching needs.
Also, I want to take this opportunity to clarify something. Our deprecation notices give customers a "heads up" that we will be retiring the product. In our deprecation notice, we outline the retirement dates which are with ArcGIS Online in the Q3 2026 update and from ArcGIS Enterprise 12.2 in the Q3 2026 release. Hopefully this provides some clarification about how much time you will have to transition from Workforce to using tasks in Field Maps!
Liz,
Wanted to let you know I have found the manager instant app particularly useful, our staff has been able to use it without issue.
It would be awesome if you could configure the filters in the dispatch map to be 1:1 with the filters created in the Field Maps Designer. As of now, I only am able to filter by extent (which is still useful).
HI Liz,
Thank you for your reply. Do you have a demo or video of sorts of the manager instant app used in a dispatching context? I did deploy this and had a look, and on initial glance did not look very useful from a dispatching perspective - this looks mostly geared towards reviewing attribute tables. I do not see here one would setup creating and assigning tasks to mobile workers.
A side question: will there be functionality to assign a task to multiple workers?
Thank you again for your help!
Mike
Thank you for sharing. Would you mind sharing your use cases for why assigning tasks to multiple workers would be helpful?
One example of how we're currently using tasks is at our city cemetery. We have two full-time field workers who often work together on assignments. When new tasks come up, they're typically not specific to one individual, so we end up leaving them marked as "unassigned"—which, frankly, gets frustrating.
It would be much more efficient if we could assign tasks to both workers simultaneously. That way, instead of having them filter their Field Maps for unassigned tasks, they could just see what's relevant to them directly.
Hi @Laura,
While there is no way to, for instance, pick multiple users from a drop-down list as the assignee, it is possible to assign tasks to multiple assignees with some changes to the task layer and the task configuration.
Essentially, you can create a field that contains all of the assignee names, and use a task filter that looks for the current user’s username anywhere in the field. To do it:
- Create a text field called “all_assignees” or similar
- When creating or assigning tasks, populate that field with the names of all mobile workers who need to see the task, i.e. “mobile_worker_1, mobile_worker_2, mobile_worker_4” etc.
Think about how this should work from the dispatching side. Maybe you use templates for the different options, maybe you use calculated values based on a “Crew” field so the dispatcher can pick the crew and the crew usernames are automatically added to the field. Maybe you use arcade to intersect with a site boundary and assign the workers that way. There are a lot of ways to automate creation of this list to keep dispatchers from having to enter names manually, it will really depend on your workflow and data.
- Create your task filter. You could edit the “Assigned to Me” filter, or create a new one. The top filter in the list will be the default filter when opening the map. Use the expression:
all_assignees like ‘%CURRENT_USER%’
Note that `all_assignees` is the example field name I used above, so use whatever field you created to hold the list of names.
This will result in any person listed in the field seeing the task in their list when they open the app
After that, any additional changes to the tasks configuration will depend on how you want things to work. Would the workers still pick up tasks individually? Or would they always tackle them as a team? You may want to adjust the “pickup” action accordingly to only change the status and not the assignee.
I’m happy to go over things in more detail if this looks like a solution that would work for you.
Chris