#Workflow builder
In this part, you can find common implementation of various conductor tasks. It's pythonic representation of conductor operators and system tasks This implementation depends on frinx-python-sdk and uses Pydantic to serialize workflow definition to result in JSON format.
#DECISION TASK
#DO_WHILE TASK
#DYNAMIC_FORK TASK
#EVENT TASK
#EXCLUSIVE_JOIN TASK
#FORK_JOIN TASK
#HUMAN TASK
#INLINE TASK
INFO: expression wrapped into javascript function:
#JOIN TASK
Read more on conductor-oss docs
#JSON_JQ_TRANSFORM TASK
#SET_VARIABLE TASK
#SIMPLE TASK
#START_WORKFLOW TASK
Start Workflow is an operator task used to start another workflow from an existing workflow. Unlike a sub-workflow task, a start workflow task doesn’t create a relationship between the current workflow and the newly started workflow. That means it doesn’t wait for the started workflow to get completed.
#INPUT PARAMETERS
start_workflow:
- StartWorkflowTaskInputParameters : StartWorkflowTaskPlainInputParameters|StartWorkflowTaskFromDefInputParameters
- StartWorkflowTaskPlainInputParameters
- StartWorkflowTaskFromDefInputParameters
#SUBWORKFLOW TASK
#SWITCH TASK
- SwitchTaskValueParamInputParameters -> VALUE-PARAM
- SwitchTaskInputParameters -> JAVASCRIPT
VALUE-PARAM evaluator type