<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Reject Completed Assignments in ArcGIS Workforce Ideas</title>
    <link>https://community.esri.com/t5/arcgis-workforce-ideas/reject-completed-assignments/idi-p/926513</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many workflows assign a task, receive a result, then either approve or reject it. If there was a way to basically just edit the status field in the assignments table, as a Dispatcher, it would greatly apply to many workflows in many industries. This is technically possible manually, by going through the feature service, and setting the Status field from "Completed" to "Assigned". But obviously having this capability through Workforce would be much better. &lt;BR /&gt;A rejection of an assignment prompts the mobile worker to re-do the work associated with assignment. Specifically, this would greatly help with Survey123 integrations, where forms follow this workflow:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Assignment by Dispatcher&lt;/LI&gt;&lt;LI&gt;Submission by Mobile worker&lt;/LI&gt;&lt;LI&gt;Rejection/Approval by a Dispatcher.&lt;/LI&gt;&lt;LI&gt;Re-submission by Mobile worker (if rejected)&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 18 Aug 2017 13:37:32 GMT</pubDate>
    <dc:creator>deleted-user-st4HsVxccxgs</dc:creator>
    <dc:date>2017-08-18T13:37:32Z</dc:date>
    <item>
      <title>Reject Completed Assignments</title>
      <link>https://community.esri.com/t5/arcgis-workforce-ideas/reject-completed-assignments/idi-p/926513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Many workflows assign a task, receive a result, then either approve or reject it. If there was a way to basically just edit the status field in the assignments table, as a Dispatcher, it would greatly apply to many workflows in many industries. This is technically possible manually, by going through the feature service, and setting the Status field from "Completed" to "Assigned". But obviously having this capability through Workforce would be much better. &lt;BR /&gt;A rejection of an assignment prompts the mobile worker to re-do the work associated with assignment. Specifically, this would greatly help with Survey123 integrations, where forms follow this workflow:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Assignment by Dispatcher&lt;/LI&gt;&lt;LI&gt;Submission by Mobile worker&lt;/LI&gt;&lt;LI&gt;Rejection/Approval by a Dispatcher.&lt;/LI&gt;&lt;LI&gt;Re-submission by Mobile worker (if rejected)&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Aug 2017 13:37:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-workforce-ideas/reject-completed-assignments/idi-p/926513</guid>
      <dc:creator>deleted-user-st4HsVxccxgs</dc:creator>
      <dc:date>2017-08-18T13:37:32Z</dc:date>
    </item>
    <item>
      <title>Re: Reject Completed Assignments</title>
      <link>https://community.esri.com/t5/arcgis-workforce-ideas/reject-completed-assignments/idc-p/926514#M64</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for submitting this idea &lt;A href="https://community.esri.com/migrated-users/23921"&gt;Jeremy&lt;/A&gt;! I've gone ahead and removed Survey123 from the categories, since this idea appears to be specific to Workforce and assignment statuses. In your current workflows, how are you handling this need for approval/rejection of assignments by the dispatcher?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Mar 2018 23:47:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-workforce-ideas/reject-completed-assignments/idc-p/926514#M64</guid>
      <dc:creator>ScottPrindle</dc:creator>
      <dc:date>2018-03-22T23:47:02Z</dc:date>
    </item>
  </channel>
</rss>

