Does conductor support dynamic subworkflow?

[qingdaojunzuo]

Hi,

We want to implement below behavior with conductor,

workflow1 => "task1 -> subworkflow -> task2 -> task3 ...“

This can be implemented with predefined workflow definition. But we want to make subworkflow as a dynamic task, such as, the input parameters of subworkflow and subworkflow name can be read from task1's output or workflow's input parameters. Like to treat the whole workflow as a template

We found,

• Dynamic task, it seems that the dynamic task supports SIMPLE task mentioned in document. Does it support operator task? such as subworkflow task? Seems that the input parameters of subworkflow can be configured with Dynamic task's input parameters and the subworkflowParam object can be configured directly on Dynamic task?
• Dynamic fork join task, we want to do some other tasks after subworkflow finished (not started) with subworkflow id, dynamic fork join task can generate dynamic subworkflow, but it seems that it can't insert task after subworkflow task and needs a join task after dynamic fork, can we get the subworkflow id after join task? using the output of dynamic subworkflow with parameter key subworkflowId or from join task output?
• Start a workflow by API in SIMPLE task, as mentioned above, we need to wait the new started workflow finished. I think we can add wait/notification between source workflow and new started one, but if the new started failed with any task, the notification is not simple to implement and also the way is complex and not straightforward
• Workflow status listener, maybe this can help in the case, such as when completed/failed, tigger another workflow with workflowid. Need to implement WorkflowStatusListener on conductor server side and register your own bean as workflowStatusListener() in ConductorCoreConfiguration.java. Is there a more flexible way to do this since the notified workflows maybe dynamic added with different input parameters. The status listener seems to be fit for the fixed requirement for all workflows
• Does name in subworkflowParam of subworkflow task support placeholder, such as ${workflow.input.subworkflowname}, checked with source code, it seems that the value of name is read from json straightforward? If name can be configured as placeholder, seems that all the things should be easy
• Create the workflow1 dynamically

So any suggestion on this? We want a lightweight, flexible, dynamic, formal and simple way to implement this or anything misunderstanding here?

Appreciate for your kindly help!

[qingdaojunzuo]

Found that subworkflowParam defined in SubWorkflow task with parameter { "version": 2 } resovled the variables in placeholder, such as,

{ ..., "type": "SUB_WORKFLOW", "subWorkflowParam": { "name": "${workflow.input.name}", "version": 2 } }

Thanks