Sample Use Cases
Payment process
In a typical payment process, for every purchase made, a payment link with the invoice will be shared with the purchaser. Upon successful payment, a receipt will be generated; in the event of failure, the entire process will have to be restarted.
The process can be set with a simple conditional workflow using Function and Branch states. Initially, a Function state sends the payment link with the invoice. A Branch state is then configured to handle the success or failure of the payment. Upon successful payment, a payment receipt is generated, and upon failure, a loopback flow invokes the first function to restart the payment process. Resend attempts can be configured in Error handling with Retry and Fallback options.
Data processing
A real-time data processing operation involves a huge volume of data input, and complex computations, and could generate a large volume of output data.
The huge volume of input data can be executed as multiple iterations using a Batch state, while a Parallel state configured can execute simultaneous operations in parallel to process data faster. In addition, Circuit allows you to break down a complex workflow into multiple circuits nested within one another for better organization.
Event driven process
Establishing a process to send customized emails to clients and perform tasks when specific events occur.
This process can be set using the conditional state called Branch state to execute different actions depending on the conditions, and with the Parallel state, multiple functions can be executed simultaneously in parallel to achieve multiple outcomes.
Data Synchronization
An automated background process to perform routine backups, auto-installation of software or software patches, and periodic upgrades of antivirus.
A workflow is created using the DB Engine state to access and retrieve data from the database. With the Function state, you can synchronize and perform a periodical backup of any service at a specific time interval. This can be scheduled using the Schedules module in Qntrl to execute this Circuit at a specific time interval. For example, you could set the scheduler to trigger the backup function every day at midnight.
ERP data backup
A process is set to automate a recurring monthly process using Schedules for implementing a standard server upgrade. Before modifications, the current ERP data is transferred to a backup folder via File Transfer. Subsequently, the Powershell Engine conducts a comprehensive backup of all ERP data, ensuring data integrity by transferring it from the source to the destination path.
Employee Onboarding
Related Articles
Use case for Bridge: Connect with remote databases using Bridge
Most organizations secure their remote databases using firewalls. If you are looking for a way to navigate these firewalls to access remote databases, Bridge can be of help. Let us try to solve a real-time business case where Bridge is used to access ...Business case 3: Use client scripts to fetch data from third party applications or websites
While designing forms, we might sometimes want to display data from other websites or applications like stock rates, flight status, freight details, weather updates, and so on. To fetch such information from third party websites or applications and ...Sample Use Case - Configuring Input and Output Processing in Circuit console
Let's explore Input/Output Processing further by building a Circuit using the example of an Employee Onboarding Process. We initiate the process with the following state Input which contains information about the employee details for employee ...Business case 1: Use client scripts to perform mathematical calculations and validations on data
While designing forms to replicate finance related documents like purchase order, invoice, or reimbursement bills, our workflows might require the calculation of total cost or sum of expenses incurred. To automate such mathematical calculations and ...Business case 2: Use client scripts to auto-populate fields based on user input
While designing forms, we would sometimes require to display different sets of fields for different user responses. Such automatic field population can be handled using client scripts. Business Scenario Helen creates a sign-up form for her product ...
You are currently viewing the help articles of Qntrl 3.0. If you are still using our older version and require guidance with it, Click here.