Skip to main content

And Operator

The And Operator object is used to merge multiple parallel branches or approvals in a workflow and only proceeds when all incoming branches have completed.

AndOperator

And Operator Object

The And Operator object is used in process flows where multiple parallel tasks or approvals are expected to converge at a single point before the workflow continues. This ensures that all parallel branches complete their tasks or approvals before the flow moves forward.

It is especially useful in scenarios such as:

  • Sending tasks to multiple positions or groups in parallel.
  • Awaiting all branches to return results before continuing to the next step.

How It Works

  • The And Operator object waits for all incoming connections to complete their executions.
  • Once every branch connected to the object has finished, the process is allowed to continue from the single outgoing path.
  • If even one of the incoming branches has not completed, the flow remains paused at the And Operator.

Rules and Restrictions

  • You can connect multiple incoming paths (n inputs).
  • The object only allows one outgoing path.
  • The merging logic is synchronous: the next action occurs only after all branches return results.

Usage Steps

  1. Drag the And Operator object from the Toolbox onto the Flow Designer canvas.
  2. Connect all relevant parallel branches to the object using arrows.
  3. Connect a single outgoing arrow from the object to the next step in the workflow.
  4. Click the object to configure its properties in the Properties Viewer panel.

Properties Panel Overview

When selected in the design view, the And Operator displays the following configuration tabs:

1. Appearance

  • Object Name: Internal system name for referencing in code.
  • Caption: Display name shown in the UI.
  • Is Lock: Prevents movement of the object during design.
  • Size: Dimensions of the object (width and height).

2. Properties

  • The And Operator does not require additional custom properties beyond connections.

3. Events

  • Custom events can be handled via the Events tab. Event methods can be generated and customized with specific logic.