> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/2024-06-05-release-notes-core.md).

# 2024 06 05 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.19.0          | 5th June 2024 @ 8am |

**Patchworks dashboard (frontend)**

| Release version | Release date        |
| --------------- | ------------------- |
| 1.14.2          | 5th June 2024 @ 8am |

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

* [Process flows](#process-flows)

## 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><p><strong>Has warnings indicator in run logs</strong><br>Run logs now include a <code>Has warnings</code> column. If a process flow run succeeds with warnings (for example, if data of the wrong type is passed into a transform function in the map shape), a warning icon is displayed in this column.</p><p>If required, the <code>Has warnings</code> column can be filtered so only runs with warnings are displayed.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/RVdm7LuBhWXjhM0Cyuq9">Run logs &#x26; queue</a></p></td><td>CPT-2701</td></tr><tr><td><span data-option="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><p><strong>Flow control shape - single items</strong><br>When configuring a flow control shape, a new <code>Do not wrap single records in an array</code> option is available. Use this if you are creating payloads with a <code>batch size</code> of <code>1</code>, and you want the output to be this:</p><pre class="language-json"><code class="lang-json">{
    "field": "value",
    "field": "value",
    "field": "value"
}
</code></pre><p>...rather than this:</p><pre class="language-json"><code class="lang-json">[{
    "field": "value",
    "field": "value",
    "field": "value"
}]
</code></pre><p><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/uNI6ZNhC4NnwLaAhP1yN">Flow control shape</a></p></td><td>CPT-1153</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><p><strong>Run process flow shape - variables</strong><br>When using the <code>Run process flow shape</code> to call one process from another, it's now possible to override flow variables with meta or flow variables defined in the <code>Run process flow</code> shape. When configuring this shape:</p><ul><li><a href="/pages/HC31VdrWhJMUz0LwmCJx">payload variable</a> and <a href="/pages/sCJOjrLZifsLUf5k3omc">flow variable</a> syntax can be used.</li><li>Any payload provided will override the passed payload from the previous step.</li></ul><p><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/1YdpDOKiycGviDZd7krP">Run process flow shape</a></p></td><td>CPT-2610</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Improved error reporting for script issues</strong><br>Logging has been extended for cases where a process flow run fails due to a custom script issue, and also if a script fails to deploy.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/5cLk6r6bIFBLhs5MFTWE">Custom scripts</a></td><td>CPT-2903</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><p><strong>Un-deployed scripts not available in map script transforms</strong><br>Fixed issue where only deployed scripts/versions were available for selection when configuring a script transform function for a field mapping (via the map shape).</p><p>Now, all scripts/versions are available for selection. If an un-deployed script/version is selected it is deployed, ready for use.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/VEY4jTycIDsGFwIsudto">Script transform function</a></p></td><td>CPT-2724</td></tr></tbody></table>