# August 27

## **Platform improvements**

### **Linter integrated to the Execution Panel**

The Linter is now integrated directly into the Execution Panel:

* The **Issues** tab in the sidebar has been removed.
* All alerts appear in the **Problems** tab within the Execution Panel, making it easier to identify and fix configuration issues during execution.

This streamlines alert management and centralizes execution feedback.

<a href="/spaces/jvO5S91EQURCEhbZOuuZ/pages/WliH0PsUcFSdDQ88JGEl" class="button primary">Read the documentation</a>

<figure><img src="/files/bEMVcyqrKkEgsvkIjGcx" alt=""><figcaption></figcaption></figure>

### **AI Assistant for Connectors now available for REST V2**

The **REST V2** connector now features the AI Assistant for the **Body** field in **POST** operations, simplifying configuration and helping you set up integrations more efficiently.

<a href="/spaces/jvO5S91EQURCEhbZOuuZ/pages/k3DyhxVltlo53WRMpB58" class="button primary">Learn more</a>

<figure><img src="/files/z7TJciKbjFCN7xzYScS3" alt=""><figcaption></figcaption></figure>

### **Build page: Pipeline cards update (General Availability)**

This release improves the Build page with the following updates:

* Pipelines saved after this release now show a **Preview** button on hover.
* **Environment tooltips** for deployed pipelines now display version details.
* Pipelines can be **opened in a new tab** via right-click.

These changes make pipeline details clearer at a glance and streamline navigation.

<a href="/spaces/jvO5S91EQURCEhbZOuuZ/pages/QsQ0ppGmiRt2QQGpJZD8" class="button primary">See details</a>

<figure><img src="/files/wy0kJdth4jgIiZgfhnfq" alt=""><figcaption></figcaption></figure>

### **Automatic data refresh on Run and Monitor pages**

Now you can update your data automatically on the **Run** and **Monitor** pages, according to the selected interval:

* 30 seconds
* 1 minute
* 5 minutes

<a href="/spaces/jvO5S91EQURCEhbZOuuZ/pages/9suWx4sdYj1OhCWwhB69" class="button primary">View in Run</a> <a href="/spaces/jvO5S91EQURCEhbZOuuZ/pages/-MkqZo_5jRUieqL3WvsR" class="button primary">View in Monitor</a>

## **Connectors**

### **Script (JavaScript) connector – Experimental runtime**

We've added a new **Use Experimental Runtime (Improved Performance)** parameter, allowing you to enable a faster, more secure, and stable runtime for your scripts. This **beta feature** improves execution performance and reliability.

<a href="/spaces/EKM2LD3uNAckQgy1OUyZ/pages/P8xiBmDAwcK8jS6iMq0D" class="button primary">Read the documentation</a>

### **SAP connector evolution**

You can now quickly generate a **pre-configured XML template for RFC calls** in the **SAP (IDoc and RFC)** connector, simplifying setup and reducing configuration effort.

<a href="/spaces/EKM2LD3uNAckQgy1OUyZ/pages/03RrG53ufvHPlZ9rbUxc" class="button primary">Learn more</a>

### **Salesforce connector updates**

* **REST protocol – Get Blob Field:** We've added two new parameters, **Save as Local File** and **File Name**, allowing files to be returned in base64 or saved to the pipeline’s local directory.
* **REST protocol – Composite Update SObject Collections**: We've improved the output to provide more accurate details when updating multiple records.
* **REST protocol – Create SObject:** We've updated the **Employees** field to support Double Braces, enabling dynamic value mapping during object creation.

<a href="/spaces/EKM2LD3uNAckQgy1OUyZ/pages/Jh3aDtsub8DGJJx8c1tF" class="button primary">See details</a>

### **HL7 Trigger – MSH-3 filtering update**

The **HL7 Trigger** now uses the **Filter from Header (MSH-3)** field to read multiple message types, replacing the previous key-value approach. This allows a single pipeline to handle different message types, consolidating flows and streamlining deployment and message processing.

<a href="/spaces/EKM2LD3uNAckQgy1OUyZ/pages/uwcowLX3puHDzdRbuhQm" class="button primary">Read the documentation</a>

## **Documentation**

We’ve updated the following documentation:

* [Licensing: Main concepts](/documentation/licensing/licensing-models/licensing-main-concepts.md)
* [Pipeline-Based Model](/documentation/licensing/licensing-models/pipeline-based-model.md)
* [Subscription-Based Model](/documentation/licensing/licensing-models/subscription-based-model.md)

## **Improvements and bug fixes**

### **Improvements**

* **Redesigned table visualization on Run page:** We’ve improved the design and navigation on the table visualization type on the [Run page](/documentation/developer-guide/development-cycle/overview.md).
* **Enable Support access directly on the Canvas menu:** We’ve improved the [management of the Digibee Support Team's access to your realm](/documentation/troubleshooting/help-and-faq/support.md#what-access-permissions-does-the-support-team-have), now available directly on the right menu on the Canvas page.
* **Filters on the Build page:** We’ve enhanced [the filters](/documentation/developer-guide/development-cycle/build-overview.md#search-and-filters), which now reset automatically when switching projects or realms.

### **Bugs**

* **Invalid cron expression:** We fixed a bug where entering an invalid cron expression with an hour value of 24 (valid range: 0–23) caused the Run page to display a blank screen and prevented pipeline deployment.
* **Salesforce: Bulk 2.0 protocol – Create Batch:** We fixed a bug that prevented correct execution of the operation and improved the output for batch creation requests.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digibee.com/documentation/release-notes/august-2025/august-27.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.