March
Last updated
Was this helpful?
Last updated
Was this helpful?
In addition to executing the entire flow or selected connectors, you can now start a pipeline execution from a specific step. This allows you to start with any step while ensuring that all subsequent steps of the flow are executed. This improvement further streamlines the testing process.
You can now request new documentation or updates to existing documentation directly on the Digibee Integration Platform.
You can also request documentation by clicking the Request documentation button at the top right corner of the Documentation Portal.
We have updated the following document:
Different execution information in Design and Inspect Mode: We fixed the bug that caused the Inspect Mode to display incorrect execution data in the Input and Output fields.
OpenAPI OAS 3.0.1 not recognized in API Trigger: We fixed the bug where the API Trigger failed to recognize OAS 3.0.1 OpenAPI specification in the trigger configuration.
Deployed pipeline not visible on Build when latest version is archived: We fixed a bug where pipelines were not displayed on the Build page when their latest version was archived, even if older versions were deployed. Now:
Deployed pipelines will remain visible if at least one previous version has been deployed.
Attempting to archive a deployed version will trigger a warning.
If no versions are deployed, the pipeline will be completely archived and removed from the list.
This feature enables you to easily create a mock response using the connector’s output message. Simply select the message you want to use as the basis for your mock response, click Create mock response, and enter the required details.
Test Payloads and Connector Mocking are now available for Capsules. These features allow you to save test payloads for future use and create mock responses for connectors.
This improvement simplifies Capsule building, making the Platform more intuitive while also speeding up testing by reducing manual steps.
We have included new commands in Digibeectl:
config set --account-id: If an account is not provided, the flag value will be displayed as account-X, where X is a unique sequential integer starting from 0.
config get --account-id: Get realms settings when searching by --account-id.
config delete --account-id: Use an --account-id to delete a Digibeectl configuration.
config update-context: Receive an update of the realms available for accounts with active status in Digibeectl.
config view: List all available/configured accounts.
config use --realm: Change the current realm for any of the availableRealms.
config use --account-id: Switch between configured accounts.
Two new troubleshooting articles:
Environment tag: We color-coded environment tags to help you quickly identify your realm and prevent mistakes when executing an action.
Organization permission for Digibeectl: When creating a new token for Digibeectl, users with the ORG:MANAGER permission can activate an option to manage multiple realms if necessary.
Environment appears in the VPN Monitoring page: We fixed the bug that displayed the environment tag on the VPN Monitoring page in Monitor.
API Trigger not saving on first attempt: We fixed a bug that prevented users from saving the API Trigger configuration on the first try.
AI feature temporarily visible on Canvas: An AI feature was unintentionally displayed on Canvas before it was officially released. This has been corrected and more details will be announced in the Release Notes once the feature is officially launched.
For more details, refer to the documentation.
You can now create alerts for your VPN metrics. With this, you can quickly identify and resolve issues in your connections. Read the .
Check out the .
: This document, previously called "Pipeline building checklist", has been updated. It offers simple guidelines to help make your pipelines secure, efficient, and well structured.
Improvement on the page: You can now copy the log message or format the JSON directly from the Completed executions sidesheet, without returning to the Pipeline logs page.
Improved selection of specific periods when searching in : We've included an improvement to make it easier to search for Audits in specific time periods.
Updates to button names in Inspect Mode: In , the "List View" and "Tree View" buttons have been renamed to "Messages" and "Flow Tree," respectively, to improve understanding and usability.
HL7 Message Transformer is a new connector that converts HL7 messages to JSON and vice versa, streamlining data transformation in healthcare integrations. It reduces complexity, minimizes errors, and decreases development effort. This connector is currently in Beta. For more details, .
The FHIR connector enables seamless interaction with FHIR servers, allowing you to retrieve, create, update, and delete FHIR resources with ease. It streamlines healthcare data exchange by ensuring compatibility with FHIR standards. This connector is currently in Beta. For more details check out the .
The Orderful connector facilitates interaction with the Orderful API, enabling you to send, receive, and manage EDI (Electronic Data Interchange) documents efficiently. It helps automate B2B transactions, improving efficiency and reliability. Learn more about this connector in the .
By simplifying the mock response creation process, this feature minimizes errors and improves the efficiency of testing and debugging. Further information can be found in the .
Learn more in the documentation for and .
We’ve improved our and now it's easier to send feedback or suggest new features for the Digibee Integration Platform.
Check out the .
Check out the complete .
New :
: Understand how a centralized error-handling pipeline improves traceability, reduces redundancy, and simplifies error management across multiple pipelines in an event-driven architecture (EDA).
Set the protocol for your ZTNA inverse flows: You can now define the type of protocol when you are : HTTP (default), HTTPS, or HL7.
New examples in the get metrics operation on Digibeectl: We’ve included new format examples in the get metrics operation in the .
"loopBreak": true in Do While no longer interrupts flow execution: We fixed a bug where encountering the “loopBreak”: true property within a Do While subflow prevented the main flow from continuing. Now, when this occurs, the output message remains empty, and the main flow proceeds as expected. .
