> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/release-information/flow/6.15/server/6.15.14.md).

# 6.15.14

2025-02-18

#### Pre**requisite**

{% hint style="danger" %}
Before updating the Flow Server to service pack 6.15.14, ensure that the Server Manager Installer is updated to version 6.15.6 or newer.
{% endhint %}

#### **Issues Resolved**

* OPC UA connector - Improved OPC UA connector performance by introducing session caching. Sessions are created per connector configuration and cached until the session timeout. The session timeout can be set in the Connector -> Default session settings. Please note that the values are in milliseconds  and the minimum session timeout that can be set is 60 seconds (60000 milliseconds). Optionally you can also define a session name.

  <figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2Fb381idufFlwEqkzipdLb%2Fimage.png?alt=media&amp;token=81f6c7fb-5ddc-4176-9764-d1bdb0f14a60" alt=""><figcaption><p>Session timeout setting</p></figcaption></figure>

  Upon the session timeout a new session will be created and the old session will be removed eventually. Because of that its possible that two sessions are active for a given connector configuration during the transition period.

* Infor m3 REST connector - Introduced the new connector configuration ***Allow leading zeros in input***. When enabled this setting will preserve the leading zeros for a number field in input/output. By default its set to false and the field value is returned as a number ignoring the leading zeros. Also fixed a minor issue with error message handling due to the changes Infor has made to error message format/structure in API v1.

  <figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FLuE2vZAG4PKSRDEzUnli%2Fimage.png?alt=media&amp;token=00fdb912-006a-4058-ac08-8d1969be941a" alt="" width="530"><figcaption><p>Infor m3 REST</p></figcaption></figure>

* REST connector - A new configuration option ***JSON treat empty string input as null*** is introduced under Model -> Attribute -> Advanced settings section. When enabled empty string values in the will be considered as null for that attribute. You can see the result in the logging file.

  <figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FIvv99tYIRLuRbryB2zb0%2Fimage.png?alt=media&amp;token=8507c420-e00d-460a-977a-e69a18f22ad0" alt=""><figcaption><p>REST Connector project</p></figcaption></figure>

#### **Manual Upgrades**

Please refer to the section [Manul Upgrades for 6.15.12](/release-information/flow/6.15/server/6.15.12.md#manual-upgrades)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://help.novacuraflow.com/release-information/flow/6.15/server/6.15.14.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.