May

Release notes 05-21-2024

Connectors

  • Stream Avro File Reader (General Availability): we released a new connector for reading Parquet files that triggers subpipelines to process each message individually. Further information can be found in the Stream Avro File Reader documentation.

  • Stream Parquet File Reader (General Availability): with this new connector, the user can read Avro files that trigger subpipelines to process each message individually. For more information, see the Stream Parquet File Reader documentation.

Triggers

Salesforce Trigger - Events (Restricted Beta): we’ve released a new trigger that allows the user to capture specific events that occur in Salesforce. This feature is in the Restricted Beta phase and is available for specific customers. For more information, see the Salesforce Trigger - Events documentation.

  • HTTP: the HTTP trigger has been updated and is available with improvements to all customers in the production environments of the BR Cluster.

Smart Connector User Experience (General Availability)

The Smart Connector User Experience is a new feature that allows you to add new connections directly in the flow in the canvas without having to drag and drop them from the connectors and capsules palette.

You only need to click on the "+" button in the floating menu above the triggers and connectors to get a unified search for connectors and capsules. The AI suggestions are also displayed in the same window. As soon as you click on the desired option, the connection is automatically added to the flow.

By enhancing, simplifying, and automating processes in canvas, this feature — and its future iterations — aims to continuously simplify the development process for creating integrations.

Learn more in the Smart Connector User Experience documentation.

Account expiration date (General Availability)

The Account expiration date is a feature enhancement that allows you to insert a reminder of the credentials expiration date when creating or editing certain types of accounts.

Accounts that have the expiration date field filled in will have a tag one month before the expiration date indicating when the credentials will expire, and another tag after the expiration date indicating that the credentials have expired. Accounts with these tags can be filtered on the Accounts page.

Further information can be found in the Accounts documentation.

Update in the License consumption page for the Subscription-based model (General Availability)

The License consumption page for the Subscription-based model has been updated to improve usability. On the updated page, you can clearly see the pipelines used in the Test and Prod environments and the RTUs consumed in each environment. The project information table has also been improved and now displays both environments in one place for easier management.

For more details, read the License consumption documentation.

Policies (General Availability)

The Policies feature, which allows you to define best practice processes for the realm and pipelines, and all currently available policies have been promoted from Beta to General Availability.

Now you can securely customize your policies to meet the needs of your business.

Learn more about the available Policies.

ZTNA Connections

  • Create new keys: you can generate new keys to reconfigure your local connection to the Edge Router if necessary. Find out more by reading our documentation.

  • Change your connection environment: you can change the name and environment of Edge Router connections. Read the documentation to learn more.

We’ve also fixed a few bugs and made the following improvements:

  • Build - Pipeline card overlaps the Help menu: we’ve fixed the bug that caused the pipeline card icons to overlap the Help menu when it was opened on the Build page.

  • Pipeline history - Trigger configuration is the same in different pipeline versions: we’ve fixed the bug that caused the trigger configuration to be repeated in different pipeline versions in the Pipeline history, even if the configuration should be different.

  • Pipeline history - Multiple minor versions of the pipeline were created at the same time: we’ve fixed the bug that caused multiple minor versions to be created when clicking to create a new version of the pipeline multiple times on the Pipeline history page.

  • Canvas - Blank page when adding a large payload on connectors: we’ve fixed the bug that caused the canvas page to go blank when there was a large payload in some connectors, such as JSON Generator.

  • Canvas - Blank page when pasting information into the Step Name of the JSON Generator: we’ve fixed the bug that caused the canvas page to go blank when pasting information into the Step Name field of the JSON Generator connector.

  • Canvas - OnProcess flow not accessible in Do While connector: we’ve fixed the bug that prevented users from seeing the content inside the OnProcess of the Do While connector.

  • Capsules - Search for capsules doesn't work with spaces in the name: we’ve fixed the bug that caused the search for capsules not to work if the search was performed with a space in the name.

  • Capsules - Blank page when saving capsules: we’ve fixed the bug that caused the page to become blank when clicking Save.

  • Connectors - REST V2: we’ve enabled the use of account information with Double Braces in query parameters when using the connector.

  • Connectors - JWT V2: we’ve enabled the ability to reference the Issuer(iss) and the custom claims information through an account when using the connector.

  • Connectors - CMS: we’ve enabled the use of DER encoding, which uses a definite length encoding, when using the connector.

Release notes 05-07-2024

Connectors

Triggers

  • DynamoDB Streams Trigger (Restricted Beta): we’ve released a new trigger that simplifies how the user reacts to updates in a DynamoDB table by listening for events such as new items being added, existing items being modified, or items being deleted. When any of these events happen, the trigger automatically starts the user’s Digibee pipeline, providing details about the change as input. This feature is in the Restricted Beta phase for specific customers. For more information, check the DynamoDB Streams Trigger documentation.

  • HTTP: The HTTP trigger has been updated and is available with improvements to all customers in the US cluster test and production environments and the BR cluster test environment.

ZTNA Connections

With this new feature, customers using ZTNA can view a detailed list of connections and routes on the Platform. Read the ZTNA Connections documentation to learn more.

Administration - New permission for ZTNA

We’ve added the new ZTNA:READ permission. With this permission, users can see the ZTNA connections created on the Platform. You can read more about this in the Roles documentation.

Double Braces autocomplete support for “item.” in JSON Transformer (General Availability)

Double Braces autocomplete now shows suggestions for completing expressions containing "item." in the JSON Transformer connector.

This simplifies the creation of Double Braces expressions as users no longer need to memorize the information and can simply autocomplete them.

Default collection and group in Capsules (General Availability)

The feature for creating Capsules in a default collection and group and for moving Capsules to other collections and groups has been promoted to General Availability. Improvements have been made so that users can now organize their capsules much more easily and smoothly.

Improvement - Warning before saving Capsules

Now when you edit the configuration form of a Capsule and click to save the form, you will receive a warning that the changes in the configuration form may affect the execution of the Capsule. We recommend reviewing the flow after each change.

This warning helps users to maintain Capsule compatibility and always review the flow after making changes to the configuration.

Run - Pipeline deployment status (General Availability)

Users can now view the new “Degraded” status in the Run page to get more information about a pipeline deployment in real time.Check the Run documentation to learn more .

Platform - Digibeectl improvements

The Digibeectl feature has new configuration options and subcommands that the user can access to have a better experience on our Command Line Interface (CLI). Read the Digibeectl documentation to learn more.

We’ve also fixed a few bugs and made the following improvements:

  • Canvas - Clicking on the Double Braces icon closes the connector form: we’ve fixed the bug that caused the connector configuration form to close when users clicked on the Double Braces icon.

  • Canvas - Step Name above the connector: we’ve fixed the bug where the text of the Step Name overlapped the connector in the flow.

  • Canvas - Tags are not added to fields in connectors and triggers: we’ve fixed the bug where it wasn’t possible to add tags in fields by pressing Enter or clicking outside the field.

  • Capsules - Accounts are not displayed in the connector within the Capsule: we’ve fixed the bug that caused the accounts not to be displayed in the connectors within the Capsule, even if they were created correctly in the Capsule configuration form.

  • Build - Projects are displayed for unassigned users: we’ve fixed the bug that previously allowed projects to be viewed by unassigned users after they were created. Now it’s no longer necessary to refresh the page to stop seeing them.

  • Connectors - JSON Path: we’ve fixed a bug that caused an error when using expressions with JSON Path.

  • Connectors - SFTP and SSH Remote Command: we've improved the connectors to allow custom client/server configurations for the server host key, public key accepted algorithms, and key exchange algorithms options.

  • Run - Wrong error message for globals: we’ve fixed the bug that caused the pipeline to display the wrong error message for globals.

  • Run - Issue with pipeline deployments with Engine Beta active: we’ve fixed the bug that caused problems with pipeline deployments while Engine Beta was active.

  • Run - Wrong message for failed deployments: we’ve fixed the bug that displayed the wrong message when a failed deployment happened.

Last updated