Can someone explain “Capture Workflow Start”, “Capture Workflow End”, “Workflow Writer” nodes do in the following workflow.
Hello @exploredata547
These three nodes are the starting road to workflow orchestration. They work together and allows you to split your workflow into different pieces that work as a function in your main process, then saved it locally or remote in server. It is the starting point for deployment and automation as a client or as a service […]
You would be able to Read and Execute your workflow in batch mode with ‘Workflow Reader’ and ‘Workflow Executor’ nodes. If you are interested on: workflow automation, deployment as a service or as a client (testing and production)… I would recommend you to cover up to L3 training course.
BR
1 Like
Thank you..
But, we have components which are like reusable functions.. not sure, why we want to replace workflow with component
Again for orchestration, we have node called call workflow service with space connector node. not sure how workflow reader and workflow executor node are different ?
Hello @exploredata547
components are integrated in workflow so they don’t execute in batch. They can be used in Apps as a part of functional requirements.
call workflow service and call workflow (table based) integrate in client (caller) apps, they work together with workflow service input/output and container input/output (table) within captured workflow
workflow reader and workflow executor nodes are usually used for workflow application testing tasks, or performance testing in development.
Then based on your previous example workflow, it can’t be called with call workflow service because is lacking of workflow service input/output nodes
BR
1 Like