# January 7 ## Release notes 01/07/2025 ### Connectors * **Azure Key account support:** It’s now possible to authenticate to SQL Server databases with the [Azure Key](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/settings/accounts#accounts-type) account type in the [DB V2](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/structured-data/db-v2) and [Stream DB V3](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/structured-data/stream-db-v3) connectors. In addition, dynamic authentication with the Azure Key account type is supported via the [Store Account](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/tools/store-account) connector. * **New Wrap Key and Unwrap Key operations in the RSA Cryptography connector:** You can now encrypt and decrypt AES session keys with an added layer of integrity validation using the newly introduced Wrap Key and Unwrap Key operations in the [RSA Cryptography](https://app.gitbook.com/s/EKM2LD3uNAckQgy1OUyZ/connectors/security/rsa-cryptography) connector. ### Execute Selected Steps (General Availability)
**Execute Selected Steps** is a new feature that allows you to test not only the entire flow, but also specific segments of a pipeline or capsule flow. By selecting which steps to run, you can focus on validating smaller parts of your integrations without having to change the flow logic or disconnect other connectors. This feature streamlines the testing process, making it more efficient and practical for troubleshooting or verifying isolated parts of the flow. For more information, see the [Execution panel](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/build-overview/canvas/execution-panel) documentation. ### Improved execution inspection: Debug Mode renaming and feature upgrades (General Availability)
The Inspect Mode is an improved version of the previous Debug Mode, which is being redesigned to provide you with a more intuitive experience when running your flows. Key changes in this release include: * The name has been changed from **Debug** to **Inspect**. * The Inspect Mode is now only available when the execution generates messages. * Visual cues are displayed on the Canvas to alert you that an execution is ready for inspection. Learn more in the [Design and Inspect Mode](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/build-overview/canvas/design-and-inspect-mode) documentation. ### AI Assistant – Flow Generation, JOLT Generation, and Docs Q\&A (General Availability)
The [AI Assistant](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/build-overview/canvas/ai-assistant) and all its AI-powered features – Flow Generation, JOLT Generation, and Docs Q\&A – have been promoted to **General Availability**. These features are designed to speed up the development process, clarify questions without leaving the Platform, and shorten the learning curve. In addition, it’s now possible to rate the answer with the “Like" and “Dislike" buttons, which helps to evaluate and train the AI model to get more accurate answers. Learn more in the [AI Assistant](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/build-overview/canvas/ai-assistant) documentation. ### Improvements on the Alerts configuration page (General Availability) We improved the navigation and user experience on the Alerts configuration page in Monitor. Here are the new features: * **Multi-pipeline alerts** help you select all the pipelines in one realm at once or select a list of pipelines to create specific multi-pipeline alerts. * **More detailed information** about your pipelines at the Alerts configuration table. * **New alert metrics**. Read more in our updated [Alerts documentation page](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/dashboards/alerts) on the Documentation Portal. ### Access by environment on the Monitor page (General Availability) The permissions below have been enhanced with an environment variable, providing control over user access to test and production environments across all tabs in the Monitor section: * `MESSAGE:READ` * `LOG:READ` * `ALERT:READ` * `METRIC:READ` * `STATS:READ` Administrators can now specify if users with these permissions can only view metrics in the test environment, production environment, or both. Check out the [Roles](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/administration/new-access-control/access-control-roles) and [List of permissions by service](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/administration/new-access-control/access-control-roles) documentation. You can also access the step-by-step guide to learn [how to set environment permissions for a group](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/administration/new-access-control/access-control-groups). ### New commands on Digibeectl (General Availability) We’ve included new commands on Digibeectl: * **get-license:** Shows license information by pipeline and projects. It helps you optimize costs and usage of the licenses, and also provide reports for different areas of your company. * **set-deployment--restore:** Creates a new deployment using the ID of a previously deployed version. It must be used together with the --history-id flag. To see the details about the commands on Digibeectl, check out the [documentation](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/development-cycle/digibeectl/digibeectl-operations). ### Introducing 5 new Use Cases to enhance your integrations * **Securing sensitive information in pipelines:** Learn security best practices such as encryption, hashing, sensitive fields obfuscation, and credential management through Accounts configuration. * **OAuth2 for secure API access:** Learn how to implement token-based authentication and role-based access in Digibee pipelines, enhancing security and operational scalability. * **Secure your APIs with JWT:** Learn how to securely implement JWT for authentication in Digibee. Discover best practices, avoid common pitfalls, and use JWT connectors for seamless integration. * **Integration best practices for developers on the Digibee Integration Platform**: Learn to optimize debugging, ensure data consistency, and validate external service interactions to enhance your integration flows. * **How to use Event-driven architecture on the Digibee Integration Platform:** Learn how to implement Event-Driven Architecture on the Digibee by transferring records between publisher and subscriber pipelines. You can explore this and more in the [Use Cases in Action](https://app.gitbook.com/s/aD6wuPRxnEQEsYpePq36/use-cases) section anytime through the Documentation Portal. ### Documentation #### Troubleshooting articles We’ve updated our troubleshooting documentation with new articles: * **Governance and connections** * [How to manage IPs on the Digibee Integration Platform](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/connectivity-guides/connection-refused-error) * [How to connect Digibee to SAP](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/connectivity-guides/digibee-sap) * [How to connect Digibee to Oracle RAC](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/connectivity-guides/digibee-oracle-rac) * **Integration guidance** * [How to perform IP address mapping with Progress database](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/connectivity-guides/ip-progressdb) * [How to resolve the "Pipeline execution was aborted" error](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/deployment-issues/pipeline-execution-was-aborted-error) * [How to resolve the "Failed to initialize pool: ONS configuration failed" error](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/integration-issues/failed-to-initialize-pool) * [Avoiding loops and maximizing pipeline efficiency](https://app.gitbook.com/s/aD6wuPRxnEQEsYpePq36/best-practices/avoiding-loops-and-maximizing-pipeline-efficiency) * **Access and performance** * [How to analyze the "Network error: Failed to fetch" in the Execution panel](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/integration-issues/failed-to-fetch-error) * **Connectors' behavior and configuration** * [Understanding @@DGB\_TRUNCATED@@ on the Digibee Integration Platform](https://app.gitbook.com/s/boT4qPJIk6PZotrxlJWL/integration-issues/dgb-truncated) #### Governance We have updated our governance documentation with two new articles: * [Naming: Global, Accounts and API Keys](https://app.gitbook.com/s/aD6wuPRxnEQEsYpePq36/best-practices/naming-global-accounts-and-api-keys) * [Roles and responsibilities: Governance and key stakeholder identification](https://app.gitbook.com/s/jvO5S91EQURCEhbZOuuZ/platform-administration/administration/new-access-control/access-control-roles/key-stakeholder-identification) ### Bugs * **Custom error not saved in Throw Error:** We fixed a bug where the custom error property was not saved in the Throw Error connector. * **Capsule configuration form freezing:** We fixed a bug that caused the capsule configuration form to freeze, preventing user interactions. * **Parameters not applied during capsule testing:** We fixed a bug where the Parameters column in the Execution panel was not applied when testing capsules.