Bridge: How to continue Parent Workflow after all Child Workflow runs have been completed
Hello,
When referring to the Child Workflow in the Parent, is there a way to have the Parent workflow continue when all runs of the Child Workflow have completed? For example:
- Parent workflow has an array with 10 elements
- Child workflow runs for the number of elements in the array, so 10 times
- Is there a way to have the Parent workflow continue after all 10 Child workflow runs have completed?
Thank you,
Neil Egsgard
Business Solutions Architect
Southern Alberta Institute of Technology
Answers
-
What exactly do you mean by "Continue"?
-
@Paul Newcome , I mean continue to the next workflow element on the Parent Workflow after the Child Workflow element. When the Child Workflow "Number of runs" is the number of array elements in an array, does the Parent workflow activate the next workflow element after the Child Workflow:
- Immediately after starting the first Child Workflow run on the first array element
- Immediately after finishing the first Child Workflow run on the first array element
- After all Child Workflow runs on array elements are complete
- After all Child Workflow runs on array elements have started
- Some other timing
In the image below, when does the Workflow enter "State: After Child". This is an example layout.
-
That's a good question. I've never actually tried to do anything after the Child Workflow.
@Genevieve P. or @Brian_Richardson Have either of you run through this before?
-
Yes it continues on once the child runs complete
-
@Brian_Richardson , thanks for the response. Just to clarify, does this mean the Parent Workflows continues after:
- All Child Workflow runs have been started or
- All Child Workflow runs have been completed
Regards,
Neil
-
I believe it’s after completion of all child runs. I don’t have a specific case though to test it with.
-
So I just did a quick test with a child workflow adding 20 rows titled "Child" and then a parent workflow adding a row afterward titled "Parent". The child workflow completed all runs before the parent continued and did it's adds.
BTW this took about 2 minutes to do 20 row adds. Child workflow spinup is not quick at all. If you ever have to use child workflows I would look at using Javascript to package things like 500 row adds at once to significantly speed this up.
You can see some examples of Javascript and bulk change in my Bridge Examples post.
-
Thanks for jumping in, @Brian_Richardson (and thanks for the tag, @Paul Newcome!)
That's correct, and a great example.
For @Neil Egsgard, here's your bullet point question from above, with the correct answer highlighted:
- Immediately after starting the first Child Workflow run on the first array element
- Immediately after finishing the first Child Workflow run on the first array element
- After all Child Workflow runs on array elements are complete
- After all Child Workflow runs on array elements have started
- Some other timing
Cheers,
GenevieveNeed more help? 👀 | Help and Learning Center
こんにちは (Konnichiwa), Hallo, Hola, Bonjour, Olá, Ciao! 👋 | Global Discussions
Categories
- All Categories
- 14 Welcome to the Community
- Customer Resources
- 64.8K Get Help
- 434 Global Discussions
- 136 Industry Talk
- 470 Announcements
- 4.9K Ideas & Feature Requests
- 129 Brandfolder
- 148 Just for fun
- 65 Community Job Board
- 485 Show & Tell
- 33 Member Spotlight
- 2 SmartStories
- 300 Events
- 36 Webinars
- 7.3K Forum Archives