Quickstart

This guide is designed as a whistle-stop tour for users, to show how a basic 1Integrate workflow is created and run. Each heading links to an explanation of that step in the process.

     Note: For in-depth explanations of each feature of 1Integrate please access the relevant sections from the table of contents.

General 1Integrate Flow

1Integrate is a robust tool that can have workflows that take different shapes and sizes. All of these follow a similar basic structure to the five steps described below, while more complex Sessions may contain more Data Stores, Rules, and Actions.

Create a Data Store

Data Stores are where the data is held within 1Integrate for access and configuration. They can be set to determine how 1Integrate interprets the data for both inputs and outputs. This may be an input of one file type that is then outputted as another type at the end of the workflow.

Create a Rule

1Integrate is a Rules-based tool that takes logical steps outlined within Rules (and Actions) to perform validation on the Data.

Rules are built to validate for specific outcomes or conditions, creating reports and filtering data to show non-conformances.

Create an Action

Actions are set up and built in the same way as Rules. However, Actions are used to add, transform, remove, or report on data. They can also be paired with Rules in an Action Map to filter the data before the Action runs.

Create a Session

Sessions are a collection of ordered Tasks that execute a particular type of instruction. Tasks include things like opening a Data Store for other tasks to get access to the Data within, or running the Rules and Actions that validate or interact with the data. These Tasks activate sequentially and it's important to understand how each Task will affect others in the Session.

Run a Session

Running Sessions will execute the Tasks in order. The Session controls allow Tasks to be paused and for the Session to be rewound and edited if necessary before running again.

Finished Sessions allow users to view the outcomes of each Task, which includes viewing reports from Rules and Actions, downloading data, or viewing data on the Map Viewer.