| Term | Definition |
|---|---|
| Action | An interaction between a RecordSet and external source. Typically takes on the function of data distribution. The current supported actions are: Send Email, Create PDF, HTTP POST, iFormBuilder Record, iFormBuilder Option List, SQL Server, Zoho Reports, and Slack . |
| Aggregation | Summarizing data such as the average, count, or min/max value of a field. The source for the aggregation can be a single RecordSet or multiple RecordSets. Related Article |
| back to top | |
| Condition | A true/false statement that determines inclusion into a RecordSet or if an Action takes place. Data Filter is based on defining a condition or set of conditions. Conditions can also be applied to Actions. |
| Connection | Authentication for interacting with external applications. The owner of a Connection is able to share it with other users; only access to the Connection is shared, not the authentication details. Supported Connections: Email Server, SQL Server, iFormBuilder, Zoho Reports, Slack Related Article |
| Customer Success Center | The support portal for those seeking help with Zerion products and services. Includes the Zerion Academy training portal as well as dedicated areas for Mobile Data Collection, Dataflow Automation, and Zerion Identity Management. Read official articles, chat with a live representative, submit a help desk ticket, or browse community forums. |
| back to top | |
| Dataflow | A diagram that maps the movement of data. Similar to a workflow, but with an emphasis on data rather than processes. A dataflow can be thought of as a container for the project. |
| Dataflow Automation | The process of developing a sequence of steps that execute automatically, managing your data. The sequence is repeated each time data enters, thus automating the process of data storage, refinement, and distribution. Related Article |
| Dataflow Canvas | The dataflow workspace. The canvas includes the Dataflow Header and the space where nodes are displayed. |
| Dataflow Header | The area located at the top of the Canvas with information about the currently loaded Dataflow. Includes: Dataflow name, ID number, Nodes used/available, full-screen toggle, refresh button, and information on selected Node when applicable. |
| Dataflow Object | An object on the dataflow. There are four types of nodes: Webhook, RecordSet, Action, and Event. |
| Delete All Records Recursive | Delete all Records in a RecordSet and all records in child RecordSets |
| back to top | |
| Event | A node that acts as a notification, used to trigger other sequences. An event will evaluate as either a Success or Failure. |
| back to top | |
| Filter | Restricting which records are allowed in a RecordSet. If a record passes the condition(s) set by the filter, it will be stored in the RecordSet. The reocrd is not modified in any way, only included or excluded. Related Article |
| back to top | |
| HTTP POST | A flexible Action that sends data to a designated endpoint. |
| back to top | |
| iForm Option List | An Action Object that can Create Option or Create Option (update if already exists). |
| iForm Record | An Action Object that can Create Record, Assign Record, or Create Record and Assign. |
| back to top | |
| JSON | how a record is structured. Stands for JavaScript Object Notation. |
| back to top | |
| Manually Re-run Data | Force the execution of Records through the Dataflow. From the selected RecordSet, the Re-run of data can be to a specific child RecordSet or all children. The set of data can be a single Record (listed by RUN_ID) or all records in the RecordSet. |
| Metadata | System captured data that is automatically generated and assigned to records. |
| back to top | |
| PDF Reports | Generated PDF Reports are stored in a directory structure accessible by the link on the left side of the navigation. |
| Permission | A policy or set of policies which define user access Related Article |
| Pre-Process | A process that happens before storage into a RecordSet. Data filter and data transform are examples of a pre-process |
| back to top | |
| Record | A single line of data. A record is structured as a JSON object and is analogous to a row in a table. |
| Record Data | A tab within the Dataflow Builder that displays a list of Records for a selected RecordSet. |
| RecordSet | Where records are stored. A RecordSet can have a pre-process applied to it to affect what is stored. The three types of data pre-processing are: filter, transform, and aggregate. Related Article |
| RUN_ID | A unique ID associated with the individual transaction. A single record run multiple times will generate a unique RUN_ID each time. |
| back to top | |
| Transaction | A common term to aggregate usage. Pulling data from a Webhook, storing a Record, pushing a Record to another RecordSet, and creating a PDF are all examples of transactions. Related Article |
| Transform | Modifying the contents of a record. The record may be added to, removed from, or modified. Related Article |
| back to top | |
| Usage/Usage Statistics | Information regarding the activity within a Company, Dataflow, or specific Dataflow Object. Usage is tracked by number of Transactions. Related Article |
| User | An entity within ZIM that is given access permissions |
| back to top | |
| Webhook | The way data automatically enter a dataflow. A webhook is a unique URL using the HTTP POST protocol. Related Article |
| back to top | |
| Zerion Academy | The e-Learning portal for improving your knowledge of the Zerion Ecosystem. Includes articles, video tutorials, and self-paced asynchronous courses. |
| Zerion Reports | An Action connecting to our customizable reporting and dashboarding service. |
| back to top | |
| Suggest a Term Last Modified: 09/16/16 |
|
Dataflow Automation Glossary of Terms
Comments
0 comments
Please sign in to leave a comment.