2025 12 03 release notes (core)
Release summary
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2025-12-03
Wednesday 3rd December (a.m)
New features, updates, and enhancements of note are summarised by product area, below:
Process flows
Flow deployment - disable option
When deploying a process flow via the view deployments modal, the default behaviour is for the flow to be deployed AND enabled, so it starts running according to defined triggers, immediately.
Now, you can choose to deploy a flow as disabled, so it will not run on any defined trigger settings. This is particularly useful if (a) you need to deploy a flow for testing and/or (b) you need to deploy flows so they can be included in blueprints.
CPT-4873
De-dupe shape performance improvements The de-dupe shape has been refactored for improved performance. Functionality is unchanged.
CPT-4252
Deleting a flow deployment via the canvas If you are working with a process flow and choose to delete an existing deployment via the view deployments modal, you are now prompted to confirm this action before it's completed.
CPT-4439
Manage your flows - latest run time
Fixed an issue where the latest run time in the manage your flows list was incorrect.
CPT-4527
Manage your flows - status filters Fixed an issue where applied status filters were not returning expected results.
CPT-4460
Flow version update time
Fixed an issue where the updated date/time for flow versions displayed in process flow settings was showing the wrong date/time.
CPT-4980
Blueprints
More information on installation failures You can now drill down for more information on blueprint installation failures, making it easier to find the cause.
CPT-4956
Deleting blueprint versions It's now possible to delete a specific blueprint version or the blueprint itself.
To delete a specific version, access the blueprint manifest and use the versions dropdown to see all available versions - each is now associated with a delete option.
CPT-4971
Email notification for bulk blueprint updates When the bulk update feature is used to force blueprint updates for selected installations, an email notification is generated upon completion. This email is sent to the email address associated with the user who triggered the update, confirming successes and/or failures.
CPT-4955
Cancel pending bulk blueprint updates Having triggered a blueprint update for multiple installations, the update jobs are queued and completed as soon as possible. Typically, this happens very quickly, but if you're updating lots of profiles with a complex blueprint, you may see pending updates. You now have the option to cancel any pending updates.
CPT-4957
Improved visibility for blueprint publish status When a blueprint is published (either after an initial build or an update), it is queued for upload to your private marketplace, and a notification is generated upon completion. To prevent timing conflicts, an 'update in progress' banner is displayed at the top of the manifest for the duration of the publish process. During this time, the blueprint is locked - it can't be changed or installed until the upload is complete.
You will always see this behaviour for new blueprints. For updates to existing blueprints, you'll only see the banner if you switch to the manifest for the latest version before it has finished uploading.
CPT-4970
Maximum number of blueprint versions A limit of 10 versions per blueprint is now enforced. This works on a first-in-first-out basis; if 10 versions exist and you attempt to publish another, you are prompted to delete the oldest version first.
Note that if the oldest version is also the active version, you must set a later version to be active before a new one can be published.
CPT-4971
Naming convention for blueprint versions Blueprint versions are now identified by a unique number, rather than a name.
CPT-4963
Deleting a blueprint If you choose to delete an entire blueprint (rather than a specific version), you must now confirm the action by entering the blueprint name in full.
CPT-4971
Opening a new blueprint draft When you choose to open a draft to update an existing blueprint, a change has been made so an empty manifest is displayed (previously, existing flows and resources were shown but not included unless selected again).
Blueprint installs page Fixed the following issues with the blueprint installs page:
Pagination was not working as expected. You can now step through page numbers correctly.
Item selections were not retained when stepping through pages. Current selections now persist.
Searching by name did not return the expected results. Search now works as expected.
CPT-4994
Bulk install status updates Fixed an issue where the status for updated company profiles was not updated consistently on the installs page.
CPT-5012
Bulk install status updates
Fixed an issue affecting blueprints that included process flows using a run process flow shape to call a sub-flow, and configured to use latest version of the flow. In this scenario, updating the sub-flow and then republishing the blueprint resulted in the older version of the sub-flow being called.
CPT-5002
Virtual environments
Flow deployment - disable option When deploying a package, the default behaviour is for all flows in that package to be deployed AND enabled, so they start running according to defined triggers, immediately.
Now, you can choose to deploy a package with disabled flows, so they do not run on any defined trigger settings. This is particularly useful if (a) you need to deploy flows for testing and/or (b) you need to deploy flows so they can be included in blueprints.
CPT-4873
Connector builder
Body format 'none' for authentication endpoints
Fixed an issue where setting the body format to none for an authentication endpoint resulted in a body of [] being sent.
CPT-4000
Last updated
Was this helpful?