<?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 Loop to Subworkflows inside a Workflow  in ArcGIS Workflow Manager Ideas</title>
    <link>https://community.esri.com/t5/arcgis-workflow-manager-ideas/loop-to-subworkflows-inside-a-workflow/idi-p/947459</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Let’s say you have a &lt;STRONG&gt;Workflow L&lt;/STRONG&gt; that fit into these guidelines:&lt;/P&gt;&lt;UL&gt;&lt;LI style="margin-bottom: .0001pt;"&gt;Frequently used.&lt;/LI&gt;&lt;LI style="margin-bottom: .0001pt;"&gt;Important to group the components as one workflow.&lt;/LI&gt;&lt;LI&gt;Updated or changed frequent enough that flexibility is a must.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;What I believe would be truly useful is the ability to recall &lt;STRONG&gt;Workflow L&lt;/STRONG&gt;, regardless if you are working in &lt;STRONG&gt;Workflow A, Workflow B, or Workflow C.&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How this would work is that in &lt;STRONG&gt;Workflow B&lt;/STRONG&gt; you get &amp;nbsp;to a step referencing&amp;nbsp;&lt;STRONG&gt;Workflow L&lt;/STRONG&gt;.&amp;nbsp; Once the user is done with &lt;STRONG&gt;Workflow L&lt;/STRONG&gt;, a question could be asked of the user inquiring if they were in &lt;STRONG&gt;Workflow A&lt;/STRONG&gt;, &lt;STRONG&gt;Workflow B&lt;/STRONG&gt; or &lt;STRONG&gt;Workflow C&lt;/STRONG&gt;.&amp;nbsp; That could recall back to the original workflow and inserted as a step after referencing &lt;STRONG&gt;Workflow L&lt;/STRONG&gt;.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A real world example of this is let’s say &lt;STRONG&gt;Workflow L&lt;/STRONG&gt; is referring to a repeatable landbase checklist that is required every time a user is posting construction updates into the database.&amp;nbsp; Once the user gets to the part in the &lt;STRONG&gt;Construction Workflow&lt;/STRONG&gt; in which the landbase should be verified before completing the update, a step could be inserted referencing the &lt;STRONG&gt;Landbase Workflow&lt;/STRONG&gt;.&amp;nbsp; Once the &lt;STRONG&gt;Landbase Workflow&lt;/STRONG&gt; is completed, a question could be asked of the user asking which workflow they were working in, with the &lt;STRONG&gt;Construction Workflow&lt;/STRONG&gt; being an option as a “3”.&amp;nbsp; That “3” could be called back in the &lt;STRONG&gt;Construction Workflow&lt;/STRONG&gt;, right after the step of directing the user to the &lt;STRONG&gt;Landbase Workflow&lt;/STRONG&gt;.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 May 2017 16:25:14 GMT</pubDate>
    <dc:creator>MelissaAnthony1</dc:creator>
    <dc:date>2017-05-17T16:25:14Z</dc:date>
    <item>
      <title>Loop to Subworkflows inside a Workflow</title>
      <link>https://community.esri.com/t5/arcgis-workflow-manager-ideas/loop-to-subworkflows-inside-a-workflow/idi-p/947459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Let’s say you have a &lt;STRONG&gt;Workflow L&lt;/STRONG&gt; that fit into these guidelines:&lt;/P&gt;&lt;UL&gt;&lt;LI style="margin-bottom: .0001pt;"&gt;Frequently used.&lt;/LI&gt;&lt;LI style="margin-bottom: .0001pt;"&gt;Important to group the components as one workflow.&lt;/LI&gt;&lt;LI&gt;Updated or changed frequent enough that flexibility is a must.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;What I believe would be truly useful is the ability to recall &lt;STRONG&gt;Workflow L&lt;/STRONG&gt;, regardless if you are working in &lt;STRONG&gt;Workflow A, Workflow B, or Workflow C.&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How this would work is that in &lt;STRONG&gt;Workflow B&lt;/STRONG&gt; you get &amp;nbsp;to a step referencing&amp;nbsp;&lt;STRONG&gt;Workflow L&lt;/STRONG&gt;.&amp;nbsp; Once the user is done with &lt;STRONG&gt;Workflow L&lt;/STRONG&gt;, a question could be asked of the user inquiring if they were in &lt;STRONG&gt;Workflow A&lt;/STRONG&gt;, &lt;STRONG&gt;Workflow B&lt;/STRONG&gt; or &lt;STRONG&gt;Workflow C&lt;/STRONG&gt;.&amp;nbsp; That could recall back to the original workflow and inserted as a step after referencing &lt;STRONG&gt;Workflow L&lt;/STRONG&gt;.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A real world example of this is let’s say &lt;STRONG&gt;Workflow L&lt;/STRONG&gt; is referring to a repeatable landbase checklist that is required every time a user is posting construction updates into the database.&amp;nbsp; Once the user gets to the part in the &lt;STRONG&gt;Construction Workflow&lt;/STRONG&gt; in which the landbase should be verified before completing the update, a step could be inserted referencing the &lt;STRONG&gt;Landbase Workflow&lt;/STRONG&gt;.&amp;nbsp; Once the &lt;STRONG&gt;Landbase Workflow&lt;/STRONG&gt; is completed, a question could be asked of the user asking which workflow they were working in, with the &lt;STRONG&gt;Construction Workflow&lt;/STRONG&gt; being an option as a “3”.&amp;nbsp; That “3” could be called back in the &lt;STRONG&gt;Construction Workflow&lt;/STRONG&gt;, right after the step of directing the user to the &lt;STRONG&gt;Landbase Workflow&lt;/STRONG&gt;.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 May 2017 16:25:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-workflow-manager-ideas/loop-to-subworkflows-inside-a-workflow/idi-p/947459</guid>
      <dc:creator>MelissaAnthony1</dc:creator>
      <dc:date>2017-05-17T16:25:14Z</dc:date>
    </item>
  </channel>
</rss>

