{"id":2974284,"date":"2026-07-06T15:45:52","date_gmt":"2026-07-06T22:45:52","guid":{"rendered":"https:\/\/www.esri.com\/arcgis-blog\/?post_type=blog&p=2974284"},"modified":"2026-07-06T15:45:52","modified_gmt":"2026-07-06T22:45:52","slug":"orchestrating-end-to-end-field-operations-with-arcgis-workflow-manager","status":"publish","type":"blog","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/workflow-manager\/field-mobility\/orchestrating-end-to-end-field-operations-with-arcgis-workflow-manager","title":{"rendered":"Orchestrating End-to-End Field Operations with ArcGIS Workflow Manager"},"author":313862,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_acf_changed":false,"_searchwp_excluded":""},"categories":[37501,37101,23261],"tags":[682761,765562,38701,24511,344152],"industry":[],"product":[760392],"class_list":["post-2974284","blog","type-blog","status-publish","format-standard","hentry","category-administration","category-announcements","category-field-mobility","tag-arcgis-field-maps","tag-arcgis-workflow-manager","tag-data-collection-and-management","tag-field-data-collection","tag-field-operations","product-workflow-manager"],"acf":{"authors":[{"ID":313862,"user_firstname":"Robert","user_lastname":"Smith","nickname":"Robert A. Smith","user_nicename":"rsmith","display_name":"Robert Smith","user_email":"rsmith@esri.com","user_url":"","user_registered":"2022-06-27 18:30:02","user_description":"Robert is a Product Engineer on the ArcGIS Workflow Manager team. Outside of his work, Robert loves being outdoors and exploring Southern California.","user_avatar":""},{"ID":443994,"user_firstname":"Artiom","user_lastname":"Dolghi","nickname":"Artiom Dolghi","user_nicename":"adolghiesri-com_esriinc","display_name":"Artiom Dolghi","user_email":"adolghi@esri.com","user_url":"","user_registered":"2026-03-09 18:53:03","user_description":"Artiom is a Product Engineer, working on documentation for ArcGIS Workflow Manager.","user_avatar":""}],"short_description":"Learn how to integrate ArcGIS Workflow Manager and ArcGIS Field Maps for seamless field-to-office workflows.","flexible_content":[{"acf_fc_layout":"image","image":{"ID":2603452,"id":2603452,"title":"Data-workflow-manager-online-banner","filename":"Data-workflow-manager-online-banner.jpg","filesize":112519,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner.jpg","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/workflow-manager\/data-management\/edit-data-offline-with-arcgis-workflow-manager\/data-workflow-manager-online-banner","alt":"","author":"334322","description":"","caption":"","name":"data-workflow-manager-online-banner","status":"inherit","uploaded_to":2371332,"date":"2024-11-26 01:06:44","modified":"2024-11-26 01:06:44","menu_order":0,"mime_type":"image\/jpeg","type":"image","subtype":"jpeg","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":826,"height":465,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner-213x200.jpg","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner.jpg","medium-width":464,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner.jpg","medium_large-width":768,"medium_large-height":432,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner.jpg","large-width":826,"large-height":465,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner.jpg","1536x1536-width":826,"1536x1536-height":465,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner.jpg","2048x2048-width":826,"2048x2048-height":465,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner.jpg","card_image-width":826,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/Data-workflow-manager-online-banner.jpg","wide_image-width":826,"wide_image-height":465}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

Administrators coordinating both field and back-office work may find tracking difficult, especially when tasks are assigned across multiple crews and at different stages of completion. Managing task updates and communication across multiple points of contact can be challenging and time-consuming.\u00a0 ArcGIS Field Maps<\/a> is essential for organizations that conduct field operations and deal with these issues. It provides a comprehensive app for viewing maps, collecting data for activities such as maintenance records and inspections, completing tasks, and maintaining situational awareness in the field. Your field crews use Field Maps to receive and complete on-site work, while the data they collect is passed to the back office for next steps such as quality control, ingestion into the authoritative database, or other related work.<\/p>\n

ArcGIS Workflow Manager<\/a> is a centralized work management system for ArcGIS that helps coordinate work across products, systems, and teams. When Field Maps and Workflow Manager are used together, organizations can manage field operations from a single system, simplifying workflows by reducing handoff gaps, lost paperwork, and manual data re-entry between systems.<\/p>\n

With the June 2026 update of ArcGIS Online, Workflow Manager includes a new Create Field Maps Task<\/a> step and the ability to configure webhook connections<\/a>. These enhancements address the challenges described above by connecting workflows directly to Field Maps, so field work can be created and tracked automatically. Together, these capabilities serve two main purposes in your workflows:<\/p>\n

    \n
  1. Create a task for field crews from an existing job in Workflow Manager.<\/li>\n
  2. Automatically continue back-office work after field work is complete.<\/li>\n<\/ol>\n

    Ready to streamline work between the field and office? Let\u2019s dive in!<\/p>\n

    Background: Create Field Maps Task step, webhook connections, and webhook dependencies<\/strong><\/h3>\n

    Let\u2019s take a closer look at how the Create Field Maps task step, webhook connections, and webhook dependencies work together to easily orchestrate processes across ArcGIS Field Maps and ArcGIS Workflow Manager.<\/p>\n

    The Create Field Maps Task step<\/strong><\/p>\n

    This step\u2019s name states its purpose precisely. When you run the Create Field Maps Task step, it will\u00a0create a task<\/a>\u00a0in the task-enabled layer you are using to manage field work, which will correspond with the Workflow Manager job you are working on.\u00a0 The Create Field Maps Task step passes custom information to the task-enabled layer, to make the handoff from your back-office team to your field crew as seamless as possible.\u00a0 Assigned crew members can then carry out the task and report on their work using the ArcGIS Field Maps app.<\/p>\n

    Webhook connections<\/strong><\/p>\n

    Webhooks<\/em> are a lightweight system for web applications to communicate with one another.\u00a0 In\u00a0ArcGIS Online<\/a>, you can configure webhooks to share information and automatically trigger actions across your organization\u2019s users and content.\u00a0 Webhook connections<\/a> establish a protocol for direct communication between feature services and your workflow item \u2013 which feature service to listen to, which events will trigger a message, and what credentials Workflow Manager will use to carry out subsequent actions.<\/p>\n

    Creating webhook connections to your task-enabled layers enables the Create Field Maps Task step to block the subsequent step until field work is complete.\u00a0 This gives you greater control and synchronization between field crews and your back-office team.\u00a0 The back-office team is prevented from starting their portion of the work prematurely, and at the same time they don\u2019t have to remember to manually resume the job once field work is done.<\/p>\n

    Webhook dependencies<\/strong><\/p>\n

    Webhook dependencies<\/a>\u00a0are the mechanism the Create Field Maps Task step uses to block the subsequent step.\u00a0 If you configure the step to add a webhook dependency, the next step will be blocked until the status of the field work meets a set of release-conditions you have configured.\u00a0 Workflow Manager will receive updates on the field work through the webhook connection.\u00a0 When the task-enabled layer sends a webhook payload to Workflow Manager which meets your conditions, the dependency will be automatically released, and back-office work will proceed seamlessly.<\/p>\n

    The Workflow Manager Advanced organization extension is required for you to create webhook connections, which are needed for webhook dependencies to be available with the Create Field Maps Task step. \u00a0If you have the Workflow Manager Standard organization extension, you will still be able to configure and run the Create Field Maps Task step, just without webhook dependencies.<\/p>\n

    Let\u2019s explore a real-world scenario.<\/p>\n

    Use Case: Inventory Management<\/strong><\/h3>\n

    You are a regional office manager at a company that supplies and maintains Automated External Defibrillators (AEDs) for healthcare facilities across the country.\u00a0 When customers need their AEDs inspected or replaced, they submit a request to the management company using an ArcGIS Survey123 form. This triggers the creation of a job in Workflow Manager for the management company to assign to the appropriate regional office, review the incoming request and provide additional details as necessary before dispatching a field crew to the site. Once the crew completes all assigned tasks and updates the status in Field Maps, the work transitions back to the regional office to perform the necessary steps to close out the job and send appropriate notifications.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2974289,"id":2974289,"title":"Field Inspection Workflow","filename":"Picture1-3.png","filesize":73953,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/workflow-manager\/field-mobility\/orchestrating-end-to-end-field-operations-with-arcgis-workflow-manager\/picture1-176","alt":"","author":"313862","description":"","caption":"","name":"picture1-176","status":"inherit","uploaded_to":2974284,"date":"2026-07-01 01:24:23","modified":"2026-07-01 01:24:41","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":624,"height":205,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3.png","medium-width":464,"medium-height":152,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3.png","medium_large-width":624,"medium_large-height":205,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3.png","large-width":624,"large-height":205,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3.png","1536x1536-width":624,"1536x1536-height":205,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3.png","2048x2048-width":624,"2048x2048-height":205,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3.png","card_image-width":624,"card_image-height":205,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture1-3.png","wide_image-width":624,"wide_image-height":205}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    Check out this short demonstration to see this scenario in action!<\/p>\n"},{"acf_fc_layout":"kaltura","video_id":"1_olcwbsot","time":false,"start":0},{"acf_fc_layout":"content","content":"

    This same pattern applies to numerous situations, like preventative maintenance, scheduled inspections, storm cleanup, asset management, and more!\u00a0 Because the underlying pattern and required steps are similar, once you\u2019ve set up the workflow for one use case, extending it to the others is straightforward.<\/p>\n

    Now, let\u2019s dig into how to set up this process in Workflow Manager.<\/p>\n

    1. Receiving the customer request<\/strong><\/h3>\n

    In the demonstration, you saw that the customer submitted an AED inventory request using a Survey123 form.\u00a0 A webhook was configured on the regional office\u2019s ArcGIS Survey123 website, which enabled the survey submission to create a job in the workflow item automatically.\u00a0 To learn more on how to set this up, please visit\u00a0this blog<\/a>.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2974292,"id":2974292,"title":"Survey123 Webhook","filename":"Picture2-4.png","filesize":55865,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/workflow-manager\/field-mobility\/orchestrating-end-to-end-field-operations-with-arcgis-workflow-manager\/picture2-113","alt":"","author":"313862","description":"","caption":"","name":"picture2-113","status":"inherit","uploaded_to":2974284,"date":"2026-07-01 01:29:56","modified":"2026-07-01 01:30:07","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":753,"height":321,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4.png","medium-width":464,"medium-height":198,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4.png","medium_large-width":753,"medium_large-height":321,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4.png","large-width":753,"large-height":321,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4.png","1536x1536-width":753,"1536x1536-height":321,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4.png","2048x2048-width":753,"2048x2048-height":321,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4.png","card_image-width":753,"card_image-height":321,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture2-4.png","wide_image-width":753,"wide_image-height":321}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    The advantage of this setup is that the process for initiating the request is fully customer-facing, and there is no opportunity for it to accidentally be missed or forgotten. Depending on your use case, there are many other approaches to initiating the process. Jobs can be created on-demand<\/a> in the back-office, scheduled automatically<\/a> to fulfill a recurring need, or generated programmatically using the Workflow Manager APIs.<\/p>\n

    2.\u00a0 Reviewing the request<\/strong><\/h3>\n"},{"acf_fc_layout":"image","image":{"ID":2974293,"id":2974293,"title":"Field Submission Workflow","filename":"Picture3-4.png","filesize":38712,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/workflow-manager\/field-mobility\/orchestrating-end-to-end-field-operations-with-arcgis-workflow-manager\/picture3-99","alt":"","author":"313862","description":"","caption":"","name":"picture3-99","status":"inherit","uploaded_to":2974284,"date":"2026-07-01 01:31:09","modified":"2026-07-01 01:31:24","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":470,"height":483,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4.png","medium-width":254,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4.png","medium_large-width":470,"medium_large-height":483,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4.png","large-width":470,"large-height":483,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4.png","1536x1536-width":470,"1536x1536-height":483,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4.png","2048x2048-width":470,"2048x2048-height":483,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4-452x465.png","card_image-width":452,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2026\/06\/Picture3-4.png","wide_image-width":470,"wide_image-height":483}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"

    This is where the work begins at the regional office and where our configured workflow guides the user through a series of steps to review the submission.\u00a0 The review process consists of the first six steps enclosed in the red box in the above diagram.<\/p>\n