# 2025 08 20 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-08-20     | Wednesday 20th August 2025  (a.m) |

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

* ​[Process flows](#process-flows)
* [Connectors & instances](#connectors-and-instances)
* [Virtual environments](#virtual-environments)
* [Connector builder](#connector-builder)
* [Administration](#administration)
* [Patchworks API](#patchworks-api)

## 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><strong>Connector shape retries</strong><br>If a process flow runs and a connector shape fails, the default behaviour is to retry the connection three times. We've fixed an issue where the connector shape did not retry if the next shape in the flow was a <a href="../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/track-data-shape">track data</a> shape.   <br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape">Connector shape</a></td><td>CPT-4193</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>Cross-reference lookup name changes</strong><br>Fixed an issue where changing the name of a cross-reference lookup table would cause <a href="../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape">map</a> shapes to fail if they included references to that cross-reference lookup table in <a href="../../process-flows/cross-reference-lookups/using-a-cross-reference-lookup-in-field-transformations">field transformations</a>. Now, any name change cascades down to existing cross-reference lookup transforms. <br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../process-flows/cross-reference-lookups">Cross-reference lookups</a></td><td>CPT-3442</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><del><strong>Set variable from payload field with spaces</strong></del><br><del>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.</del> <br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/set-variables-shape"><del>Set variables shape</del></a></td><td><del>CPT-4197</del></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="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><strong>Authentication certificates</strong><br>Some systems require a certificate to communicate with their target server. This functionality is now built into the connector instance creation wizard.<br><br>When adding an instance for any connector (irrespective of the selected authentication method), you can access <code>certificates</code> settings to upload a certificate and (optionally) enter an associated passphrase.<br><br>Currently, <code>p12</code> certificates are supported.<br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../connectors-and-instances/working-with-instances/adding-an-instance">Adding a new instance</a></td><td>CPT-4520</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="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Deleting virtual environments</strong><br>Previously, deleting a virtual environment meant that the virtual environment name could not be used again. Following this update, names used for now-deleted virtual environments can be reused.<br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../virtual-environments/managing-virtual-environments-versions-and-flows/managing-virtual-environments/deleting-a-virtual-environment">Deleting a virtual environment</a></td><td>CPT-4547</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Virtual environment summaries</strong><br>When viewing the <code>virtual environments overview</code> page, each existing environment is displayed as a tile with summary information, including a list of deployed process flows. This list is now limited to three displayed items. If appropriate, the list is followed by an indicator that additional flows are present. Hover your cursor over this indicator to view the names of these flows.<br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../virtual-environments/accessing-virtual-environments/understanding-the-virtual-environments-overview-page">Understanding the virtual environments page</a></td><td>CPT-4496</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><strong>Endpoint schemas</strong><br>Fixed an issue where deleting the schema for a connector endpoint did not also clear the associated data path.<br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../developer-hub/connector-builder/building-your-own-connector/4-endpoints/endpoint-options/schema-taxonomy">Endpoints - schema &#x26; taxonomy</a> </td><td>CPT-4075</td></tr></tbody></table>

## Administration

<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>Company creation optimisation</strong><br>Behind the scenes, the company creation process has been optimised with the introduction of database pools. The average time taken to create a new company is now three times faster than previously.<br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="../../company-management">Company management</a></td><td>CPT-4497</td></tr></tbody></table>

## Patchworks API&#x20;

<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>Blueprint flow tagging</strong><br>When a process flow is installed via a blueprint, it is now tagged with a <code>marketplace_app_id</code> . Accordingly, you can use the Patchworks API to filter flows by a given <code>marketplace_app_id</code> value.  <br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FRrjk9xAjfqkNrsD16eTE%2Ficon%20page.png?alt=media&#x26;token=dab50d7c-876d-460c-a6ba-676fac0531f9" alt="" data-size="line"> <a href="https://postman.wearepatchworks.com/#514e8788-2fa2-44a6-be96-0bc7fbb8f9f4">Flows API</a></td><td>CPT-4350</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><p><strong>API Key creation during company creation</strong><br>When creating companies via the Patchworks API, a new <code>with_api_key</code> boolean parameter can be used to generate an associated API key automatically. This works as follows:<br></p><ul><li>If a  <code>with_api_key</code> value is not provided or set to <code>false</code>,  an API key is not created.</li><li>If the  <code>with_api_key</code> value is set to <code>true</code>, an API key is generated and returned in the response.  </li></ul></td><td>CPT-4351</td></tr></tbody></table>