📄️ Step 1: First Workflow Application
Let’s build a workflow for the sample banking use case - deposit funds into a customer account and notify them via email and SMS about the status.
📄️ Step 2: Running Workflows from Code
So far, we have seen how to compose and run basic workflows from the UI. However, more commonly, we will be running the workflows from an application or service. Let’s learn how to do this from our applications. Orkes Conductor platform offers various SDKs in different languages
📄️ Step 3: Adding Custom Code Worker
Continuing the use case from the previous step, we now have a requirement to add a fraud check for all deposit transactions >= $10,000.
📄️ Step 4: Running an Inline Function
So far, we haven't done anything here, even if the fraud check fails. How can we handle the case where the fraud check returned a fail, and we want to skip processing the deposit transaction? We can add another inline task that can check for the outcome of the fraud check and send a different message to our users via SMS or Email.
📄️ Step 5: Adding Wait Conditions
The wait task in Conductor is used if the workflow is to be paused for external signals. The signals can be manual human interventions or an event from external sources such as Kafka, SQS, etc. Let’s learn how to pause your workflows using wait tasks.
📄️ Step 6: Executing Tasks in Parallel
Another exciting feature of Conductor is executing tasks in parallel. A common scenario is to run a specific task based on an array of values. Let's try this out on our workflow.