# 2025 09 03 release notes (core)

## Release summary <a href="#release-summary" id="release-summary"></a>

This page summarises items scheduled for the following release to the Patchworks Core Production environment.&#x20;

| Release version | Release date                  |
| --------------- | ----------------------------- |
| v2025-09-03     | Wednesday 3rd September (a.m) |

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

* ​[Process flows](#process-flows)
* [Virtual environments](#virtual-environments)
* [Blueprints](#blueprints)

## Process flows <a href="#process-flows" id="process-flows"></a>

<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>New filter options for JSON arrays</strong><br>The filter shape includes new <code>list</code> and <code>list length</code> filter types. Use the <code>list</code> option to filter JSON payloads based on given values in an array field. Use the <code>list length</code> option to filter payloads based on the number of items in an array. <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/Sy6mhTYAW0f9nCQgnU73">Using list &#x26; list length filter options</a></td><td>CPT-4126</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Script shape settings</strong><br>When choosing which script to run via script shape settings, you can now search by script name. <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/0C93Lh1WJuGoTR9rN6NN">Script shape</a></td><td>CPT-4396</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Time zone for dynamic date flow variables</strong><br>Fixed an issue where the <code>time zone</code> set for a <code>dynamic date</code>  flow variable was not applied as expected for anything other than UTC.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/sCJOjrLZifsLUf5k3omc">Flow variables</a></td><td>CPT-4585</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Set variable from payload field with spaces</strong><br>Fixed an issue where using the <code>set variables</code> shape to define a variable from an incoming payload field with spaces (for example: <code>[[payload.customer id]</code>]) did not resolve correctly. <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/T9gT7vCqVNpdJ4mwYRsa">Set variables shape</a></td><td>CPT-4197</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Flow variables in prefix transformations</strong><br>Fixed an issue where flow variables were not resolved when defined as part of a string prefix transform function.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/PQ54P1sP9fWSs927IYm5">The prefix transform function</a></td><td>CPT-3516</td></tr></tbody></table>

## Virtual environments

<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>Generate webhook &#x26; callback URLs for virtual environments</strong><br>A new virtual environment selector is available in trigger shape settings. </p><p></p><p>If a virtual environment is selected here, any subsequent webhooks or callbacks display a <code>copy VE URL</code> option. You can use this to copy a 'ready to go' version of the URL for the given virtual environment, instead of editing URLs manually.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/B7zUw05sBtV2aQnpFzbT">Webhook triggers</a> &#x26; <a href="/pages/pjs69xcYUPTKrvyb5yvA">callback triggers</a></p></td><td>CPT-4519</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Deploying process flows</strong><br>When deploying a process flow via process flow settings, environment selection is now clearer. You can now choose <code>no environment</code>, or an applicable virtual environment.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/QJn3I6Ens3cFWBGOJZMh">Deploying a single process flow to a virtual environment</a></td><td>CPT-4546</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><p><strong>Deployed flows count</strong><br>Fixed an issue where the deployed flows count (found at the top of the <a href="/pages/9OIfoWLTibQsBjWhcMoj">manage your flows</a> page) was not updated correctly when process flows were deployed to multiple environments. Now, every deployment (irrespective of environment) increments this count.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/9OIfoWLTibQsBjWhcMoj">Accessing your process flows</a></p><h3 id="introduction"><br></h3></td><td>CPT-4557</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Virtual environment flow deployments information</strong><br>Fixed an issue where the <code>deployed by</code> column was not populated when viewing details for a virtual environment.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/SiWXnE8YVuWBDKUA7NFW">The anatomy of a virtual environment</a></td><td>CPT-4514</td></tr></tbody></table>

## Blueprints

<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><strong>Try/catch sequencing after blueprint install</strong><br>Fixed an issue where the sequencing of try/catch branches in process flows would be reversed when the flow was installed via a blueprint.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/jfpe0I4JN0aeeuKW4KyA">Blueprints</a></td><td>CPT-4567</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/2025-09-03-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.
