September
Last updated
Was this helpful?
Last updated
Was this helpful?
Azure CosmosDB: new connector that reads and writes records in the CosmosDB database on the Azure cloud platform. .
You can now quickly access the Smart Connector User Experience and easily add a new connection to your flow by clicking the “+” button, available both at the end and middle of the flow. This streamlines the process, reducing clicks and making it easier to add the next step.
Discover more about the connections you can add to your flow with the .
We've added new search filters to the Pipeline Metrics page. You can now filter pipelines by Active and All, including pipelines that haven't been deployed yet. When you select the Active filter option, you can also filter pipelines by the following categories:
Deployed
Redeploy
Error
Degraded
Read the to know how to apply the filters correctly.
We have included new commands on Digibeectl:
Get pipeline: Now it’s possible to see all projects related to pipelines in Digibeectl using the following command:
Rollback command: You can now run a rollback command to restore the previous version of the pipeline that was deployed, using the following command:
Performance improvement in Canvas: we optimized memory to reduce the impact of open and inactive tabs, made visual optimizations to lighten the interface, and simplified element representation to reduce resource consumption.
Run - Pipeline search with page refresh disabled: we’ve fixed the bug on the Run page that continued to search for pipelines disregarding the filters applied by users, even if the page refresh was disabled.
Canvas - Block Execution loses connection with the OnException flow: we’ve fixed the bug where, in some cases, the Block Execution connector lost the connection to the OnException subflow.
Capsules - Account field not recognized when copying and pasting the connector: we’ve fixed the bug that prevented the Account field from being recognized during execution testing when the connector was copied and pasted into the flow.
S3 Storage Connector (AWS) - Items in another language in the Region field: we’ve fixed the bug where one of the items in the Region field list was in another language, inconsistent with the other options.
AES Cryptography Connector - Character limit in the field: we’ve fixed the bug that limited the connector fields to 200 characters.
Build - Fixed incorrect access: we’ve fixed the bug where a user without permissions could access a pipeline that was created in a project they didn't have access to.
Capsules - Loading capsules: we’ve fixed the bug that prevented the capsule's listing page from loading collections, groups and capsules.
Canvas - "Account" parameters on canvas: we’ve fixed the bug when loading the selection fields of parameters of type "Account" on canvas.
Salesforce connector - Bulk operation not working: we’ve fixed the bug that caused the Bulk operation of the Salesforce connector to not work properly.
Salesforce connector - Error loading Object Name: we’ve fixed the bug that prevented the Object Name parameter from being loaded. For this purpose, we have temporarily disabled the AuthToken Reuse for the Salesforce connector.
HL7 connector - Charset ISO-8859-1: we’ve fixed the bug that occurred in Engine V2.
Read the to learn about all Digibeectl commands.
We have included a for Windows to the Digibee documentation portal. We have also updated the to ensure better navigation and usability.
Improvements to the Google Cloud Functions connector: we’ve implemented updates to the connector and its documentation to make it even more intuitive to use. .
DynamoDB: we have added the parameter to the connector, allowing you to configure and specify accounts directly in your pipelines at runtime. Additionally, you can use temporary AWS credentials generated by the connector. .
Store Account: the connector now supports storing accounts, enabling you to securely store and manage temporary credentials. .
Improvements to the Slack connector: we've implemented enhancements to the connector and its documentation to make it even more intuitive to use. .
New SESSION-TOKEN parameter for AWS V4 accounts: you can now directly include an AWS session token when configuring an AWS V4 account. .