Integration flows

Trigger node

The trigger node is the starting node of a flow. It contains the global configuration for the flow, including parameters, timeout settings, and policies. The trigger node is a value-carrying node. You can reference the user-configured parameters with trigger.data.

Parameter descriptions:

Integration action node

Integration action nodes have multiple action types, such as script, SQL, and Model Studio applications.

async () => {
  // your code here
}

if node

The if node works like an if...else statement in a programming language, as shown in the following example:

if (condition) {
  // statement 1
} else {
  // statement 2
}

An if node consists of the following three parts:

• Condition [Required]: A JavaScript expression that evaluates to a Boolean value.

• if node collection [Required]: The collection can contain any nodes.

• else node collection [Optional]: The collection can contain any nodes.

while node

The while node works like a while loop in a programming language, as shown in the following example:

while (condition) {
  // statement
}

A while node consists of the following two parts:

• Condition [Required]: A JavaScript expression that evaluates to a Boolean value.

• Node collection [Required]: The collection can contain any nodes.

try node

The try node works like a try...catch statement in a programming language, as shown in the following example:

try {
  // tryStatements
} catch (exception) {
  // catchStatements
} finally {
  // finallyStatements
}

A try node consists of the following three parts:

• try node collection [Required].

• catch node collection [Optional]: Nodes within the catch collection can access the caught exception using the error keyword. The error object contains code and message properties.

• finally node collection [Optional].

throw node

The throw node works like a throw statement in a programming language, as shown in the following example:

throw expression;

It is usually defined within a try node collection. The thrown error is handled in the catch node collection.

The following table describes the configuration items.

Variable node

The variable node works like let in JavaScript. It declares a block-scoped local variable that can be reassigned, and you can optionally initialize it to a value.

You can assign values in two ways within an integration flow:

• Explicit assignment: Use an assignment node to assign a value.

• Implicit assignment: Set the value of the node object's data property in a script or expression. For example, variableId.data = xxx.

Assignment node

The assignment node explicitly assigns a value to a variable node.

An assignment node consists of two parts:

• Assignment target: The variable to be assigned.

• Value: A JavaScript expression.

User task node

The user task node lets you temporarily interrupt an integration flow and wait for user input. For more information, see User task nodes and interruptible integration flows.

Return node

The return node works like a return statement in a programming language. The value returned by the return node becomes the execution result of the entire integration flow.

Scope is the current execution context where values and expressions are "visible" or accessible. If a variable or expression is not in the current scope, it is unavailable. Scopes can also be stacked in a hierarchy. A child scope can access its parent scope, but not the other way around.

Simulation parameters

Simulation parameters display the node data that the script or configuration of an integration node (action node) depends on.

The simulation parameters are displayed as a JavaScript object. The object's properties are the IDs of the nodes referenced in the configuration items. The values are the node object values, which are null by default.

The following are three exceptions:

• The trigger simulation data that is set in the trigger panel is globally available.

• The referenced node is a variable node. Mobi reads the value from that variable node's configuration. If the variable expression has no external node references, the result can be obtained directly using `eval`.

• If the referenced node is an integration node and already has a test result, that result is used as the default value.

You can add, edit, or delete simulation parameters. You can set the values as required. These values are used as parameters for testing the node.

Test results

The figure shows the test status indicator. Different colors represent different statuses. The three statuses are as follows:

• Gray: The test is pending.

• Green: The test is successful. The execution succeeded and a result was obtained.

• Red: The test failed. The success identifier in the returned result is `false`. You can adjust the configuration or code based on the error message.

The content area displays the test result. The result remains displayed until you run another test or the simulation parameters change.

Test/Run

This button runs the flow or executes the integration action based on the configuration information and simulation parameters.