October
Last updated
Last updated
We have added two new functions so you can manage your ZTNA connections with greater autonomy:
Delete Connections (Edge Router): Remove a connection from your ZTNA connection database.
Delete Routes (Network Mapping): Remove a route from your ZTNA connection database.
See the documentation for detailed step-by-step guides.
It is now possible to create projects and pipelines (without a flowSpec) in the Digibee Integration Platform using Digibeectl.
To create a project, use the create project command along with the --name (project name) and --description (project description) flags.
To create a pipeline, use the create pipeline command along with the --name (pipeline name) and --project (project name) flags.
Read the documentation to learn more.
Now users can have two new roles:
global-environment-manager: Allows you to define access to view and manage Globals by environment.
account-environment-manager: Allows you to select the environment where users can perform actions related to Accounts.
Read the documentation to learn more.
We have added a section for practical use cases in the Documentation Portal. This section provides real-world examples that explain pipeline concepts and help you apply integration scenarios.
In the first use case, you will learn how to improve integration performance with API pagination, making it easier to manage large data sets.
You can explore the Use Cases in Action section anytime through the Documentation Portal:
Improvements to CPU and Memory usage charts on the Pipeline Metrics page: The CPU usage and Memory usage charts now display minimum, maximum, and average usage values for both CPU and memory, providing a more detailed view of your pipelines' performance.
Connectivity documentation update: Documents related to connectivity technologies on the Digibee Integration Platform have been updated. Access the Documentation Portal to learn more.
It is now possible to scaffold a pipeline from an OpenAPI specification file. To do so, simply click on Create, as usual, and select the Pipeline with OpenAPI option. After selecting the file and reviewing the routes, a pre-structured pipeline will be created with each route connected to a Block Execution, speeding up the process and simplifying management.
Learn more in the documentation.
The API Trigger is the new version of the REST Trigger, bringing significant improvements. The route table now presents the relationship between path and method more clearly, making it easier to understand the configurations. Additionally, after saving the configurations, the pipeline is automatically generated in the Canvas, already pre-structured, with each configured route connected to a Block Execution connector.
For more information, refer to the documentation.
Triggers are now divided into categories and organized alphabetically, making it easier to find the desired trigger in the list. The categories are:
Web Protocols: Triggers used to execute web protocols.
Scheduling: Triggers scheduled to perform actions at a specific time or interval.
Messaging and Events: Triggers activated by messages or events.
Others: Other types of triggers.
The AI Assistant is a new AI-powered functionality in the Digibee Integration Platform. It offers three ways to speed up your work:
Flow Generation: With this option, you can request the Assistant to generate a part or the entire flow of a pipeline, inserting it directly into the Canvas. Refer to the documentation to learn how to request flow generation and how to create effective prompts.
JOLT Generation: This feature streamlines the transformation of JSON inputs and outputs into a JOLT specification, simplifying the process and reducing the learning curve needed to do it manually. Learn more in the documentation.
Docs Q&A: The Docs Q&A feature allows you to ask questions about the Platform while building your pipeline. The Assistant uses Digibee’s official documentation, ensuring reliable answers. Refer to the documentation.
The Overview tab in Monitor now displays Insights tags in the pipeline table, making it easier to identify and investigate execution issues. Clicking on the tags will take you to the Pipeline metrics or Completed executions pages, with information for the selected pipeline already filtered. For more details, see the documentation.
Users with the API Key Manager, Deployment Manager, and Pipeline Manager roles can configure specific permissions for each environment (test or production), ensuring that authorized groups can only perform tasks in the selected environment. Read the updated List of permissions by service documentation for more information, and check out the step-by-step guide to learn how to include this parameter.
New shortcuts in the Monitor Overview: easily access the Completed executions, Logs, Metrics, and Alerts pages, with data already filtered for the specific pipeline, using the three-dot icon in the table on the Overview tab. For more details, see the documentation.
New shortcut to the number of errors in the Monitor Overview: when clicking on the number of errors for a pipeline in the Errors column, a new tab will open showing the Completed executions page, with the detailed history of failed executions for the selected pipeline.
Usability improvements in Digibeectl: use the --output or -o flags together with GET commands to display resources in JSON format in Digibeectl.
Build – Archived pipelines not appearing in projects: We fixed the bug that prevented archived pipelines from being displayed in projects, even when the "Archived" filter was applied in the search.
Canvas – OnException subflow in For Each: We fixed the bug that prevented the OnException subflow from being executed in the For Each connector.
Canvas – Retry not working in SOAP V3 connector: We fixed the bug that caused the "retry" function not to work in the SOAP V3 connector.
