April
Last updated
Was this helpful?
Last updated
Was this helpful?
We've made improvements to optimize the performance of the Build page, where all pipelines and projects are listed. Loading the information on the page now takes much less time, which improves the user experience.
Canvas - Double Braces autocomplete doesn’t retrieve globals: we’ve fixed the bug that caused the Double Braces autocomplete to not find global variables for completion, even if they were present in the Globals page.
Canvas - Infinite suggestions in Double Braces autocomplete: we’ve fixed the bug that displayed suggestions in autocomplete when no suggestions should have been displayed.
Canvas - Scrolling and clicking doesn’t work in Double Braces autocomplete: we’ve fixed the bug that caused scrolling and clicking with the mouse in Double Braces autocomplete to not function properly.
Canvas - Double Braces highlight doesn’t work for lowercase functions: we’ve fixed the bug where highlighting in Double Braces expressions didn’t work when functions were written in lowercase.
Canvas - Integer values are changed in the Execution panel: we’ve fixed the bug that caused the integer values to change in the Execution panel.
Pipeline - White screen for pipelines when using Capsules: we’ve fixed the bug where a white screen appeared when running the pipeline or opening the Capsule configuration if the Capsule had too many parameters.
Capsules - Generic error when trying to move a Capsule: we’ve fixed the bug where an incorrect error message was displayed when users tried to move a Capsule to another collection that had a different Capsule with the same name. Now the displayed message correctly reflects the error.
Capsules - Distorted image of the header in the list of collections: we’ve fixed the bug that distorted the header image in the collections list by removing the header from the sidebar and making it visible only in the Capsule icon.
Capsules - Incorrect error message when validating the Capsule name: we’ve fixed the bug that displayed an incorrect error message if the name of a Capsule exceeded 60 characters.
Capsules - Capsules are not saved: we’ve fixed the bug that Capsules were not saved even if the name matched all rules.
Capsules - Two properties with the same name cause the Capsule configuration form to crash: we’ve fixed the bug that caused the Capsule configuration form to crash when multiple parameters had properties with the same value.
Capsules - Restriction when moving capsules between groups: we’ve fixed the bug that prevented users from moving Capsules to different groups within the same collection.
Capsules - Capsules with the special character at (@) are saved: we’ve fixed the bug that allowed users to save Capsules with the at (@) character, although this shouldn't be allowed.
Components - Double Braces: we’ve fixed a bug that prevented the use of Double Braces expressions containing tab (\t).
Components - Salesforce: we've fixed a bug that caused an error when using Bulk 2.0 API protocol and entering Bouble Braces in the body of the CreateJob operation.
Components - Memcached: we've fixed a bug that prevented the user from using the connector with an AWS Memcached serverless account.
Profile - Profile picture is not displayed: we’ve fixed the bug where the profile picture wasn't displayed immediately after uploading and the user had to refresh the page to see the changes.
Globals - Incorrect validation in the name of a global variable: we’ve fixed the bug that displayed an incorrect error when creating the name of a new global variable.
Monitor - we’ve fixed the bug that didn’t allow to close the execution Details side-sheet at the completed execution section using the 'Esc' short key.
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.
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.
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.
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.
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:
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.
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
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.
AuroraDB support for DB V2 and Stream DB V3 (General Availability): we’ve released an update for the DB V2 and Stream DB V3 connectors that allows users to perform operations with AWS AuroraDB in their pipelines in the same way they are used to with other database engines such as MySQL, Oracle and others supported by Digibee. For more information, see the following documentation: , , and .
DynamoDB (Beta): we’ve upgraded the component . DynamoDB allows pipelines to perform operations against DynamoDB database tables in AWS. Learn more in the .
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 and components.
Learn more in the
Learn more about .
Learn more about .
Learn more in the .
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 .
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 .
Learn more in the .
We’ve launched our first set of Mini-challenges, the perfect opportunity for you to test your integration knowledge on .
