Displays the Applications available in Integration Cloud.

Use the Service blocks (date, math, string, and so on) to specify the service that will be invoked at run time. Related services are grouped in blocks. You can sequence services and manage the flow of data among them.

Displays the list of Integrations created in Integration Cloud. You can invoke an Integration from another Integration. When copying integrations from one stage to another, all the referred Integrations and their dependents will also be copied.

Click Duplicate to repeat a block, click Collapse to flatten a block, click Delete to remove a block from the workspace, or click Disable to disable a block and all blocks within that block. If you disable blocks, those blocks will not be considered for execution, test, or debug operations.

Conditional expressions, looping structures, and transform pipeline.

Conditional expressions perform different computations or actions depending on whether a specified boolean condition evaluates to true or false.The if block is used to evaluate a boolean condition and if the condition is true, statements inside the if block are executed. The if statement can be followed by an optional else statement, which executes when the boolean expression is false.

The if statements are executed from the top towards the bottom. You can use one if or else if statement inside another if or else if statement(s). You cannot have multiple else statements.

The try catch block is used to handle errors and exceptions. If you have a statement in the try block that has thrown an error, the error will be caught in the catch statement.

Loops execute a set of steps multiple times based on the block you have chosen. It repeats a sequence of child steps once for each element in an array that you specify. For example, if your pipeline contains an array of purchase-order line items, you could use a Loop to process each line item in the array. Loop requires you to specify an input array that contains the individual elements that will be used as input to one or more steps in the Loop. At run time, the Loop executes one pass of the loop for each member in the specified array. For example, if you want to execute a Loop for each line item stored in a purchase order, you would use the document list in which the order’s line items are stored as the Loop’s input array.

The while loop is used to iterate a part of the program several times. If the number of iterations are not fixed, it is recommended to use the while loop.

The do-until loops are similar except that they repeat their bodies until some condition is true.

The for-each block traverses items in a collection. Unlike other for loop constructs, for-each loops usually maintain no explicit counter: they essentially say “do this to everything in this set”, rather than “do this x times”.

The Exit Integration signaling success block allows you to successfully terminate and exit from the currently running Integration. You cannot attach child blocks to the Exit Integration signaling success block.

The Exit Integration signaling failure "…" block abnormally terminates the currently running integration with an error message. You can specify the text of the error message that is to be displayed. If you want to use the value of a pipeline variable for this error message, type the variable name between % symbols, for example, %mymessage%. The variable you specify must be a String. You cannot attach child blocks to the Exit Integration signaling failure "…" block.

The Throw error "..." block can be attached inside any block except the catch section of the try catch block, and allows you to explicitly throw an exception with a custom error message. If it is used inside the try section of the try catch block, the error will be caught in the catch section. If you want to use the value of a pipeline variable for this custom error message, type the variable name between % symbols, for example, %mymessage%. The variable you specify must be a String. You cannot attach child blocks to the Throw error "..." block.

The Break out of loop block should be used only within a loop and allows you to break out of the containing loop, that is, it allows you to break the program execution out of the loop it is placed in. You cannot attach child blocks to the Break out of loop block.

A Loop takes as input an array field that is in the pipeline. It loops over the members of an input array, executing its child steps each time through the loop. For example, if you have a Integration that takes a string as input and a string list in the pipeline, use Loops to invoke the Integration one time for each string in the string list. You identify a single array field to use as input when you set the properties for the Loop. You can also designate a single field for the output. Loop collects an output value each time it runs through the loop and creates an output array that contains the collected output values.

Use the Transform Pipeline block to make pipeline modifications. See Pipeline and Signatures for more information.

Logical operations, comparisons, and values.

The six comparison operators are: equal to, not equal to, less than, less than or equal to, greater than, greater than or equal to. Each takes two inputs and returns true or false depending on how the inputs compare with each other.

The and block will return true only if both of its two inputs are also true. The or block will return true if either of its two inputs are true. The not block converts its Boolean input into its opposite.

You can also type a text value, select a field on which to build an expression (Select field), or select a block with no inputs.

The Field exists block allows you to check if a variable exists or not and can be used with other Control Flow blocks, for example, the if block. The Field exists block validates the existence of a particular field in the pipeline.

Only for the Control Flow block and the Root block.

Comments for the Control Flow block and the Root block. Click the Show comments inline check box to view the comments entered for the blocks.

Applications, Services, Integrations, and the Root block

You can use a Document Reference to define the input or output parameters for an Integration. If you have multiple Integrations with identical input parameters but different output parameters, you can use a Document Type to define the input parameters rather than manually specifying individual input fields for each Integration. When you assign a Document Type to the Input or Output side, you cannot add, modify, or delete the fields on that part of the tab.

You can select a Document Type from the Document Reference drop-down list. To create a Document Type, from the Integration Cloud navigation bar, select Projects > <Select a Project> > Document Types > Add New Document Type. See Document Types for more information.

You can create pipeline variables as document references, create document types comprising of document references, and also define the signature of Integrations comprising of document references.

See Creating Document Types from Scratch for more information.

Select the Validate input and Validate output options if you want to validate the input and output to the Integration, against the service input or output signature.

Integration Cloud allows you to log select business data from the Operation and Integration signatures either always, or only when errors occur. Values of logged fields can be viewed in the Only Business Data section in the Execution Results screen. You can also create aliases for the logged fields.

When selecting fields for logging, you can create the same alias for more than one field, but this is not recommended. Having the same alias might make monitoring the fields at run time difficult.

Map the input of the operation from the Pipeline and also map the output of the operation into the pipeline.

You can select a block, other than the root block, and click Duplicate to repeat a block, click Collapse to flatten a block, click Delete to remove a block from the workspace, or click Disable to disable a block and all blocks within that block. If you disable blocks, those blocks will not be considered for execution, test, or debug operations.

Control Flow > Transform Pipeline

Make pipeline modifications. Edit data mapping, add Transformer, clear all mappings, add, delete, edit, or discard a field, set a value for a field and perform pipeline variable substitutions.

Applications

Select an Account and an Operation for the Application.

Applications

The block is not configured. Select an Account and an Operation for the Application.

Services

The block is not configured. Select a service.

Orchestrated Integrations

Click to view or modify an Orchestrated Integration after it is moved to the workspace. The Orchestrated Integration will open up for editing in a new tab.

Orchestrated Integrations

An Orchestrated Integration has been modified or newly created but not saved.

A breakpoint is a point in an Integration where you want processing to halt when you debug that Integration. Breakpoints can help you isolate a section of code or examine data values at a particular point in the execution path. For example, you might want to set a pair of breakpoints before and after a particular block so that you can examine the pipeline before and after that block executes.

Breakpoints are recognized only when you execute an Integration in debug session. To insert a breakpoint, in debug mode, click the top-left corner of the block. To remove a breakpoint, click on the inserted breakpoint.

When you execute an Integration that contains a breakpoint, the Integration is executed up to, but not including the designated breakpoint. At this point, processing stops and the debug session suspends. To resume processing, select Resume. After you resume the debug session, the Integration flow stops at the next breakpoint.

Ignores all breakpoints inserted in the Integration blocks. You cannot insert breakpoints for variables in the Expressions category.

Executes the current block. Integration Cloud suspends the debug session immediately before executing the next block in the Integration.

The debug session resumes but suspends at the next breakpoint.

Terminates the debug session.

A debug session may also stop by itself for the following reasons:

Removes all breakpoints inserted in the Integration.