March
Last updated
Was this helpful?
Last updated
Was this helpful?
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, refer to the documentation.
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 documentation.
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 documentation.
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.
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 Connector Mocking documentation.
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.
Learn more in the documentation for Test Payloads and Connector Mocking.
We’ve improved our Customer Feedback Portal and now it's easier to send feedback or suggest new features for the Digibee Integration Platform.
Check out the step by step guide.
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.
The --realm and --account-id flags for config use are mutually exclusive, meaning only one of them can be used at a time.
Check out the complete Digibeectl documentation.
New Use Case in Action:
Error handling strategy in event-driven integrations: Understand how a centralized error-handling pipeline improves traceability, reduces redundancy, and simplifies error management across multiple pipelines in an event-driven architecture (EDA).
Two new troubleshooting articles:
Set the protocol for your ZTNA inverse flows: You can now define the type of protocol when you are creating your ZTNA inverse flows: HTTP (default), HTTPS, or HL7.
Environment tag: We color-coded environment tags to help you quickly identify your realm and prevent mistakes when executing an action.
New examples in the get metrics operation on Digibeectl: We’ve included new format examples in the get metrics operation in the Digibeectl documentation.
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.
"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. Learn more in the documentation.
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.
