Process Steps Reference

A Process is comprised of a series of steps that dictate how the Process retrieves, manipulates, routes, and sends data from source to destination. Steps can be connected together in endless combinations to build simple to very complex integration work flows.

Each step has its own set of configuration options. The configuration often references other components such as Profiles, Maps, Connections, and Operations.

To add a step to a Process, drag and drop the icon from the palette on the left side of the Process Builder onto the canvas.
To edit a step already on the canvas, double click it to display the configuration options.
To remove a step from the canvas, click the step to select it and press the delete key on the keyboard.

Special Steps

Start

Gets data into the Process. The Start Step is simply a mandatory "Get" Connector at the beginning of every Process. The Start Step is automatically added to your Process and cannot be removed.

Execution Steps

Execution steps manipulate the Document data.

	Connector	Gets data into the Process or sends data out of the Process.
	Data Process	Manipulates data with one or more processing steps, including document splitting, zip/unzip, and custom scripting.
	Set Properties	Sets Connector-specific properties (such as Disk file name, FTP directory, Mail subject, etc.) for Documents as well as global Process properties.
	Map	Transforms data from one format (Profile) to another.
	Message	Generates free-flow text messages with both static and dynamic content.
	Process Call	Executes another Process from within a Process.
	Program Command	Executes commands including calling database SQL and stored procedures and invoking command line scripts.

Logic Steps

Logic steps direct the flow of Documents through the Process.

	Branch	Creates a copy of a Document and passes it down each branch in sequential order. A branch is executed to completion before the next branch is executed. If a Document errors on one branch it will not continue down subsequent branches.
	Cleanse	Repairs or rejects Documents by validating field-level restrictions defined by the data Profile.
	Decision	Routes Documents based on a true/false comparison of two values. Comparison values can be static or dynamically pulled from Document Properties or actual document data.
	Exception	Terminates the Document execution and generates a user-defined error.
	Route	Routes Documents conditionally down different paths based on some value. Routing values can be static or dynamically pulled from Document Properties or actual document data.
	Stop	Ends the current execution path without generating an error.