Double Braces autocomplete

Learn more about how to autocomplete your Double Braces expressions in the Digibee Integration Platform.

This feature replaces the IntelliSense that was always displayed on the right side of the connector’s configuration form.

Double Braces is an expression language developed by the Digibee Integration Platform that you can use to reference and manipulate data in a flow. Fields that accept Double Braces expressions contain the { } symbol.

Double Braces autocomplete can reference:

  • message.: the data output from the last connector.

  • global.: global variables created in Globals.

  • metadata.: data about the pipeline itself.

  • item.: the way in which certain data is accessed in the JSON Transformer connector.

  • functions: any Double Braces functions.

capsule. and account. cannot yet be referenced by Double Braces autocomplete.

How the Double Braces autocomplete works

To trigger the autocomplete, you must open a Double Braces expression by typing {{ in a field that accepts Double Braces. All available options will be displayed, but you can start typing part of the argument of the expression to filter the options. For example, you can write {{ TOI to find the TOINT function.

You can search for a function in lower or upper case.

When the selection list is open, you can navigate through the options using the arrow keys on the keyboard. Once you have selected an option, click on it press the Enter key (for Windows users) or the Return key (for Mac users) to add it to the expression.

Within the Double Braces expression, you can press Ctrl+Space to trigger autocomplete at any point in the expression. If you want to replace an argument, select the part of the argument you want to replace, press Ctrl+Space, and click on the new argument or press the Enter or Return key.

The message. argument can’t be completed

The message. argument can’t be completed if:

  • The connector has a dynamic output, such as transformation connectors, and the pipeline has not yet been executed. Each time the value of the connector’s output changes, the pipeline must be executed again.

  • The connector is not yet connected to the rest of the flow.

Last updated