<?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>question Parallel Approval in traditional workflow in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/parallel-approval-in-traditional-workflow/m-p/3546214#M6958</link>
    <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;I would like to ask for guidance and best practice recommendations regarding a legacy Workflow Editor implementation that I am currently reworking.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Current Behavior:&lt;/P&gt;&lt;P&gt;* The workflow currently generates approvals sequentially.&lt;BR /&gt;* Each approval has a corresponding SCTASK.&lt;BR /&gt;* When an approval gets approved, its related SCTASK changes from "Pending" to "Open".&lt;BR /&gt;* The SCTASK then triggers a separate automation flow for provisioning/access activities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;New Requirement:&lt;/P&gt;&lt;P&gt;* All predefined approvals and SCTASK definitions should be generated upfront (simultaneously).&lt;BR /&gt;* Approvals should run in parallel instead of sequentially.&lt;BR /&gt;* Each SCTASK should remain in "Pending" state initially.&lt;BR /&gt;* Once a specific approval is approved, only its corresponding SCTASK should transition from "Pending" to "Open".&lt;BR /&gt;* The existing automation flow triggered by SCTASK state change should remain unchanged.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additional Notes:&lt;/P&gt;&lt;P&gt;* This is implemented in Legacy Workflow Editor (not Flow Designer).&lt;BR /&gt;* I am exploring approaches using either workflow.scratchpad or approval/task correlation logic without introducing too many additional custom fields.&lt;BR /&gt;* One issue encountered is that when one approval is approved, the remaining approvals sometimes become "No longer required."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to ask:&lt;/P&gt;&lt;P&gt;1. What is the recommended design pattern for handling parallel approvals with individually linked SCTASKs in Legacy Workflow?&lt;BR /&gt;2. How do you prevent sibling approvals from being automatically marked as "No longer required"?&lt;BR /&gt;3. What is the best way to correlate each approval to its corresponding SCTASK?&lt;BR /&gt;4. Has anyone implemented a similar approach successfully in Legacy Workflow Editor?&lt;/P&gt;&lt;P&gt;Any guidance, workflow design suggestions, or implementation examples would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Wed, 20 May 2026 09:46:37 GMT</pubDate>
    <dc:creator>Jubet Alimasa</dc:creator>
    <dc:date>2026-05-20T09:46:37Z</dc:date>
    <item>
      <title>Parallel Approval in traditional workflow</title>
      <link>https://www.servicenow.com/community/community-central-forum/parallel-approval-in-traditional-workflow/m-p/3546214#M6958</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;I would like to ask for guidance and best practice recommendations regarding a legacy Workflow Editor implementation that I am currently reworking.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Current Behavior:&lt;/P&gt;&lt;P&gt;* The workflow currently generates approvals sequentially.&lt;BR /&gt;* Each approval has a corresponding SCTASK.&lt;BR /&gt;* When an approval gets approved, its related SCTASK changes from "Pending" to "Open".&lt;BR /&gt;* The SCTASK then triggers a separate automation flow for provisioning/access activities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;New Requirement:&lt;/P&gt;&lt;P&gt;* All predefined approvals and SCTASK definitions should be generated upfront (simultaneously).&lt;BR /&gt;* Approvals should run in parallel instead of sequentially.&lt;BR /&gt;* Each SCTASK should remain in "Pending" state initially.&lt;BR /&gt;* Once a specific approval is approved, only its corresponding SCTASK should transition from "Pending" to "Open".&lt;BR /&gt;* The existing automation flow triggered by SCTASK state change should remain unchanged.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additional Notes:&lt;/P&gt;&lt;P&gt;* This is implemented in Legacy Workflow Editor (not Flow Designer).&lt;BR /&gt;* I am exploring approaches using either workflow.scratchpad or approval/task correlation logic without introducing too many additional custom fields.&lt;BR /&gt;* One issue encountered is that when one approval is approved, the remaining approvals sometimes become "No longer required."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to ask:&lt;/P&gt;&lt;P&gt;1. What is the recommended design pattern for handling parallel approvals with individually linked SCTASKs in Legacy Workflow?&lt;BR /&gt;2. How do you prevent sibling approvals from being automatically marked as "No longer required"?&lt;BR /&gt;3. What is the best way to correlate each approval to its corresponding SCTASK?&lt;BR /&gt;4. Has anyone implemented a similar approach successfully in Legacy Workflow Editor?&lt;/P&gt;&lt;P&gt;Any guidance, workflow design suggestions, or implementation examples would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 20 May 2026 09:46:37 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/parallel-approval-in-traditional-workflow/m-p/3546214#M6958</guid>
      <dc:creator>Jubet Alimasa</dc:creator>
      <dc:date>2026-05-20T09:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: Parallel Approval in traditional workflow</title>
      <link>https://www.servicenow.com/community/community-central-forum/parallel-approval-in-traditional-workflow/m-p/3546248#M6960</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://www.servicenow.com/community/user/viewprofilepage/user-id/773661"&gt;@Jubet Alimasa&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;You can use the following 'Wait for Condition Approval' activity.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dgarad_0-1779272778606.png" style="width: 400px;"&gt;&lt;img src="https://www.servicenow.com/community/image/serverpage/image-id/516668i18C8CDB459DB7D08/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dgarad_0-1779272778606.png" alt="dgarad_0-1779272778606.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 May 2026 10:26:37 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/parallel-approval-in-traditional-workflow/m-p/3546248#M6960</guid>
      <dc:creator>dgarad</dc:creator>
      <dc:date>2026-05-20T10:26:37Z</dc:date>
    </item>
  </channel>
</rss>

