# 2025 07 16 release notes (core) ## Release summary This page summarises items scheduled for the following release to the Patchworks Core Production environment. | Release version | Release date | | --------------- | ------------------------- | | v2025-07-16 | Wednesday 16th July (a.m) | New features, updates, and enhancements of note are summarised by product area, below: * [Process flows](#process-flows) * [Virtual environments](#virtual-environments) * [Connector builder](#connector-builder) ## Process flows

Type	Summary	Ref #
Enhancement	Transform functions list The list of transform functions (accessed via the map shape) is now sorted alphabetically within each category. Available transform functions	CPT-2916
Bug	Adding multiple transform functions Fixed an issue where adding multiple transform functions for a map shape could result in some settings not being cleared between saving one transform and creating the next. Working with field transformations	CPT-4044
Bug	Join transform function Fixed an issue where the `array` ➤ `join` transform function did not allow a blank `delimiter` field. Now, leaving this field blank joins the given array values without spacing or any other delimiter. Join transform function	CPT-3171
Bug	Cast to boolean transform function Fixed an issue where the `other` ➤ `cast to boolean` transform function processed `null` values incorrectly. Cast to boolean transform function	CPT-2863
Bug	Extra-long request URLs in logs Fixed a UI issue where very long request URLs exceeded the run logs modal layout. Wrapping is now applied when needed. Realtime run logs	CPT-3104
Bug	Save response in payload for SEND endpoints Fixed an issue where selecting the `save response in payload` option in a connector shape configured with a SEND type endpoint was not adding the endpoint's response to payloads. Configuring settings for a connector shape	CPT-4291
Bug	Optional header filters Fixed an issue where values entered as optional header filters (via the connector shape) were not passed into endpoint requests. The connector shape	CPT-4013

## Virtual environments

Type Summary Ref #

Enhancement Remove flows from an undeployed package
It's now possible to remove process flow versions from a package, provided that the package has never been deployed.
Managing virtual environment packages CPT-4440

Type	Summary	Ref #
Enhancement	Remove flows from an undeployed package It's now possible to remove process flow versions from a package, provided that the package has never been deployed. Managing virtual environment packages	CPT-4440
Enhancement	Virtual environment status Previously, when viewing virtual environments from the overview page, each virtual environment was associated with a `deployed` or `not deployed` status. For clarity, these status indicators have changed to `flows deployed` or `flows not deployed` , so you can see at a glance if flows have been deployed to an environment. The virtual environments overview page	CPT-4338
Enhancement	Flow version number added to run logs When viewing run logs, the flow version number is now appended to the flow name so it's clear which version ran. Working with run logs	CPT-4362

Enhancement

Virtual environment status
Previously, when viewing virtual environments from the overview page, each virtual environment was associated with a deployed or not deployed status.

For clarity, these status indicators have changed to flows deployed or flows not deployed , so you can see at a glance if flows have been deployed to an environment.
The virtual environments overview page

CPT-4338

Enhancement Flow version number added to run logs
When viewing run logs, the flow version number is now appended to the flow name so it's clear which version ran.
Working with run logs CPT-4362

## Connector builder

Type Summary Ref #

Type	Summary	Ref #
New	Base64 encoding for endpoints To handle cases where data returned from a source system is not in a standard text-based format (e.g. JSON or XML) but is instead binary (e.g. the raw contents of a PDF or image file), Base64 encoding is now supported for connector endpoints. Base64 encoding can be enabled via a new `response options` tab in the connector setup. When this option is enabled, the raw binary data received from the endpoint is automatically converted to a Base64-encoded string. Endpoint options	CPT-4468

New

Base64 encoding for endpoints
To handle cases where data returned from a source system is not in a standard text-based format (e.g. JSON or XML) but is instead binary (e.g. the raw contents of a PDF or image file), Base64 encoding is now supported for connector endpoints.

Base64 encoding can be enabled via a new response options tab in the connector setup. When this option is enabled, the raw binary data received from the endpoint is automatically converted to a Base64-encoded string.
Endpoint options

CPT-4468

--- # 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-07-16-release-notes-core.md?ask= ``` 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.