January
Last updated
Was this helpful?
Last updated
Was this helpful?
We are very happy to announce the launch of the new Documentation Portal for the Digibee Integration Platform. This new version is designed to make the user experience even more intuitive, efficient, and convenient, making it easier to access information about the Platform.
What’s new:
New home page
New documentation sections
Easier and improved navigation
New design
How to access?
Access now through the same link: https://docs.digibee.com/documentation and share your feedback.
Now you can set up your ZTNA Inverse Flow connections on the Digibee Integration Platform independently. The Inverse Flow allows you to execute calls from your infrastructure to internal pipelines within the Platform using ZTNA.
Read the documentation to learn more.
To improve our documentation, we’ve created the article below:
Blank screen on Block Execution: We fixed a bug that caused a blank screen when opening a Block Execution with the same number of connectors as the root.
For Each loops not accessible in Inspect Mode: We fixed a bug that prevented users from navigating between loops within the For Each in Inspect Mode.
Azure Key account support: It’s now possible to authenticate to SQL Server databases with the Azure Key account type in the DB V2 and Stream DB V3 connectors. In addition, dynamic authentication with the Azure Key account type is supported via the 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 connector.
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 documentation.
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 documentation.
The 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 documentation.
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 on the Documentation Portal.
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 and List of permissions by service documentation. You can also access the step-by-step guide to learn how to set environment permissions for a group.
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.
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 section anytime through the Documentation Portal.
We’ve updated our troubleshooting documentation with new articles:
Access and performance
Connectors' behavior and configuration
We have updated our governance documentation with two new articles:
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.
