Overview
Any system is defined by the data it receives as input, the way it processes that data, and the output it generates. In a Circuit execution, the input to the circuit is provided as JSON key-value pairs. This JSON is passed as input to the initial state and the processed output is passed as input to the subsequent state in the Circuit. Each state handles JSON input and produces output in JSON format, until reaching an end state or a terminal state like Success or Failure.
Here, we'll explore how JSON data is passed from one state to another within a circuit and how the JSON data transforms during this process. This requires an understanding of the field structures in the Input and Processing of the Circuit and their significance in data selection and filtering.
The flow of JSON input and output data between different states of a circuit can be regulated, managed, and manipulated through the different types of fields explained below:
- InputPath - Filters the state's JSON input by restricting the input passed to the state as required or by relevance.
- Parameters - Used to add a collection of key-value pairs to the state's input to incorporate new values, exclusive to specific states.
- Result Selector - Refines and filters the task output (state's result) by picking up the required elements in the result object and constructing the key-value pairs. This allows us to choose what to pass to the next field, ResultPath.
- ResultPath - Customize a state's output by merging its input and result(ie., via Result Selector), enabling the transmission of modified JSON to the next state for processing. It helps to replace, augment, or adjust the State Input using the task's result.
- OutputPath - Determines the final result of the state. This is what serves as the input for the next state enabling further refinement of the information. If not defined, ResultPath controls the State Input for the subsequent task.
The below diagram illustrates the flow of JSON data within a task state.
It is essential to specify the respective location or path of data within the Input, Output, and Result datasets for further processing. The conventions for defining the specific data path required from the input, output, and result data sets are explained in the JSON Path article.
Next: JSON Path
Related Articles
Overview of Reports
One of the best ways to manage teams in an organization is to take a step back and analyse the work pattern. Evaluate different aspects of your team’s progress using Reports in Qntrl. Apart from the default reports provided by Qntrl, users can also ...Overview of extensions
Qntrl hosts extensions that provide additional business solutions for your organization. These extensions are software add-ons focusing on feature enhancements, third-party integrations, and many other valuable additions. Qntrl hosts extensions that ...Overview of integrations
Unlock the power of Qntrl with streamlined workflows, and discover new opportunities you can create for your business. Integrate Zoho tools and other third-party applications with Qntrl to facilitate business activities among other horizons, and ...Overview of Users
Organization users Your employees can be added to Qntrl organization as users . Once you add a user to the organization, an invitation email will be sent to their email address. Upon accepting the invite, they will become a current user of your ...Overview of Qntrl
Qntrl helps businesses automate their everyday workflows involving wide-ranging tasks and detailed nuances under a single platform. Whether it's a straightforward workflow involving a single team, or a complex workflow involving multiple teams, Qntrl ...
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.