cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Events for workflow state change

Events for workflow state change

Currently there are no events available for programming showing that a subworkflow has been terminated or completed.

I'd like the main workflow to complete if all of its subprocesses are completed or terminated. Currently this can only be done directly in the Workflow Template Adminstrator but the backdraw is that this solution only works if the number of subworkflows has to be known at the time when you create the main workflow.

4 Comments
DonSenchuk
Regular Member

Could you clarify this? I'm looking at the template administrator right now and I don't see anything called a "subworkflow" or a "subprocess". It's unclear what you mean by "subworkflow".

hlinseisen
Newbie

You can start new (sub) workflows within another ( main ) workflow either programatically or by designing it in the worklowadministrator

hlinseisen
Newbie

I just wonder why one voted this down

DonSenchuk
Regular Member

I asked you to clarify what you were talking about and you simply repeated what you had already said. That is not clarifying, it’s repeating.

The suggestion is unclear and uses terminology that isn’t seen in the workflow template administrator (“subworkflow” & “subprocess”). If I were to assume – which I hate to do – what you mean by “subworkflow”, it can already be done with the Change Notice/Change Activity setup [1] or it could be done with the Process node [2] in the workflow editor, neither of which requires any new implementations.

[1] You can have many Change Activities running inside a Change Notice and you do not need to know how many there are when you create the workflow.

[2]