nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Nested Workflow

kaalraa

Hi,

Can anyone make me understand some of the concepts related to nested workflows?

1. When we run a nested workflow, what would be the status of both the workflows? Parent as well child before completion. Does child wf hangs on till the time parent workflow complete its job?

2. What would be the status of the ENDTASK in the child workflow? Activated, Inactivated or Done?

Also if anyone suggest me any link from where i can read on about more nested workflow concepts... that would be great.

Thanks in advance.

Find more posts tagged with

Comments

Adam Stoller

Hi,

Can anyone make me understand some of the concepts related to nested workflows?

1. When we run a nested workflow, what would be the status of both the workflows? Parent as well child before completion. Does child wf hangs on till the time parent workflow complete its job?

2. What would be the status of the ENDTASK in the child workflow? Activated, Inactivated or Done?

Also if anyone suggest me any link from where i can read on about more nested workflow concepts... that would be great.

Thanks in advance.

I haven't used the wfttask in a while, so things might have changed a bit - but I believe the answers are:

1. Yes - child wf hangs on until parent ends
2. activated

If you search the forums you'll find a number of threads regarding nested workflows - some are more informative than others. In the end though, empirical evidence is your best bet as to behavior - write a small nested workflow and see what happens.

kaalraa

Thanks Adam.... am working on the same. The issue i am facing is in my Parent workflow 2 tasks run in parellel. One is the wftask (nested) and other is normal task running through.

My query is as what would happen if the nested workflow hangs upon any usertask defined within, whereas the normal flow of the parent wf comes to end?

Also there is a bit confusion i have in my WFT. when i use iwgetwfobj to check the status of wftask in parent wf it get back as DONE. Whereas if we check the status of EndTask in child wf it gives status as INACTIVATED.

Adam Stoller

Thanks Adam.... am working on the same. The issue i am facing is in my Parent workflow 2 tasks run in parellel. One is the wftask (nested) and other is normal task running through.

My query is as what would happen if the nested workflow hangs upon any usertask defined within, whereas the normal flow of the parent wf comes to end?

Also there is a bit confusion i have in my WFT. when i use iwgetwfobj to check the status of wftask in parent wf it get back as DONE. Whereas if we check the status of EndTask in child wf it gives status as INACTIVATED.

Your parent workflow should not allow itself to be completed until the child workflow has completed (conditional clause in activation section somewhere after the forking of the two processes) - so that shouldn't be an issue.

Killing the parent workflow while the child workflow is still active is another story. Not sure what happens there - my guess is you get an orphaned child workflow that you'd have to kill off manually.