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; } } }

Create Dynamic workflow through WFM

RaamKumar

Hi all,

I am trying to create a dynamic workflow through workflow modeler. But in my scenario, i select a list of reviewers in the initiator form. so the workflow should be dynamically created depending on the number of reviewers selected.

If i select 2 users, then 2 reviewers will get a task to review the files. Upon review the successor task will be different for both reviewers. The same if the selected numbers of reviewers varies (3,4..8).Advice me if we have any options in achieving this. I got stuck up in achieving this scenario.

Also is there any options to modify the jobspec similar to template script in case of WFT.

Please help me in solving this scenario. Thanks for your response in advance.

Thanks
Raam

Find more posts tagged with

Comments

Faizi

Hi all,

I am trying to create a dynamic workflow through workflow modeler. But in my scenario, i select a list of reviewers in the initiator form. so the workflow should be dynamically created depending on the number of reviewers selected.

If i select 2 users, then 2 reviewers will get a task to review the files. Upon review the successor task will be different for both reviewers. The same if the selected numbers of reviewers varies (3,4..8).Advice me if we have any options in achieving this. I got stuck up in achieving this scenario.

Also is there any options to modify the jobspec similar to template script in case of WFT.

Please help me in solving this scenario. Thanks for your response in advance.

Thanks
Raam

It is not possible to create any task on the fly in workflow. You have to defined what are the tasks required then add those task in the workflow.

As per your requirement there are multiple reviewer selection, for each reviewer has different successor task. right!
So it is not possible to create many user task for review and then its successor task. You have to define first what are the types of reviewer and its successor task (in number) then divide them into groups. Now for each group define its successor task. Now using conditional link you can pass to user task (review) and then its successor task. In this way you can solve your requirement.

Hope this helps.

Samir_Friend

It is not possible to create any task on the fly in workflow. You have to defined what are the tasks required then add those task in the workflow.
-------------------
-------------------

A little correction here.... It is possible to create tasks dynamically while using wft approach(through Perl). Not sure about the WFM.

RaamKumar

Hi Faizi,

Yes, we can achieve this through conditional link. Just want to clarify whether it can achieved through post processor.

Thanks,
Raam.

Faizi

A little correction here.... It is possible to create tasks dynamically while using wft approach(through Perl). Not sure about the WFM.

Hi Samir,

My reply was in context of WFM, because if you look on Title it is clearly mentioned "Create Dynamic workflow through WFM".

Anyway thanks for pointing.

Thanks,

Samir_Friend

Hi Samir,

My reply was in context of WFM, because if you look on Title it is clearly mentioned "Create Dynamic workflow through WFM".

Anyway thanks for pointing.

Thanks,

Fine. Just thought I should point it out. Keep up the good work! Smiley Happy

Faizi

Hi Faizi,

Yes, we can achieve this through conditional link. Just want to clarify whether it can achieved through post processor.

Thanks,
Raam.

If you go through WFM guide. You will find the below description:

Pre-processor commands are executed during the workflow instantiation (just before the instantiation screen is rendered), whereas post-processor commands are executed after the instantiation screen is rendered and before the workflow job is created.

Note:
You cannot remove a CONFIGURABLE, DATASOURCE or SCRIPT variable using workflow apis, within a PreProcessor or PostProcessor Command. Workflow APIs only support removing simple text values and not variables.

Your requirement comes into picture after the instantiation screen. So job specification file already created, so now you would add more task in the workflow.
So i do not think PostProcessor will help you much.