2025 11 05 release notes (core)
Release summary
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2025-11-05
Wednesday 5th November (a.m)
This release is currently in testing; therefore, the items detailed below (together with associated documentation) are subject to change. Please check back on release day for final updates.
New features, updates, and enhancements of note are summarised by product area, below:
Process flows
Branch shape
The maximum limit of branches per branch shape (six) has been removed. Now, any number of branches can be added.
Branch shape
CPT-4763
Fallback transform function
It's now possible to specify one or more source fields that can be referenced for a fallback value.
Documentation in progress
CPT-4035
Blueprints
Connector endpoint scripts
Fixed an issue where pre-request and post-request scripts were not uploaded correctly when defined in blueprint process flows.
Pre-request scripts / post-request scripts
CPT-4710
Virtual environments
Sort & filter options
Additional sort and filter options have been added to tables throughout virtual environments pages.
Virtual Environments
CPT-4330
Flow deployment
You can now deploy a process flow via process flow settings and overwrite an existing deployment of that flow, if one exists. This also applies if you are deploying to no environment.
Previously, any existing deployment of a flow had to be deleted before another version could be deployed via process flow settings.
Deploying a process flow to a virtual environment
CPT-4386
Environment variable replacements
Minor UI enhancements for configuring environment variables.
Virtual Environments
CPT-4535
Underscores in environment variables
Underscores can now be used when naming environment variables.
Virtual Environments
CPT-4535
Partner features
Private marketplace blueprint updates
If you manage multiple company profiles and use blueprints to install process flows, it's now possible to update a blueprint and deploy changes to any 'child' companies where it's used.
Note that update functionality is available for any blueprints built after this release - it is not retrospective. If you have an existing blueprint that you want to update on an ongoing basis, you should build a new version, upload this to your private marketplace, and re-install for applicable child companies.
If you do this, take care to ensure that flow deployments from the previous blueprint version are disabled for each child company, and that the latest flows are active.
Documentation in progress
CPT-4748
Cascading permissions for master accounts
When a new child account is created, any active users associated with the parent company are automatically granted access to manage the child company. As an administrator, you can access the child company profile and remove any team members who don't require access.
Documentation in progress
CPT-4852
Last updated
Was this helpful?