PlentyONE Flow

Disclaimer

The full name of the tool is PlentyONE Flow. For simplicity’s sake, the tool is also referred to as Flow throughout this manual.

This first manual page of the PlentyONE Flow area serves as an introduction to the world of PlentyONE Flow. It consists of the following two sections:

  • General summary of PlentyONE Flow: This section gives you a basic understanding of Flow.

  • Structure of the PlentyONE Flow area: This section explains how the PlentyONE Flow area in the manual is structured.

Use the tabs below to switch between the two sections.

  • General summary of PlentyONE Flow

  • Structure of the PlentyONE Flow area

The scope of functions depends on the contract. The following table provides an overview.

Table 1. Contract levels
Function Lite Lite+ Expand Scale Ultimate

Workflow automations

10

15

20

50

500

Drag-and-drop editor

check

check

check

check

check

Workflow tracking

check

check

check

check

check

Workflow import / export

check

check

Note: Once the maximum number of flows has been reached, no new flows can be created or copied, and import/export is no longer possible.

What is Flow?

In Flow, you create, configure, and monitor automated workflows for your daily business processes. Flow is based around the Canvas – the intuitive interface where you map out the steps of each workflow. For this, you use two types of graphic element: actions and controls.

Flow Studio and Flow Tracker

Flow comprises the following two intersecting tools:

  • Flow Studio: Use Flow Studio to create and configure the automated business processes referred to in PlentyONE Flow as flows.

  • Flow Tracker: Use Flow Tracker to manage and monitor Finished flow runs,Flow runs in progress, and Scheduled flow runs. Each instance in which a flow is executed is referred to as a flow run.

The three types of flows in PlentyONE Flow

There are three types of flows available for creating a new flow in Flow Studio, with each named after its trigger type:

  • Event-based: Here, the occurence of a defined event in an order (e.g., a status change) triggers a flow run for that particular order.

  • Time-based: Here, the arrival of a specific point in time (e.g., Tuesday at 9 AM) triggers a flow run for all orders that match the set filter criteria.

  • Manual: Here, a user manually triggers a flow run for selected orders.

The Flow canvas

The Flow canvas is where the sequence of steps for the respective flow is mapped out.

The canvas view is available in both Flow Studio and Flow Tracker, but it behaves differently in each.

  • The canvas view in Flow Studio

    • In Flow Studio, you use the canvas to configure Flows.
      → The canvas is therefore editable.

    • You access the canvas view in Flow Studio when you open an existing flow or - if creating a new flow - after selecting the trigger type (and performing the settings for the trigger type, if these are necessary).

  • The canvas view in Flow Tracker

    • In Flow Tracker, you use the canvas to review and monitor flow runs. The canvas has a primarily informational purpose.
      → The canvas is therefore read-only.

    • You access the canvas view in Flow Tracker when you open an existing flow run.

Actions and controls

You use the actions and the controls to map out the steps of a Flow. To do this, drag and drop the desired actions or controls onto the canvas.

  • Actions: Here, you select the action that will be executed for the orders that reach the respective flow step. Refer to the manual page Use the Flow actions for mor information.

  • Controls: Four types pf controls are available for selection:

    • The Search control is typically used at the beginning of a time-based or manual flow. It searches the system for all orders that match the set filters and passes them to the next flow step.

    • The Branch control is typically used in event-based flows. It creates two possible flow branches for the respective order:

      • If the order meets the set filter criteria, it flows into the True branch.

      • If the order does not meet the set filter criteria, it flows into the False branch.

    • The Start control is used to trigger an additional parallel flow for the orders that reach the flow step.

    • The Adapter control is used to introduce a new, related object type into the flow. .

Refer to the information on the manual page Use the Flow controls for more information.

Preparatory settings

To use Flow, you first need to perform some preparatory settings. This manual page explains what they are.

Chapter:

Working with Flow Studio

In Flow Studio, you create and configure automated workflows, called flows. This manual page and its associated subpages shows you how.

Chapter:

Subpages:

Working with the Flow Tracker

In the Flow Tracker, you review and monitor flow runs. This manual page provides corresponding instructions.

Chapter: