# 2024 06 18 release notes (core)

## Release summary

This page summarises items scheduled for the following release to the Patchworks Production environment:

**Patchworks core (backend)**

| Release version | Release date         |
| --------------- | -------------------- |
| 1.20.0          | 18th June 2024 @ 8am |

**Patchworks dashboard (frontend)**

| Release version | Release date         |
| --------------- | -------------------- |
| 1.15.0          | 18th June 2024 @ 8am |

New features, updates, and enhancements of note are summarised by product area, below:

* [Process flows](#process-flows)
* [Connectors & instances](#connectors-and-instances)
* [Custom scripts](#custom-scripts)
* [Connector builder](#connector-builder)

## Process flows

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><strong>Cache lookup transform - fail on miss option</strong><br>The cache lookup transform function now includes a <code>fail on miss</code> option. When this option is ON, the map shape will fail if the <code>cache lookup</code> transform function is configured to use a cache key that can't be found in the given cache. If this option is OFF, a missing cache key will not cause the map shape to fail.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/egBLpC2Ogo7GaK36YWHW">Referencing a cache in mapping transformation</a>s</td><td>CPT-2931</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Script shape - script deployment &#x26; retries</strong><br>If a script shape is configured to use a script that needs to be re-deployed, deployment is attempted automatically. <br><br>In the event that the first attempt fails, it is retried up to three times. After three failed attempts, the step fails and further checks should be made.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/0C93Lh1WJuGoTR9rN6NN">Script shape</a></td><td>CPT-2961</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><p><strong>Improved logs for regex transform failures</strong><br>The following transform functions use a regex expression to split strings according to a user provided delimiter: <code>Last word</code>, <code>First word</code>, <code>split</code>.</p><p></p><p>Logs have been enhanced for cases where one of these transforms fails because the specified delimiter is not escaped. Now, an <code>invalid regex statement</code> error message is provided, with details about which transform has failed.  <br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/HDn9NDKmYejdH2cKYLTv">Transform functions</a></p></td><td>CPT-2954</td></tr></tbody></table>

## Connectors & instances

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>My connectors paginatio</strong>n<br>The <a href="https://app.wearepatchworks.com/login">my connectors</a> page now includes pagination. If more than 50 connectors are installed, page numbers are now available so you can step through pages.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/o2uhNbBA04vHcA45QhE6">Accessing your connectors</a></td><td>CPT-2951</td></tr></tbody></table>

## Custom scripts

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><strong>Custom scripts - write flow run logs</strong><br>To provide more visibility on what a script is doing, you can now add a message to scripts for output to logs (both live and retrospective). <br><br>This is achieved using a <code>logs</code> array key in a script, with required output added as strings (maximum of 500 characters).  <br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/lE5P0UVkf7DL5JHDRgKR">Custom script messages for logs</a></td><td>CPT-2914</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><p><strong>MySQL database access from PHP scripts</strong></p><p>The <code>PDO_MYSQL</code> extension has been added for PHP, providing access from PHP to MySQL databases.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/5cLk6r6bIFBLhs5MFTWE">Custom scripts</a></p></td><td>CPT-2927</td></tr></tbody></table>

## Connector builder

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><p><strong>Field tags duplicated when multiple schema items are present</strong></p><p>Fixed issue where the field tags list for an endpoint would include duplicate entries if the schema includes duplicate data (i.e. where an actual payload rather than a schema was provided). <br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/1HQOidwFKDzQGFGi3zxg">Field tagging</a></p></td><td>CPT-2765</td></tr></tbody></table>


---

# 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://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/2024-06-18-release-notes-core.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.
