This page summarises items scheduled for the following release to the Patchworks Production environment.
Patchworks core (backend)
1.24.3
21st August 2024 @ 9am
Patchworks dashboard (frontend)
1.18.1
21st August 2024 @ 9am
New features, updates, and enhancements of note are summarised by product area, below:
Delete items from run queue It's now possible to delete items from your run queue. Queued items are now displayed with a delete icon - click this to remove the run job from your queue.
CPT-3131
CPT-1297
CPT-3212
CPT-2117
Resources uploaded to the private marketplace for a parent company are visible in the private marketplace for that parent AND in the private marketplaces for any child companies
Resources uploaded to the private marketplace for a child company are visible in the private marketplace for that child AND in the private marketplace for the parent company AND in any private marketplaces for sibling-child companies
CPT-3273
CPT-2960
CPT-3254
Run logs for failed connections Fixed an issue where a failing connector with a long response body could give an 'internal failure' message - a more meaningful message is now output.
CPT-3288
Map shape - remove null & empty field conditions A new remove field conditions field is available for field mapping rows. You can use this to choose whether empty and/or null values are removed for this field.
Route shape - filter logic for multiple filters
When defining a route with multiple filters, you can now choose whether the logic for matching these filters is AND (so all defined filters must apply for a match) or OR (so any one of the defined filters will result in a match).
Map shape refactor The map shape has been refactored for improved performance and efficiency. There are no related changes in terms of functionality/usage.
Private marketplace resource visibility The visibility of private marketplace resources for parent/child companies (i.e. ) has changed. Now:
Cold storage for scripts
If a custom script is associated with an enabled process flow, it will never be un-deployed and put into 'cold storage'.
If a custom script has not been used for 4 days and is not associated with an enabled process flow, it is un-deployed and placed in 'cold storage'. If you add an un-deployed script to a process flow (via the or a ) it will be re-deployed automatically when called.
Route shape - routing method
Fixed an issue where setting the routing method to follow first matching route only in a draft version could change to follow all matching routes when the process flow is deployed.