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

chetansethi

Hi All,

I am working on a nested workflow. Before the wftask for nested workflow there is an external task which compiles the wft file to create a job specification file. The wftask has the element jobfile with value as the file created by the external task earlier. But even when wftask is activated the nested workflow is not automatically instantiated.

As per my understanding if in the wftask i put the jobfile element then the upon activation of the wftask, teamsite automatically compiles and instantiates a job using the spec file. But somehow that is not happening.

What could be wrong here. Thanks in advance for your help!

Chetan
TS: 6.1.0 Service Pack 2

Find more posts tagged with

Comments

chetansethi

The problem is solved... For all those who might be thinking.. The wftask needs to have owner as someone who is a master, because that task needs to instantiate a workflow.

milind

Hi Chetan,

I am also trying same thing. In my case the user is not a master even then he can start the nested workflow, also in the documentation it is not mentioned that user must be a master. Please check if there is any other error.

Reviewing the TS65 workflow developer guide, it's documented that the the v must be specified in the full path to the workflow template file. Also, it's important that the that all necessary arguments will have been provided as task variables to ensure that the workflow to start up successfully. Violation to these criteria will prevent the workflow from starting up correctly and require user intervention.

Please try this and let me know if it works

Regards
Milind

chetansethi

Milind,

Thanks for your input... Does the nested workflow start automatically or does it require the user to click on Start Job button of the task?

Cheers,
Chetan

milind

Chetan,

If the nested(child) workflow expects any input from user then user needs to click on "Start Job" button. But if no input is required then it starts automatically in background.

Regards
Milind