Data Import Steps

Data Import Steps are used when importing / uploading data via the

Overview

A Workflow typically describes a "process" through which some entity, such as an Application, moves through. A Workflow Instance is always “on” a specific Data Entry Step, which describes the data entry form that is displayed to the user including the fields that are collected, their validation rules, and the Actions that can be performed while on that Step.

By comparison, Data Import Steps live “outside” of that step-by-step process. Data Import Steps describe data manipulations that can occur at any time, triggered by a file upload. A Workflow Instance is never “on” a Data Import Step.

Using “Data Import Steps” to import data

For more information on how Data Import Steps are used as part of the Workflow Import Queue, see these related pages:

Differences between “Data Entry Steps” and “Data Import Steps”

Concept / Feature

Data Entry Steps

Data Import Steps

Concept / Feature

Data Entry Steps

Data Import Steps

Current Step

The Workflow Instance is always “on” a Data Entry Step.

Only the Actions from this Step can be performed.

The Workflow Instance is never “on” a Data Import Step. Actions from this Step can be performed at any time, triggered by a file upload.

Calculated based on the “Current Step”

No bearing on “Owner Complete”

Completion Status

Cannot modify a Workflow Instance in a Completed Successfully or Completed Unsuccessfully status; a “Make Incomplete” Action must be used first.

Import Steps can be configured to modify Workflow Instances regardless of their Completion Status.

(This is not the default behavior and must be specifically configured)

Input Attributes

Input Attributes are displayed as form fields on the Workflow Popup, which a user fills out within LearningBuilder.

Input Attributes must be present as data columns in the uploaded file.

Display Attributes

Display Attributes (e.g. properties of the “reference entity”) can be displayed as read-only fields on the form, to provide additional context to the user.

Display Attributes have no meaning to a Data Import Step. Only editable fields can be modified via file upload.

Dirty Form Detection

System warns / prevents user from submitting a Workflow Popup if the underlying data has changed since the popup was opened.

System does NOT do any dirty form detection. Values in the incoming file are always treated as valid and not “stale”.

Attribute Visibility

Input fields can be conditionally visible, hiding them from certain users or when certain criteria are met.

Attribute visibility has no meaning to a Data Import Step.

Validation Warnings

Warnings are presented to the user, who is given an option to ignore them and continue anyways.

Warnings are treated as errors and prevent a file row from being processed.

Step Sections

Complex forms can be broken into multiple “sections”, creating a tabbed interface in the Workflow Popup.

Sections have no meaning to Data Import Steps. By definition, import steps always have one, and only one, Section.