Tasks

Tasks are managed through Sessions, and are placed in the order in which they should be performed.

Tasks can be added, disabled, deleted, and re-ordered. All required parameters can be browsed and updated. Multi-level undo/redo can be used to correct mistakes.

Tasks can be renamed from the context menu (right-click the task name).

     Note: Sessions execute asynchronously, so that you can monitor progress and abort Sessions. They continue processing even if you log out or shut down the client computer.

The following types of Task can be included in a Session:

Task

Description

Open Data

Enables access to data from a Data Store.

A Session can open data from a number of Data Stores then check Rules based on relationships between features stored in different locations.

Open Schema

An Open Schema Task is used to open a Schema in a Session without loading the associated data from that Data Store.

Build Topology

Allows a build topology task to be run, which applies topology structuring and snapping to your data.

Check Rules

Checks a defined set of Rules on the data and reports non-conformances.

Apply Actions

Apply a defined set of Actions to the data independently of the Rules.

Apply Action Map

Apply one or more Action Maps to the data to identify and resolve non-conformance to Rules.

Transform Schema

Transform Schema is a Session Task that reads input data classes and creates new objects in the Copy To classes. This is achieved by copying the objects from the Read and Commit classes, so the Session will contain both the source and the target objects at the same time.

Validate Schema

The Validate Schema Task type allows you to compare the Schema of two Data Stores, without loading all of the data associated with them.

Pause

Requests the Session to suspend execution, to allow results to be examined before processing the next task. 

When a Session completes, all intermediate data is discarded. A Pause Task can be added at the end to retain data for further processing.

Commit

Updates a Data Store with data changed as a result of applying Actions or Action Maps. 

Writes objects back to the original Data Store that have changed since the last commit (or since the data was opened if this is the first commit).

Copy To

Copies data from the Session to a new Data Store.