August
Last updated
Last updated
JSLT Component (Beta): we’ve created a new component that allows the manipulation of JSON content through JSLT technology. Learn more in the JSLT documentation. This feature is currently in the Beta phase.
Updates for Basic Auth for HTTP, HTTP File, and REST triggers (Beta): we’ve updated the following configuration details, as shown in the Consumers (API Keys) and HTTP trigger, HTTP File trigger, and REST trigger documentation.
When configuring a Basic Auth credential, the created username receives the prefix {realm}, as in: {realm}-{username}.
The Rate Limit parameter is only visible if the API Key or Basic Auth parameters are enabled.
The Aggregate By parameter displays the following options: Consumer or Credential (API Key, Basic Auth).
Store Account (Restricted Beta) and all components that support dynamic credentials now have the Scoped flag. This allows these components to be executed within stream blocks in parallel without overlapping data and race conditions.
We recommend validating expressions when configuring the JSON Path parameters in the For Each, Stream JSON File Reader, and JSON Path Transformer components. This precaution ensures that pipelines work more accurately and helps prevent errors.
We are launching the Group restoration feature under Groups, and it allows you to restore groups that might have been archived accidentally or intentionally at any time, keeping the same users that already belong to them.
By restoring a group, users who belong to it will have the permissions given by this group again as long as they are active. Learn more in the Groups documentation.
When the user clicked on the magnifying glass in the Actions column, they were redirected to the Completed executions page inside the Overview page. That, sometimes, caused some of the information, like the ones entered in the filters, to be erased. Now, when users click on the magnifying glass, they are still redirected to the same Completed executions page but in a new tab, keeping all the previously entered information.
Learn more in the Completed executions documentation.
Now, the user has the option to send notification alerts using a webhook, in addition to e-mail and Telegram. The user must also provide the endpoint needed to activate the webhook.
Learn more in the Alerts documentation.
The Alerts feature is currently in the restricted beta phase and is only available to specific customers. If you would like to access this feature, please contact support or your CSM. Learn more about the Beta Program.
We are launching 4 new Monitor notification alerts, as detailed below:
Pipeline memory usage: it shows the average percentage of memory usage for each replica of the pipeline for the interval in the selected time period.
Pipeline response time: it shows the average time (in milliseconds) it took the pipeline to generate a response for all replicas.
Pipeline message size: it shows the average request and response message size (in bytes) for all pipeline replicas for the interval in the selected time period.
Pipeline inflight executions: it shows the total number of inflight executions (in messages) of all pipeline replicas for the interval in the selected time period.
Learn more in the Alerts documentation.
The Alerts feature is currently in the restricted beta phase and is only available to specific customers. If you would like to access this feature, please contact support or your CSM. Learn more about the Beta Program.
Roles - List of selected bindings: we’ve fixed the bug that when selecting new role bindings, they were not sorted in the order they were selected.
Roles - Saved role bindings: we’ve fixed a bug where group bindings were not displayed in alphanumeric order after being saved.
Roles - Selection of role bindings: we’ve fixed the bug where roles already linked to the group kept appearing in the available selection list.
User profile menu: we’ve fixed the bug that the Create button overlapped the user profile menu.
Canvas - Execution panel validation: we’ve fixed the bug in which the Payload editor of the Execution panel wasn’t validating duplicated properties, like the old Test mode.
Basic Auth for REST, HTTP, and HTTP File triggers (Beta): Basic Auth is an authentication method that uses Base64 encoding to avoid unauthorized access. This feature update is currently in Beta phase. Learn more about it in the Consumers (API Key), and REST, HTTP, and HTTP File triggers documentation.
Filter and sort account list for connectors components (General Availability): we’ve improved all connectors components that use an account list (learn more in the Accounts documentation). Now, the user can view only the supported accounts for a specific connector component in alphabetical order. The documentation for each connector component also lists the supported accounts in the configuration parameters.
This is an exclusive new feature of Engine V2 that allows the user to change their credentials configurations on the Runtime page through the Store Account component.
Learn more in the supporting dynamic accounts documentation.
Digibee Integration Platform can now be installed and run on Elastic Kubernetes Service (EKS), Amazon's Kubernetes management service. This implementation adds another option for fully cloud-native workflows to our suite of capabilities for dedicated SaaS customers.
Learn more in the EKS documentation for dedicated SaaS customers.
Now, it’s possible to document the purpose of components and triggers in their configuration forms, making troubleshooting and collaboration in pipeline creation easier and more efficient.
Learn more about the Documentation field on Canvas.
We’ve improved the user experience of viewing and editing Permissions on the Users, Roles, and Groups pages:
We’ve changed the Permissions component in the configuration table on these pages.
We've added a tooltip to the subject in the specific permissions column.
We've included the link to our documentation above the Role permissions configuration table.
In the Specific column, we now take into account the number of permissions selected when more than one item is selected.
Learn more in the Users, Roles, and Groups documentation.
Our IdP accesses page has been upgraded from Restricted Beta to Beta phase, and it’s available to all clients who have set up their Identity Providers (IdP). Note that with this change, the access manager can control the login method of users in a realm with Single Sign-On (SSO).
Learn more in the IdP accesses documentation.
The number of failed login attempts remaining is displayed on the login unlock page, and the counter is reset for each successful attempt.
Learn more in the Login flow documentation.
When an active group integration is archived, its status automatically changes to inactive. When all active group integrations are archived, the realm becomes non-federated again.
Learn more in the Integration of IdP groups with Digibee groups documentation.
The metric Messages on queue informs users when the volume of incoming requests requires an increased number of pipeline replicas to increase available processing capacity.
The Alerts feature is currently in the restricted beta phase and is only available to specific customers. If you would like to access this feature, please contact support or your CSM. Learn more about the Beta Program.
Now, users can rollback the pipeline to a previously working deployed version.
Learn more in the Rollback of deployed pipeline version documentation.
Now you can promote a deployed pipeline across environments into production. Then, it’s deployed and immediately available for use in your chosen environment.
Read more in the Promoting pipelines across environments documentation.
Don't miss out on this fantastic opportunity to expand your knowledge and make your way toward integration independence on the Digibee Integration Platform:
Our webinars Event Driven Architecture I and Level up your pipelines working with files now have subtitles in English, Spanish, and Portuguese. Check it out on Digibee Academy!
You can also access our AI Assistant directly from the Digibee Integration Platform! Click on the "?" (question mark) icon in the menu just below the Documentation.
Canvas - Choice structure: we’ve fixed the bug that sometimes incorrectly pasted the structures that contained the Choice component.
Canvas - Images of Components: we’ve fixed the bug that made the images of some components unavailable.
Canvas - Linter alert for Session: we’ve fixed the bug where Linter incorrectly reported that the Session component variable was not used when the flow contained a Session component that had a PUT request inside an OnProcess, another Session component that had a GET request outside that OnProcess, and the first component's OnException was empty.
Canvas - Disconfigured Choice: we’ve fixed the bug that disconfigured the name of the Choice component conditions and prevented the pipeline from running if there were more than ten conditions in Choice.
Users: we’ve fixed the bug that sometimes didn’t return records when searching only for the user's full name or last name.
Components - Script: we’ve fixed a bug that affected the Script component.
Components - REST V2: we've fixed a bug that caused incorrect behavior when doing API calls using the REST V2 component.
