Introduction to Flow Data
- Updated on 08 Jan 2019
- 2 minutes to read
Flow Data is the information that is being managed or accessed by a Flow. Flow data is generated by every step and that data can be accessed downstream from the Flow. Steps generate data in a Flow, but the step also requires data from the Flow in order to execute. An example of a step that generates data would be, a step that fetches a file from an FTP server or gets data from a database. Any step that can consume data and execute the Flow can pass the Flow Data along. Some examples of steps that consume data include a rule step, a send email step, or a step that retrieves data from an excel file. These steps produce a specific outcome for the flow to execute and complete.
Data can also be provided as input to a flow. Flows that start with a User taking action on a form will often have no data as inputs. Flows that are triggered by service calls or used as sub flows often have data as both inputs and outputs. The data is set up on the inputs of the start step in a flow. The same data can be set up on the outputs of the end step.
- Refers to all data managed or accessed in a flow
- All Steps can create data usable downstream
- Steps may require data to execute
- System-wide constants
A document approval Flow could be called by another system. The Flow might take in a document and a list of required approvers. That Flow would then use the data to communicate assigned tasks and write an approval status to a database. In addition, the data produced by the steps and the data that is input into the flow itself.
Look up Lists & Constants
System-wide data constants can be defined and are available as flow step input data. These system constants are specified in the Lookup Lists and Constant folder.
- Stystem>Designers>Look up lists and constants .
The Lookup List is a Folder containing a collection of system constants and lookup lists. That can be created and used in Flows or Rules as reusable data. These lists are usually common names, places, numbers, or other types of information that can help decipher a field.
Data Mapping Editor
The Mapping editor represents the flow of data using a visual map and accounts for each input and output data type. The Mapping editor shows the data types connection from one output to the next input. Use the Mapping Editor to select a data source to use as an input for the selected step in the flow. You can also define how these inputs should be used before proceeding to the next step.
Using the Mapping Editor