Turn the way you work into an executable process.

Drag nodes from the NodeTemplate library onto the canvas and connect them into a process. Combine interface elements with nodes such as Expressions and Functions for calculations and actions.

Every process starts at a Root node. Execution follows one path at a time. That path can branch, merge and loop back to an earlier step. This structure is called a Control Flow Graph.

A process without a user interface is called headless. The process engine runs non-interactive nodes autonomously. A process with an interface is started by a user from a client, for example through a dashboard or dataview.

When execution reaches interface nodes, the elements from that cycle are sent together to the client. It displays them in the browser or the Android and iOS mobile app. The process then waits for an interface event, such as clicking a button or a table row, before continuing.

• The same process logic can handle data and ask for input along the way.
• The interface can change from one step to the next as the process advances.
• Interactive processes require a user and a client; headless processes contain no interface.

Build a form from available input components. Combine everyday fields with record selection, files or information captured on location.

Use buttons, icons, images, labels, labels with an icon or badge, maps, popups, multiline text and timers. An interface element can display information, collect input or combine both.

Events from supported interface elements move the process forward. A button can confirm a step, while selecting a row can continue the process with the chosen Asset.

One process can start another directly or place it in a queue. In the latter case, a Flow Service picks it up for execution in the background.

Input arguments pass information into a process. Output nodes at the end of a process path can return a result. This lets you use a process as a subprocess or function and avoid rebuilding the same logic.

Connect a process to opening an Asset or to the add button in a dataview. When a user clicks an Asset, that Asset can be passed as an argument.

On an Asset dashboard, a process button can pass the current Asset. Choose a popup or navigate to the process. An inline process widget displays the interface directly within the dashboard; users can scroll if the content exceeds the available space.

For example, a report could open a handling process that asks for a comment and updates its status. You configure the steps and actions to match the task.