- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2023 12:38 AM
Hello,
I have 2 change activities (change_task) to run at the same time and at the beginning of the workflow, the first change activity runs all the time but the second one only runs when a field "A" in table "change_request" is checked.
Since the workflow runs directly after the creation of the "change_request", the field "A" will always be unchecked, and we can never start the second activity.
I have tried to do this, but with this workflow, every time we have to wait for the second activity to run while in reality, we can finish the workflow without running the second activity (in case we didn't check the field "A") :
How can I achieve this please?
Thank you in advance
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2023 05:36 AM
If field A is always unchecked when the change request is created, at what point could it become checked? It seems like you don't want/need the Join activity here since you have the wait for activity to wait for the 2 tasks to be completed, in the case that they will be. So if it works with the Join removed in the scenario where both tasks are needed, you can add something like a timer followed by a check of field A and if it's still not checked by that time/after the first task, whatever your cutoff is, it would lead to the Set Values -> end.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2023 05:36 AM
If field A is always unchecked when the change request is created, at what point could it become checked? It seems like you don't want/need the Join activity here since you have the wait for activity to wait for the 2 tasks to be completed, in the case that they will be. So if it works with the Join removed in the scenario where both tasks are needed, you can add something like a timer followed by a check of field A and if it's still not checked by that time/after the first task, whatever your cutoff is, it would lead to the Set Values -> end.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2023 11:03 AM
Hey,
Do they need to be split like that? If path A runs every time and waits for path B to receive a checkbox, could you just have it go:
Start > Create task > Set values > Wait for checkbox > Create task
If the checkbox is optional, you may have to include a timer as Brad mentioned.
Thanks,
-Mike