Have you considered using dynamic task expressions to trigger only that tasks that you what when you want based on the drop down options picked?

Using this method allows you to add multiple tasks to a single process stage that only fire up when needed. 

Alternatively, if you wanted them to become separate requests instead then you could look at bundles instead.

Steve,

the goal is to fire all tasks concurrently, not one at a time.  The point is that HR, Security, and Procurement have no interdependency on the other tasks, so they can all kick off concurrently.  Unfortunately, both methods shown, still do one task at a time (in series not concurrently), unless I’m missing something.  We use dynamic task expressions all the time, but even if i put the same express in all the tasks, it only fires one task, waits for it to get done then fires the next one; I need all of them to fire at the same time.  Bundles doesn’t seem appropriate as this isn’t multiple requests, this is just one question which triggers multiple tasks concurrently.  Bundles doesn’t solve the issue because again it’s one task at a time.  I need a process that fires all initial tasks at one time, then it may tree off those initial tasks with other tasks but, I need that initial concurrency.

In my example any of the 9 tasks can trigger concurrently, each one designed to go to a different technical team based on form inputs. The workflow will not progress to the next stage until after all of the tasks have been closed. You achieve this by putting multiple tasks in the same stage, each with their own expression.

For example you might use something like…

I’ve tried this with dynamic expressions and it still only fires one assignment is there a setting somewhere to allow concurrent?  This is 11.7 if that matters?
 

I’m trying to make an international travel request which concurrently goes to multiple teams to.  As an example: start security to issue vpn, HR has to update records for where the person is traveling and the timeframe, electronic communicate provides international numbers for teams, procurement to provide an international certificate for the equipment, if the period is longer than 30 days there are other concurrent tasks, if the person is traveling to certain countries there are other initial requirements, if they are going to another office there are other initial security items.  Once the certificate is done (don’t care about the other items), if they said they need a cell, then they order an international phone, once the phone arrives, support sets it up for vpn, mail and teams (this has interdependencies on everything except hr being done).   
 

so waiting for everything to close, to move to the next set, isn’t dynamic to trigger the next task.  I’d like to look for completion of whatever tasks I choose in my dynamic formula to kick off the next level. If one item only need procurement done, if another item only needs security done, if another item need security vpn, certs, and teams intl done before it starts that’s what I’m looking for.  
 

the little box to write this dynamic formula I haven’t figured out because each need is looking for specific criteria to initialize it: what countries (multi select field), how long (date range from to), is this greater than 30, will you need a cell, are you taking company equipment, select computer to certify and encrypt… all answers will trigger different initial tasks that have no interdependence on each other initially.   That’s a very difficult formula to write and I haven’t figured it out yet and getting the correct things to trigger.  But none the less, the next layer doesn’t need ALL the tasks complete, if they said yes to the cell that can start once procurement gets the cert.  if they said more than 30 days or they need access to a facility that can start as soon as HR has them setup for international, it doesn’t need to wait for all tasks and frankly can’t! 

Tried again, it is firing only the first task.  There has to be a setting I’m missing.

Hi Steve,

I am in the same boat… I am trying to configure 2 parallel tasks/processes where one of them would not stop the process to continue to the next stage (not mandatory) and the other would be “mandatory” to be closed. Let me add some context:

Process for a lost or stolen IT Asset (logged from an offering assigned by default to the Service Desk)

Stage1: Service Desk Triage

It’s a Decision task with 3 options for question: “What type of device?”

1. Mobile Device
2. Other IT Asset
3. Cancel request

Stage2

In cases where answer = 1 it would “INSERT” a “Mobile Device” sub-process that has 2 sub-processes.

• One process (also used in #2) would simply generate a Normal Task assigned to the  IT Security Team (for Assessment/Loging security incident etc.). 

That would be the task that I’d like to be “non mandatory” so the process can continue to next stage, even though it is not closed.

• The second sub process (specific for mobile devices) would also generate a Normal Task  to the MOBILITY Team to blacklist the Serial number of the lost/stolen mobile device. 

This task is “mandatory” and I’d like the main Process to go to next stage only when this one is CLOSED

Stage3

This is a “dummy stage” that is associates with a specific Action Type, and there would be a Smartmail Rule to send an email to the end user to give him the insctruction to order a new device (if needed). The rest of the process is not that important for my question… but fyi, after email is sent… process would end there, waiting for the IT Security Task in stage2 to be completed.

So to make a ong story short, I am also having hard time to configure the parallel tasks in stage2, where one would not be “mandatory” and the other is…

Maybe I should revise my logics ?

Maybe I should simply put the “blacklist” task only at the 2nd Stage and use another method to send a task to the ITSec team?

thanks for any advice!