- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2018 05:01 AM
Hello everyone,
I have an workflow with multiple layers of tasks and I have a problem with one of the wait for conditions. What happens is that I open 5 tasks at some point in the workflow and one of these 5 tasks when it gets closed it will open another task. The first 4 tasks are all going into an wait for condition so that the workflow doesn't end if and when on these 4 are closed. The 5th task is opening another task when it gets closed. This other task goes into the same wait for condition.
If the 5th task is being closed before the other ones then everything goes fine, the other task is being opened and then when the other tasks are closed the workflow closes out successfully.
If I close the first 4 tasks and then I close the 5th one the tasks associated with the 5th one gets opened but automatically is set on Closed Incomplete and the workflow ends.
Any idea how can I fix this behavior?
Thanks,
Bogdan
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-17-2018 05:33 AM
Try a single 'Join' activity in place of your 2 'Wait for' activities you have currently. It will cause the workflow to wait for all paths into it to complete before the workflow continues on. Your 'Wait for' activities shouldn't be necessary with a 'Join'. Just make sure all of your task activities have their own 'Wait for completion' option selected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-10-2018 02:58 AM
Hi Akil,
The "No" option always goes to the Join activity so that the workflow doesn't end if the previous task was not fired. If you notice I also have a Branch activity which checks the values when the form was submitted. This way I know if I need to fire an additional task or not.
The join activity will wait until every activity that is coming into it will finish, one way or the other(yes or no).
This is how I designed it per our business needs. Based on yours you might need to change some things. I listed the entire workflow below for your reference. If you still have issues getting this to work please list your business requirements so I can get an idea about what is need exactly.
Good luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-11-2018 11:28 PM
I cant use Join activity for all the multiple if conditions.
I am having multiple tasks for multiple If conditions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-10-2018 04:24 AM
Hi Bogdan,
In your case No is not having any task.
My first questions is If No goes to Join activity , How Yes also will reach join in your case . When we are checking for If else -> either if or else should reach join but not Both. Correct me if I am wrong.
My Requirement is I am having parallel If tasks with with parallel and serial tasks, But I want to wait till all the tasks to be completed. and Initially I am waiting for the user to full the variables in Backend and update the RITM.So not sure when user will fill and update But I have to wait until user. If user Fills then it will go to if condition to check whether the variable selected is Yes/ No. On selection of Yes /or I am having some tasks for Yes and some tasks for No.
Either it will trigger tasks related to Yes or No and I am having multiple If condtions in parallel and multiple tasks .
I have to wait till the tasks to be completed to end the workflow.
Note: I am having tasks for either Yes or No but not both based on the user selection of Field.
Please help me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2018 04:35 AM
Hi Akil,
You could put a Join Activity right at the end, after the wait for condition, this way the workflow should wait until all tasks are finished. Please have a look at the concept below. Notice that you can group tasks in one Join activity and then use another Join activity at the end to wait for all tasks.
Hope this helps!
Regards,
Bogdan