April

Release notes 04-02-2024

Components

  • DynamoDB (Beta): we’ve upgraded the component from Restricted Beta to Beta. DynamoDB allows pipelines to perform operations against DynamoDB database tables in AWS. Learn more in the DynamoDB documentation.

  • Configuration form improvements (General Availability): we’ve improved the user experience of the configuration form that allows the user to set up components and triggers. Now, the configuration parameters are divided into specific tabs according to the needs of each component. This improvement is currently available for the Salesforce and DynamoDB components.

Double Braces autocomplete (General Availability)

The Double Braces autocomplete is an update to the experience of creating Double Braces expressions.

When a user creates an expression, the autocomplete displays information from the previous component’s output, as well as global variables, metadata, and functions.

This enhancement to Double Braces replaces the IntelliSense that was always displayed on the right side of the component’s configuration form.

Learn more in the Double Braces autocomplete documentation.

Pipeline documentation in Portuguese (General Availability)

The Pipeline documentation with AI is now also available in Portuguese.

Important: the documentation language will be linked to what was configured in your browser.

Learn more about Pipeline documentation with AI.

New configuration form for Capsules (General Availability)

We’ve promoted the new configuration form for Capsules to General Availability. We’ve improved the form design and its configuration. With this update, the Parameters and Accounts tabs are now combined in a Form tab, which reduces the complexity of the configuration.

Learn more about how to configure a Capsule.

API Management (Beta)

Now, with the API Management page, users have more autonomy to generate their own credentials to authenticate access to the Digibee Integration Platform API metrics.

Learn more in the API Management documentation.

HTTP headers policies (Beta)

The HTTP headers policies are two new transformation policies that allow users to manipulate and transform their HTTP headers during an HTTP response for all their pipelines at once.

The policies we're introducing are:

  • Custom HTTP header: users can add any custom headers in this policy to provide information about the response of the pipeline. Learn more in the Custom HTTP documentation.

  • CORS HTTP header: users can add CORS headers in this policy. CORS stands for Cross-Origin Resource Sharing and is an HTTP header-based mechanism that allows a server to specify origins other than its own, such as domain, scheme, or port, from which a browser should allow resources to be loaded. Learn more in the CORS HTTP documentation.

Update in License Usage page for pipeline and capacity-based models (General Availability)

This update is an improvement to the License Usage page for pipeline and capacity-based models.

Now, the licenses or credits for the different environments are displayed in a single card, with a bar splitting the licenses or credits for each environment.

We’ve also unified the project list to display all environments in one place.

Learn more in the License Usage documentation.

Digibee Academy — Mini-challenges

We’ve launched our first set of Mini-challenges, the perfect opportunity for you to test your integration knowledge on Digibee Academy.

The list includes:

  • Field mapping with JOLT

  • Log Stream

  • OAuth2

  • Transformations and Aggregations of JSON using JOLT

  • Database extraction with pagination control

  • Circuit breaker

  • Working with files and data transformation​ ​ ​

We’ve also fixed a few bugs: ​

  • Components — SOAP V3: we’ve fixed the bug preventing the user from correctly visualizing the “Account” field.

  • Components — Memchaced: we’ve fixed the bug that caused a TLS connection error when using the component.

  • Canvas — Pipeline documentation: we’ve fixed the bug where the documentation generated incorrect information about the REST trigger. This occurred within the pipeline documentation when creating a PDF.

  • Canvas — Pipeline documentation: we’ve fixed the bug where, depending on the size of the pipeline, some documentation wasn’t generated.

  • Canvas — Execution panel: we’ve fixed the bug where the logs were duplicated in the Execution panel.

  • Canvas — AI Assistant for flow creation: we’ve fixed the bug where the AI Assistant was displayed in the connection between the trigger and the first component.

  • Build — Pipeline list: we’ve fixed the bug that occurred when an empty project was opened, and the button to create a new pipeline in the project had no content.

  • Build — Capsule collection: we’ve fixed a bug that allowed users to save the Capsule collection form with information missing, and the collection wasn’t created.

  • Run — Special characters and symbols: we’ve fixed the bug that prevented the user from interacting with and visualizing items within a project if the title had special characters and symbols.

  • Run — Deployment process messages: we’ve fixed bugs that displayed incorrect deployment messages, such as restore version status, confirmation, and number of available licenses.

  • Run — Search: we’ve fixed bugs on search functionality that didn’t display or change results when using the projects filter.

  • Administration — Groups: we’ve fixed the bug where the page got blank when editing a group.

Last updated