General


Lookup List Overview

This tutorial demonstrates how to create and use Lookup Lists in Decisions. Lookup List is a feature that was implemented in Decisions 3.5 and newer. This feature allows to create a specific System Constants...

Folder Aware Flow Behavior

This document demonstrates how to use Folder Aware Flow behavior. In this tutorial we are going to create a Page that can be used on different Folders to display Comments that live in that Folder using...

Flow Designer Wizard Overview

Flow Designer Wizard is created to ease a flow creation process. This Wizard starts up every time we create a new flow. We start this overview from clicking Create Flow in the Designer Folder...

Connecting Steps and Changing Flow Execution Paths

This article describes how Flow Designer Wizard helps to simplify Flow Design process. Next, this article briefly describes using GoTo step to jump between flow steps and Catch Exception step to catch...

Rest Handling for Services

Summary A flow can be made into a REST web service that supports either HTTP GET or POST methods. REST calls to a flow require either (1) valid user session ID, or (2) valid user authentication ID....

Post to Flow Behavior

Summary A flow can be made into a REST web service that supports either HTTP GET or POST methods. REST calls to a flow require either (1) valid user session ID, or (2) valid user authentication ID....

Creating Process Extension Data Structure

Flow execution data extensions are custom data structures that can be attached to process folders for reporting, or to provide contextual data throughout the life of a process. Flow data extensions can...

Adding Actions to Folder Entities with the Flow Designer

Folder entity actions are actions which can be taken upon a folder entity. Custom folder entity actions are built in flows, and saved within a [MyFolderEntity] folder for the entity type, within a Designer...

URL Alias For Flow

Using a URL Alias to route to Decisions A URL Alias is a user defined text that can then be used to call Decisions workflows via Alias Name rather than FlowID or Path. This can be done as an action...

Form Assignment Handler Flows

Automated actions, such as tagging a Form assignment, can occur at the moment a form is assigned by utilizing our Form Assignment Handler flow behavior. Example: This example demonstrates how to tag...

Creating a KB Article via a Flow

Use the Mapping Editor to create complex objects from multiple step inputs. For example, map the output of data entered in form fields to the inputs of an internal service to transform user-entered information into a KB article (Knowledge Base).

Creating Your First Flow

A Flow is a diagram of interconnected components that sequentially execute steps to accomplish a task. Almost all steps result in an outcome, such as true or false, and most output some type of data.

Using the Mapping Editor

Each step in your application's flow accepts a data input and returns a data output for use in the next step. For some steps, multiple sources of data may be available to use as inputs. Use the Mapping...

Using Sub-Flows/Child Processes

When using the Flow Designer, it is possible to embed another flow as a step in your parent flow by adding it from the list of available components. This is referred to as adding a "child process" or...

About Branching and Merging Flows

Branching and merging allows us to process multiple flow steps in parallel, rather than one after the other. You can create branches and mergers by dragging and dropping the Branch Step and Merge Step...

Running a Flow from a URL

It is possible to run a flow just by accessing its URL. The URL can be copied to the clipboard and emailed to a user, or bookmarked, for example. The URL can be lengthy, and one way to make it more...

Running a Flow On a Schedule

Some flows should capture or transform data on a regular basis. Your application may require that flows run on an hourly, daily, weekly or monthly schedule. The Job Schedule wizard steps you through...

Creating Your First Form Flow

A form displays controls that allow a user to perform an action, such as enter data, display a report or folder, or manage entities. You can create a flow that, when run, opens a form. Create a new...

Building an Array or List of Items

The Array Builder is a simple way to aggregate multiple variables into single input. It can be found in the Mapping Editor, under the input type Build Array. Example Our example flow will display a...

Using Rule Steps in a Flow

Rule Steps evaluate a data input and return an outcome of true or false depending on whether the input satisfies the conditions of the rule(s) they contain. Rule Steps can contain entirely original rules,...

Changing Output Data Mappings

Most steps in your application's flow will return a data output for use in the next step. In cases where that data must be reorganized such as being renamed, ignored, combined into an array, or broken...

Mapping a Complex Object

Use the Mapping Editor to create a complex object from multiple step inputs. For example, map the output of data entered in form fields to the inputs of an internal service to transform user-entered information into a Knowledge Base article.

Using the No Data Result Path

If a flow step requires input but the input is not provided, the flow will stop running. For example, if a step requires input data from a user-completed form and the user submits the form with no data...

Managing Contact Information with the Flow Designer

The Contact Info Entity is a folder entity which collects addresses, phone numbers, email addresses and other contact details into a single entity. These contact details can be updated and deleted in...

Using Placeholder Components to Sketch Out Flow Structure

The Placeholder Step component simulates a working component by providing simulated outcomes or objects. It has no function except to describe a component to be inserted at a later date. Use a placeholder...

Outputting Data Objects From Rule Steps

Rule Steps can be configured to return data objects rather than simple outcomes. For example, you can create a rule that outputs an account object that can then be displayed in a form. In the Properties...

Adding a Step Outcome for Exceptions

Even under the best conditions, inputs can be unreliable. To handle missing or invalid data without crashing, steps need paths to account for errors or exceptions. We can add these outcome paths by selecting...

Adding Outcome Data to Step Output

When a step is placed within a flow, its outputs are automatically given path names that follow some basic default rules. To help you make these path names more meaningful, the Flow Designer offers controls...

Expose Step as a Rule

This tutorial demonstrates how to Expose Step as a Rule. This step configuration is available for any step in Decisions that has True/False outcome (including Rules). Expose Step as a Rule is helpful...

Catching All Unconnected Outcomes

The Catch Outcome component listens to unconnected flow outcomes and provides a universal mechanism for handling them. To add the component to a flow, in the Flow Designer's Components panel, under...

Catching All Unhandled Exceptions

An exception is an anomalous or exceptional situation in a flow requiring special processing. Exception handling is the response to this occurrence. The platform provides two ways to catch exceptions....

Running Unit Tests from the Flow Designer

The Unit Tester organizes test data and scenarios. Unit tests can check for flow success, failure, errors or lack of errors. To manage unit tests, open a flow in the Flow Designer and select the Debug...

Swimlanes

A Swimlane (or swimlane diagram) is a visual element used in process flow diagrams, or flowcharts that visually distinguishes job sharing and responsibilities for sub-processes of a business process. Swimlanes...

Fetching Report Data in the Flow Designer

Report components make report data available for use in flows. Report components can be found in the Toolbox tab, under the category Integration > Reporting. Example In our example flow, we will...

Run Flow Async From Sync Step

This tutorial demonstrates how to use Run Flow Async And Wait configuration for the Sub-Flow steps. Run Flow Async And Wait is an advanced configuration and should be used with caution. It is important...

Moving Folder Entities with the Flow Designer

Folder entities can be moved with the Move Entity component. It can be found in the Toolbox tab, under the category Integration > Entity Framework. Example In our example flow, we will use two forms...

Adjusting at runtime what sub flows are run from flow engine

Flows can call sub flows. The choice of which sub flow is called can be made at design time (see: Using Sub-Flows) or at run time. This article shows how to configure your flow to determine which sub...

Navigating to page at end of flow interaction

Flows can be used to control portal navigation. This example will show how to navigate to a specific folder/page using a flow.   Example Before creating a flow, you need to know the id of the folder...

Overview of the Process View Page

The Process View Page provides a snapshot of where a process resides. The name and the description of the process display, and its current state is in the upper right of the screen. The current assignment...

Establishing Constant Data (Global Variables)

The Portal provides the ability to store constant values for reuse in flows. This is a way of creating "global data." It is useful because when a change is needed, the data itself is updated in one...

Using Validation Engine for Entities

A folder entity can have validation applied, set up in the form of rules or a flow created by the entity's action folder. Setting up validation rules is particularly useful if the Action menu is...

Exposing Flow as a Web Service

Decisions flows can be exposed as an external web service. This allows external applications to utilize this flow via a standard SOAP web service call.   Example Create a new flow. Click on any blank...

Using Collection Sort Step

This tutorial demonstrates how to configure and use Collection Sort Step. This step can be found under All Steps [Catalog] > Data > List category in the Flow Designer. With this step we can implement...

Cache Fetch Flow Behavior

This tutorial demonstrates how to use Cache Fetch Flow Behavior. This Flow Behavior can be used to fill the cache in with data that we need to keep for a certain time. Additionally, this tutorial demonstrates...

Retrieving Contact Information with the Flow Designer

The Contact Info Entity is a folder entity which collects addresses, phone numbers, email addresses and other contact details into a single entity. These contact details can be retrieved in a...

Time Zones in Decisions

Time zones in Decisions are derived from the Time Zones recorded in Windows 2008 Server. When time-shifting dates and times between time zones, be sure to use the Time Zone Value rather than the Display...

Asynchronous Invoking of Sub-Flows/Child Processes

There are two ways to call a subflow: 1) The "non-asynchronous" method, which is what is used when you simply drag and drop a flow into the Flow Designer workspace, or use the Flows > [Pick or Create]...