<?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 Allow overlapping areas by job type in Workflow Manager in ArcGIS Workflow Manager Ideas</title>
    <link>https://community.esri.com/t5/arcgis-workflow-manager-ideas/allow-overlapping-areas-by-job-type-in-workflow/idi-p/940791</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;WMX provides the following LOI overlapping options as system settings:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;allow&lt;/LI&gt;&lt;LI&gt;disallow&lt;/LI&gt;&lt;LI&gt;disallow by job type&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In our shop we do not allow overlapping areas but there are special cases that require to work on jobs inside other job areas.&amp;nbsp; The main job is mainly created to identify and define the overall LOI of the "mini-jobs" to be work inside that extent.&amp;nbsp; Due to the nature of those jobs and to be able to work more efficiently they need to allow overlapping AOIs.&amp;nbsp; So we like to have the option to allow overlapping areas by job type but allowing to overlap with other job types so we can still have the main extent delimited or somehow parent and child jobs be able to share an LOI.&amp;nbsp; Right now we have the main LOI created in job type A and corresponding jobs (job type B) as child jobs but either skipping AOI creation (not desired but the application allows it, which is a big data security flaw) or creating AOI as they are available in the main extent (which delay our operations).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 May 2019 15:26:09 GMT</pubDate>
    <dc:creator>Ulises</dc:creator>
    <dc:date>2019-05-07T15:26:09Z</dc:date>
    <item>
      <title>Allow overlapping areas by job type in Workflow Manager</title>
      <link>https://community.esri.com/t5/arcgis-workflow-manager-ideas/allow-overlapping-areas-by-job-type-in-workflow/idi-p/940791</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;WMX provides the following LOI overlapping options as system settings:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;allow&lt;/LI&gt;&lt;LI&gt;disallow&lt;/LI&gt;&lt;LI&gt;disallow by job type&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In our shop we do not allow overlapping areas but there are special cases that require to work on jobs inside other job areas.&amp;nbsp; The main job is mainly created to identify and define the overall LOI of the "mini-jobs" to be work inside that extent.&amp;nbsp; Due to the nature of those jobs and to be able to work more efficiently they need to allow overlapping AOIs.&amp;nbsp; So we like to have the option to allow overlapping areas by job type but allowing to overlap with other job types so we can still have the main extent delimited or somehow parent and child jobs be able to share an LOI.&amp;nbsp; Right now we have the main LOI created in job type A and corresponding jobs (job type B) as child jobs but either skipping AOI creation (not desired but the application allows it, which is a big data security flaw) or creating AOI as they are available in the main extent (which delay our operations).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 May 2019 15:26:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-workflow-manager-ideas/allow-overlapping-areas-by-job-type-in-workflow/idi-p/940791</guid>
      <dc:creator>Ulises</dc:creator>
      <dc:date>2019-05-07T15:26:09Z</dc:date>
    </item>
    <item>
      <title>Re: Allow overlapping areas by job type in Workflow Manager - Status changed to: Under Consideration</title>
      <link>https://community.esri.com/t5/arcgis-workflow-manager-ideas/allow-overlapping-areas-by-job-type-in-workflow/idc-p/1012572#M61</link>
      <description>&lt;P&gt;Hi UlisesFelicianoTroche,&lt;/P&gt;&lt;P&gt;This makes sense. It would need to be based on the parent/child relationship though, that's the only way we could define a pattern to follow.&lt;/P&gt;&lt;P&gt;So it would be something like Disallow Overlapping with an optional checkbox to add in an exception:&amp;nbsp;Except in parent/child scenarios&lt;/P&gt;&lt;P&gt;This way a parent could have a large location (with children within it) and it would disallow parent jobs from overlapping and children from different parents overlapping.&lt;/P&gt;&lt;P&gt;Would this satisfy your use case?&lt;/P&gt;&lt;P&gt;Thanks for contributing &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;</description>
      <pubDate>Mon, 28 Dec 2020 22:16:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-workflow-manager-ideas/allow-overlapping-areas-by-job-type-in-workflow/idc-p/1012572#M61</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2020-12-28T22:16:05Z</dc:date>
    </item>
  </channel>
</rss>

