# 2025 10 01 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-10-01     | Wednesday 1st October 2025 (a.m) |

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

* ​[Process flows](#process-flows)
* [Virtual environments](#virtual-environments)
* [API](#process-flows-1)
* [General](#process-flows-2)

## 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="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><del><strong>Map shape - source schema applied to the target if no target endpoint is selected</strong></del><br><del>Fixed an issue where selecting a <code>source</code> endpoint and no <code>target</code> endpoint resulted in the <code>source</code> schema being applied to the <code>target</code>.</del>   <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/sDacY10PFWZPapzdTUvr"><del>Map shape</del></a></td><td><del>CPT-3819</del></td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>De-dupe shape - tracking data using a meta variable</strong>  <br>Fixed an issue where using a meta variable as a custom value for tracking data did not work correctly if multiple payloads were received (the meta variable received for the first payload was not cleared for subsequent payloads).    <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/LQRcBGzoCvqv2cEsqUsZ">De-dupe shape</a></td><td>CPT-4677</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="d8457d8925c74fab90fa132d141b764b">Change</span></td><td><strong>View deployments - environment type separated from environment name</strong> <br>Having selected view deployments from process flow settings, the environment type (test or live) is now displayed below the name; previously, this information was appended to the name.  <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-4389</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Visibility of flow status in packages</strong>   <br>When viewing package contents, you can now expand a deployment entry to view the current status of associated flows in that environment.  <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/RqEJoVH7jg8eA64ESoRt">The anatomy of a package</a></td><td>CPT-4511</td></tr><tr><td><span data-option="d8457d8925c74fab90fa132d141b764b">Change</span></td><td><p><strong>Package removal</strong> <br>It's now possible to delete a package, provided that it does not contain any <code>enabled</code> flows. So:<br></p><ul><li>If a package is created but never deployed, the package can be deleted. </li><li>If a package has been deployed but all associated flows have been disabled in the deployed virtual environments, the package can be deleted. </li></ul><p><br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/SEdfMXJXlYSQwTP7pWsL">Deleting a package</a></p></td><td>CPT-4511</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Enabled flows count on packages page</strong>  <br>Fixed an issue where the <code>enabled</code> column of the packages list was not being updated with the enabled flows count.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/uooz3oh18slPGz1lAOAj">Accessing packages</a></td><td>CPT-4512</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>User ID for package deployments</strong> <br>Fixed an issue where the username associated with a deployment was not displayed for package deployments.  <br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/vA7dSxodDGw4rcUx8h54">Deploying a package</a></td><td>CPT-4706</td></tr></tbody></table>

## API <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><p><strong>Cross-reference lookups</strong>  <br>A new API route can be used to clear all values from a cross-reference lookup table, while leaving the empty table in place:</p><p><code>POST</code>  <code>https://core.wearepatchworks.com/cross-reference-lookups/:id/clear</code><br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/8trpSpsBHu5AxTBZNK3d">Cross-reference lookups</a></p></td><td>CPT-4764</td></tr></tbody></table>

## General <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="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Error handling for incorrect password reset</strong>  <br>Fixed an issue where attempting to reset an account password with an invalid password failed to prompt an error message for the user.<br><img src="/files/j1i0cLEEKzAu7FBcGQmn" alt="" data-size="line"> <a href="/pages/BBJUwjamohErtkjKoYeD">Password control</a></td><td>CPT-4764</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-10-01-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.
