Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2024-12-16
16th December 2024 - starting between 8-9am
New features, updates, and enhancements of note are summarised by product area, below:
This release is in the final stages of testing, therefore items detailed below are subject to change. This page will be updated up to the time of release.
CPT-3409
CPT-3253
CPT-3746
CPT-3077
CPT-3478
CPT-3767
CPT-3720
Company creation Fixed an issue where creating a company via the dashboard could occasionally result in the company being partially created in the database.
CPT-3821
Peoplevox uses SOAP authentication with tokens. Typically, this works by authenticating once and sending a valid token in response - this token is included in all subsequent requests until it expires. When the token expires, a 401 (authentication failed) A response is returned, and we will re-authenticate with the next request.
However, Peoplevox doesn't send a 401 response when a token expires - a 200 (success) code is returned and the outcome is included in the response body. So, we need an alternative approach to manage these requests.
We currently authenticate every Peoplevox request to ensure that valid tokens are always present. This happens automatically because a pre-authentication request script is applied for the SOAP authentication method on the Peoplevox connector.
This approach is reliable but not optimal in terms of performance.
In this release, the presence of a pre-authentication request script no longer triggers authentication for every request.
A new Peoplevox Re-Authentication Response Script has been developed, which should be applied to any connector steps in your process flows(s) where Peoplevox is used.
The script runs every time a connection is attempted and checks the <AuthenticateResponse><AuthenticateResult> section of the SOAP response body to determine success or failure. If authentication has failed, the connector step retries the request and re-authenticates for a new token. If authentication is successful, no re-authentication is required.
In this way, we only re-authenticate requests when necessary.
If you receive or send data from/to Peoplevox in process flows, follow the steps below to implement this enhancement.
Don't worry if you can't make these changes immediately - process flows with Peoplevox connectors will continue to run normally, though not optimally. For more information, please see The Peoplevox re-authentication response script.
Step 1 Install the Peoplevox Re-Authentication Response Script from the Patchworks marketplace.
Step 2 Apply this script to any process flow connector shapes where Peoplevox is defined as the source or target instance.
Step 3 Raise a ticket with Patchworks support for the Enhanced Peoplevox Re-Authentication feature to be switched on for your organisation.
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2024-12-04
4th December 2024 - starting between 8-9am
New features, updates, and enhancements of note are summarised by product area, below:
CPT-3429
Flow run logs - error visibility When viewing logs for a flow run, a status column is now included in the shape-by-shape breakdown panel. Here you'll see visual cues for warnings or errors encountered in a step, so it's easier to see where issues have occurred.
CPT-3510
CPT-3140
CPT-3130
CPT-3301
CPT-3733
CPT-3749
CPT-3513
Tracked data page Fixed two issues:
# characters are now supported when searching for values
Delay added so a search isn't attempted each time a character is added to the value field
CPT-3561
Login page The login page background has been refreshed.
CPT-3658
CPT-3591
Laravel 11 Patchworks Core has been upgraded to the Laravel 11 framework.
CPT-3586
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2024-10-16
16th October 2024 @ 9am
New features, updates, and enhancements of note are summarised by product area, below:
This update introduces a feature flag 'switch on' for a change that could cause some existing connector endpoints to break. The change (CPT-1085) relates to connector endpoints that SEND data via the request body, where the body format is set to none.
We have identified customers with existing endpoints that would be adversely affected by this change and we're in the process of reaching out to resolve any issues directly. If you are affected, this feature will NOT be switched on - all of your connectors will continue to operate normally.
If you are not affected, this feature will be switched on as part of this release.
Please check the Breaking changes section below for more information.
CPT-3167
CPT-3436
CPT-3523
Body content none for SEND endpoints
This update introduces a feature flag to manage a potentially breaking change for connector endpoints SENDing requests with body format set to none.
Affected customers have been identified and will receive an email detailing affected endpoints. This change will stay switched OFF for affected customers. For everyone else, it is switched ON as part of this release.
CPT-1085
CPT-3551
Additional libraries for PHP and C#
CPT-3527
When configuring connector endpoints which are set to SEND data via the request body, behaviour associated with the body format / none setting has changed.
Previously, if a connector endpoint includes static body content - or if your API passed payloads into the body - this content was passed into the request body even if the body format option was set to none. Now, all request body content is ignored if the body format option is set to none.
However, this change is behind a 'feature flag' which means this feature change is be switched on for customers in a controlled way.
This change has been released to prevent content from being sent erroneously.
An example of this is where an endpoint is defined to send specified JSON content in the body with the body format set to raw/json.
Before this update, if this option was subsequently changed to none (because existing JSON content is no longer required) but the specified content was not removed, it would continue to be sent.
If you have built connectors (using our connector builder) with an API that SENDs incoming payloads in the request body, you may be affected.
A handful of Patchworks marketplace connectors are affected.
We have identified customers who may be affected and in these cases, this feature change is switched OFF. This means there is no change to how your connectors (and therefore process flows) behave.
If you are affected, we will be reaching out individually by email, before our release on the 16th October 2024. In this email, we will list any affected connectors and process flows. Then, you can either:
Check/update your own endpoints (see instructions below) - then notify Patchworks that you're happy for this feature change to be switched on
OR
Raise a support ticket for Patchworks assistance with required fixes and then switch the feature change on
All affected customers will be notified before the 16th October 2024. If you don't receive an email, you are not affected by this change and it will be switched ON from the 16th October 2024.
No. This feature change will remain switched off for affected customers until either:
You notify Patchworks that you've fixed your own endpoints and are ready for the feature change to be switched ON
OR
You have completed the required fixes on a call with Patchworks and confirmed that you're happy for the feature change to be switched ON.
Whilst there is no deadline, we strongly recommend that you take the time to ensure that affected endpoints are fixed so we can switch the feature change ON for your company profile. This will ensure that the body format / none option functions as expected, removing the risk of payloads being passed inadvertently.
If you've fixed your own endpoints and are ready for the feature change to be switched ON, please get in touch with support. The feature change will then be switched on as soon as possible, and you will be notified when this is complete.
If you want to check/update your connector endpoints, the required steps are detailed below.
Step 1 Log in to the Patchworks dashboard, then select process flows > connectors & instances:
Step 2 Click the settings icon associated with a connector that you want to update:
Step 3 Click the endpoints tab:
Step 4 Click the name of the endpoint that you want to update:
If the connector includes a lot of endpoints, use CTRL+F to search for a specific part of the endpoint name.
Step 5 Click the body tab from the endpoint setup page:
You only need to change SEND endpoints where the body formatoption is set to none and you expect bodycontent to be passed into the request.
Step 6 Click in the body format field and select raw from the dropdown list:
With this setting, any incoming payload will be sent in the request body.
Step 7 Set the data type as required (the default is JSON):
Step 8 Click the save and go back button at the bottom of the page.
Step 9 Repeat for each affected endpoint.
Step 10 This step is only required if affected endpoints are associated with a connector that has been uploaded to your private marketplace:
If an affected connector exists in your private marketplace, you should re-upload it so the latest version is available in future. See Changing a private marketplace connector for more information.
If an affected connector is part of a private marketplace process flow, you should delete the existing process flow from your marketplace and upload the latest version. See Changing other private marketplace resources for more information.
If an affected connector is part of a private marketplace blueprint, you should re-upload it so the latest version is available in future. See Changing a private marketplace blueprint for more information.
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2024-10-30
30th October 2024 - starting between 8-9am
New features, updates, and enhancements of note are summarised by product area, below:
Connection pools For systems where concurrency limits are important (e.g. NetSuite), you can now define connection pools to dispatch simultaneous requests based on a given concurrency limit. Connection pools are configured (via a new navigation menu option) and then assigned to connector instances.
Even if your integrations don't require concurrency limits, this feature can also be useful when testing process flows where lots of data is sent at the same time. With a connection pool, you control how many requests are sent.
CPT-3502
Production flow indicator
A new production flow toggle option is available in process flow settings. Activating this allows Patchworks to receive alerts which may be analysed to understand trends and for future enhancements.
CPT-3329
XML support for payload variables
Payload variables now support XML payloads. The syntax is the same for both JSON and XML - e.g. [[payload.xyz]].
CPT-3335
Faster flow run queue execution
All scheduled process flow runs are added to your run queue and then run when a slot becomes available. When jobs are run depends on several factors, including a platform-wide FLOW_QUEUE_FREQUENCY - this is the frequency at which run jobs are picked from your queue. In this release, the FLOW_QUEUE_FREQUENCY is reduced from 30 seconds to 20 seconds, which means consecutive flow runs are faster.
CPT-3440
Improved handling for connector re-authentication Previously, if a connector step received a 401 response (failed authentication), it would re-authenticate, fail the step, and then retry with new authentication details. Now, re-authentication happens without failing the step.
CPT-3523
Company insights gauge labels Gauge labels have been updated for greater clarity.
CPT-3508
SOAP authentication body content Fixed an issue where body content could not be added when configuring SOAP authentication.
CPT-3502
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2024-11-07
7th November 2024 - starting between 8-9am
New features, updates, and enhancements of note are summarised by product area, below:
Connection pool timeout option A timeout option has been added to connection pool settings, so you can determine the number of seconds that a request should wait for a connection pool slot to become available, before timing out. If no timeout is defined, a default timeout period of 240 seconds applies.
CPT-3677
Queuing sub-flows from a manual run Previously, if a process flow contained a run process flow shape to call sub-flows and was run manually, all sub-flows would be triggered immediately (bypassing the queue system). Now all sub-flows are added to your run queue and will be processed according to standard queue rules (e.g. priority and flow concurrency allowance).
CPT-3426
Map shape - array transformations Fixed an issue where some transform functions did not transform all items in an array - only the first item was processed.
CPT-3661
System status URL
Fixed an issue where the system status link in the footer of the dashboard login page directed users to an old status page.
CPT-3670
Skip option for process flow shapes
To help when designing/testing process flows, a new skip option is available for all process flow shapes (except for ). This is a toggle option at the top of the settings drawer - when toggled on, the associated step is skipped whenever the flow runs.
Documentation in progress
Delete inactive process flow versions
It's now possible to delete inactive versions of a process flow.
Each time a process flow is deployed, the previously deployed version becomes inactive. All inactive versions are retained indefinitely, so if you have lots of flows with multiple iterations, it can be useful to remove older, inactive versions.
Documentation in progress
Postman importer The maximum file size allowed for import has increased from 5MB to 50MB. The Postman importer is now out of BETA.
Flow variables can now be made secret It's now possible to mark string-type flow variables as secret. This means that any value provided for this variable is not displayed anywhere in the system, and is stored securely. Documentation in progress
Company insights - CPU usage For greater clarity, CPU usage bars now display usage figures. Documentation in progress
Relative dates in scripts
Fixed an issue where relative date flow variables used in scripts were reset to -0 seconds.
Peoplevox re-authentication In this release, we've added a feature to enhance performance for Peoplevox re-authentication. This is an 'opt-in' feature - please see the notes for details and implementation requirements.
Delete all flows in queue It's now possible to delete run jobs from your queue. New options are available to remove all run jobs for a selected process flow and to clear the entire queue.
Support for dynamic dates in variables & filters Dynamic date types are now supported for , , , and .
Syntax highlighting for manual payloads Syntax highlighting has been added for the and the option.
Set variables shape Spaces are now supported in variable value names.
Map shape - stacked transform functions Fixed an issue where stacking transform functions (i.e. asking one transform to use the output from a previous transform) could fail because a source value was passed in rather than the last output transform.
Map shape - stacked transform functions
Fixed an issue where the remove on empty may not work as expected when multiple transforms are applied to a field.
Default values for multiple filters Fixed an issue where settings applied to the first filter became default settings for any subsequent filters added - this affected filter and track data shapes.
Registration The registration process now includes a step for users to accept terms & conditions. Documentation in progress
Try/catch shape Our new try/catch shape gives you full control over how process flow exceptions are handled. Errors are caught, removed from the flow and sent down your defined path (for example, you might use the to alert contacts about issues and/or add exceptions to a for follow-up processing).
Queue priority setting for process flows
A new queue priority option is available in process flow settings. Use this to determine whether runs for this flow should be picked from your as a high, low, or regular priority (the default is regular).
Improved error message for invalid endpoint URL If a connector request is calling / (i.e. the endpoint URL has not been defined), a clear message is now displayed in run logs, advising the user to check the request endpoint (previously an internal error message was given).
For more information please see our section below.
Endpoint names should not be unique between connectors
Fixed an issue where a duplicate name error was incorrectly prompted when attempting to create an endpoint with the same name as another endpoint associated with a different connector. Endpoint names are not unique between connectors.
The library has been added for PHP 8.1 and 8.2, allowing you to read and write various spreadsheet file formats.
For C#, and libraries have been added.
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2024-10-02
2nd October 2024 @ 9am
New features, updates, and enhancements of note are summarised by product area, below:
Process flows
CPT-3167
Track data shape The existing track data shape has been completely overhauled with new functionality within the shape itself, and related dashboard areas.
CPT-2515
CPT-3345
CPT-2590
CPT-2869
CPT-3418
CPT-3145
CPT-2912
CPT-2607
Platform status information The status link in the left-hand navigation menu has been updated and now navigates to our refreshed status page.
CPT-3443
If you use process flows to sync data, the underlying architecture for your system is Core. All Core releases are summarised below.
New skip shape option, ability to delete inactive flow versions, Peoplevox re-authentication enhancements, and more.
Delete flow runs from queue, and more.
Connection pool enhancement for user-defined timeouts, and more.
New global connection pools, faster consecutive flow runs, and more.
New try/catch shape, a possible breaking change for SEND endpoints with a body format of none, and more.
New notify and track data shapes, and more.
New partner features, and more.
Enhanced run process flow shape, and more.
Added a delete option for queued run jobs, and more.
Introducing blueprints (replacing apps).
Introducing blueprints (replacing apps).
Note: This release has been rescheduled.
New partner features bolt-on, response scripts, and more.
New partner features bolt-on, response scripts, and more.
Note: This release has been rolled back.
New 'operations' and improved queuing for process flow runs. Possible breaking change included.
New filter types for 'in' and 'not in' scenarios. Possible breaking change included.
All new company insights, and more.
Switch from Laravel Horizon/RabbitMQ to Supervisord/RabbitMQ.
Switch from Laravel Horizon/RabbitMQ to Supervisord/RabbitMQ.
Write flow run logs from custom scripts, and more.
Add custom names to shapes in a process flow, and more.
Clearer indication of process flow runs completed with warnings in logs, and more.
New transform functions, and more.
Event triggers & company profile banners.
Event triggers & company profile banners.
Import and export map shape configuration , and more.
New GraphQL pagination method for Shopify, and more.
New track data shape, and more.
Import & export cross-ref lookups and de-dupe data, new download run logs option, and more.
Introducing private marketplaces, shape notes, and more.
Bug fixes.
New expect empty payload option, and more.
New retry failed process flow option, new clone connector endpoint option, and more.
New process flow run queues, and more.
New core subscription tiers, new roles, and more.
New run process flow and set variables shapes, new round number transform function, and more.
Bug fixes.
Create instances as part of app installation, and bug fixes.
Bug-fix release.
New prebuilt connectors and minor bug fixes.
Introducing apps, prebuilt process flows and an all-new marketplace.
Hotfix release.
Introducing apps, an all-new marketplace, and more.
Introducing multi-company support, Postman importer, and more.
Enhancements to run logs, cache maintenance, and more.
Introducing the de-dupe shape, and more.
Introducing the scripts marketplace, cache maintenance, and more.
Duplicate process flows between company profiles, and more.
Introducing an all-new process flow home page, email alerts for process flow run failures, and more.
New run logs and webhook enhancements.
Payload variable support for cache shapes, and more.
New cache shapes, flow variables, and more.
New layout for the company profile form.
Multi-language support, view multiple payloads, and more.
Introducing webhook support for process flow triggers, pre & post request scripts for connector builder authentication methods, and more.
Multi-language support, variables & parameters from incoming payload, enhanced real-time process flow logs, and more.
Launch of new Core features - process flows, marketplace, and connector builder.
This page summarises items scheduled for the following release to the Patchworks Production environment.
Patchworks core (backend)
1.27.0
11th September 2024 @ 9am
Patchworks dashboard (frontend)
1.20.0
11th September 2024 @ 9am
New features, updates, and enhancements of note are summarised by product area, below:
All shapes - source/target inheritance Shapes will not longer inherit source/target instance & endpoint details from the previous connector step.
CPT-3412
Run process flow shape settings Fixed an issue where run process flow shape settings were not retained when the process flow was installed from the marketplace.
CPT-3280
Run process flow shape - payloads Fixed an issue where the payload passed into a run process flow shape wasn't being passed to the next shape, causing the flow to stop.
CPT-2278
Setting meta variables from a manual payload Fixed an issue where setting variables (via a set variables shape) from a manual payload was not working as expected.
CPT-3219
Route shape - is null comparison Fixed an issue where a process flow would stop if a route condition included an IS NULL condition and the element did not exist in the payload.
CPT-2405
Map shape - override source/target format
Fixed an issue where selections made for override source format and override target format option were not saved correctly.
CPT-3396
CPT-3045
UI updates A number of minor UI updates have been made, including: max limit indicator on gauges now shows how far over the allowance usage has gone; data numbers are now shown in GB; info icon added to operations dial.
CPT-3202
Reactivate Deleted Users Patchworks Admin users now have the ability to reactivate deleted users.
CPT-2699
Map Source no longer auto selected The mapping source is no longer auto selected based on the previous connections shape,
CPT-3419
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
1.21.5
17th July (starting between 8am-9am)
Patchworks dashboard (frontend)
1.15.7
17th July (starting between 8am-9am)
This release includes preparatory information for an upcoming change which affects the behaviour of filters when values are not of the expected data type. Please ensure that you check the Breaking changes section.
New features, updates, and enhancements of note are summarised by product area, below:
New filter types for 'in' and 'not in' scenarios
To handle cases where a filter needs to match incoming data based on one of many given values being present/not present, two new filter types have been implemented: Contains one of many and Does not contain one of many.
CPT-1872
Shape source endpoint selector In shapes where source instance/endpoint options are available (e.g. connector, flow control, route), the endpoint selector has been enhanced to include a search field, so you can quickly search for the required endpoint by name.
CPT-2500
Run process flow shape When selecting a process flow to be initialised from a run process flow shape, ALL defined process flows and associated versions are available for selection (by default, the latest is prompted). This removes the restriction of only being able to call deployed & enabled process flows.
CPT-2983
Filters: enforced validation for data types Additional validation has been added for filters, which means that input values must be of the expected data type. For example, consider the payload below:
Notice that both records include a ref field, but one (Jane) is a string type value and the other (Bob) is a number type value. Now suppose we define a filter to examine the ref field, and to expect the value of this field to be a number .
Previously, the data type was not validated, so both records (Jane and Bob) would have been matched. Now, the data type defined in filters is validated and a record will only be matched if the filter value is of the expected type. This is a phased change.
Phase 1 (this release)
In this release, any data type validation issues will be reported as warnings in run logs but this will not cause filter behaviour to change. So taking our example above, both records (Jane and Bob) would continue to be matched.
Phase 2 (next release)
In our next release, data type validation for filters will be enforced - i.e. filter behaviour will change so a record will only be matched if the required value is of the expected type. Taking our example above, only Bob will be matched - Jane would not be matched because the ref field is provided as a string.
CPT-2862
Company insights - usage stats Fixed issue where usage figures shown in the left-hand navigation bar may not match the main customer insights page.
CPT-1568
Company insights - graph display Fixed issue where the graph display could be lost when switching between process flows/connectors/shapes tabs multiple times in quick succession. Now, switching between tabs is not possible until the current graph is fully loaded. In a related issue, graph zoom has been disabled.
CPT-3097 CPT-3098
Static date selector for variables Fixed issue where no time selector was available when choosing to add a static date/time in a flow variable or in the set variables shape.
CPT-2451
Route shape settings Fixed issue where creating a new route for a route shape did not go on to display settings for that route. Now, associated settings are shown when a new route is created.
CPT-3129
This release includes changes that may affect the behaviour of filters defined in existing process flows. Please follow the advice below to avoid any issues.
When defining process flow filters (for example, in a filter or route shape), you select a data field and then the corresponding data type for this field - for example:
In this release, we start to enforce the specified data type for any filters. For example, if a filter based on the customer_id field is defined to expect string data, but the incoming payload provides these values as numbers, this will cause a validation error.
Filter validation issues will be enforced in two phases:
1: Warning
17th July 2024
2: Enforcement
If a process flow runs and an invalid data type is passed into a filter, a warning message is displayed in the run logs.
A record that previously matched a filter based on the required filter value will now fail to match if that value is not of the expected data type.
Phase 1 is scheduled for implementation on the 17th July 2024. We recommend making the following checks before this time:
Filter & route shapes
Check any filter and route shapes in your process flows now, and ensure that defined data types reflect your source data. If you find a mismatch, you can:
Change the data type for the process filter, if appropriate
Apply a field transform (via a map shape) immediately before the filter step to convert incoming values to a different data type. Several transform functions are available which can help to change data from one type to another - please see Working with field mapping transformations for more information.
Change the data type for this value at source (if you have the option to do so)
Connector shapes
Check any connector shapes in your process flows, and ensure that defined data types reflect your source data. If you find a mismatch, action depends on whether the connector is a standard Patchworks connector or a custom connector that was built by your own company with the Connector builder:
For a standard Patchworks connector, it’s advisable to change the data type for this value at source. If this isn’t possible, you can edit the filter within the connector endpoint setup and change the data type to match source data. However, be aware that if you subsequently install a Patchworks update for this connector, your changes will be overwritten.
For custom connectors, you can edit the filter within the connector endpoint setup and change the data type to match source data.
After the release on the 17th July 2024, please review run logs for all of your active process flows and check if there are any warnings - for example:
You can filter your run logs list so that only entries with warnings are displayed.
If warnings are given, please check the associated process flow and make changes as detailed above.
Phase 2 is scheduled for implementation on the 24th July 2024. We recommend checking run logs for your flows with extra care as soon as possible after this release, just in case validation issues are still present.
Please see release notes for the 24th July 2024 regarding Phase 2 of this change, and also Phase 2 of a similar change to transform validations.
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
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
1.25.0
8th August 2024 @ 9am
Patchworks dashboard (frontend)
1.18.0
8th August 2024 @ 9am
Introducing blueprints In this release, we introduce blueprints. Replacing apps, Blueprints are templates for automating data flows between specific systems.
The most notable change is that Blueprints can be purchased directly from the Patchworks website. Once purchased, a blueprint becomes available in your dashboard (via the marketplace) within 24 hours.
In the dashboard marketplace, you'll find that apps are now referred to as blueprints however, you will only see blueprints that your organisation has purchased via the Patchworks website.
CPT-3123
This release has been rolled back. Items detailed below will be included in our next scheduled release - 7th August 2024.
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
1.23.0
31st July @ 9am
Patchworks dashboard (frontend)
1.17.0
31st July @ 9am
New features, updates, and enhancements of note are summarised by product area, below:
Partner features subscription bolt-on A new partner features bolt-on is available for Patchworks partners to purchase. This allows Admin users to create new, linked companies for ongoing management.
When the partner features bolt-on is enabled, allowances are provided for the number of companies that can be created for different . For more information, please contact your Patchworks Partner Manager.
CPT-3304
Response scripts for connector shapes
There may be scenarios where you need to control whether a process flow shape or run should fail/continue based on information returned from a connection request. To achieve this, you can now apply a response script to your connector shape, utilising a new response_code feature to determine the outcome.
CPT-2913
Custom scripts - Python requests library The requests HTTP library has been added for Python scripts.
CPT-2407
Shape documentation
Relevant documentation can now be accessed directly from the settings drawer for any shape - look for the ? icon in the top-right corner.
CPT-2932
JSON encode transform function The JSON encode transform function has been enhanced so now any data type is supported.
CPT-3217
Endpoint content types
UTF-8, ASCII and ISO-8859-1 charsets are now fully supported content types.
CPT-3085
This page summarises items scheduled for the following release to the Patchworks Production environment.
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
This release includes possible breaking changes related to the validation of process flow filters and transforms. Please ensure that you check the section.
New features, updates, and enhancements of note are summarised by product area, below:
This release includes changes that may cause process flow runs to produce errors, or to fail. Please follow the advice below to avoid any issues:
When defining process flow filters (for example, in a filter or route shape), you select a data field and then the corresponding data type for this field - for example:
In this release, we start to enforce the specified data type for any filters. For example, if a filter based on the customer_id field is defined to expect string data, but the incoming payload provides these values as numbers, this will cause a validation error.
Filter validation issues will be enforced in two phases:
Phase 1 was implemented on the 17th July 2024. We recommended making the following checks before this time:
Filter & route shapes
Change the data type for the process filter, if appropriate
Change the data type for this value at source (if you have the option to do so)
Connector shapes
You can filter your run logs list so that only entries with warnings are displayed.
Phase 2 is implemented in this release. We recommend checking run logs for your flows with extra care as soon as possible after this release, just in case validation issues are still present.
For example, if a string > lowercase transform is defined to convert the customer_id field to lowercase but the incoming payload provides these values as numbers, this will cause a validation error.
Transform validation issues will be enforced in two phases:
We recommend checking run logs for your flows with extra care before and after this release, just in case validation issues are still present.
Change the data type associated with this value at source (if you have the option to do so).
Add a transform function immediately before, changing source data to the required type. For example, cast a string to a number or a number to a string.
Use a different transform function (if applicable).
This release has been postponed. Items detailed will be rescheduled as soon as possible.
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
Notify shape Use this shape to send a custom notification message into the run logs and (if required) as an email alert to selected notification groups.
In shape settings, you can now define your own success criteria to determine if a tracked entity was processed successfully or not. This can be particularly useful when sending data to systems that return 'successful' response codes even when there are data issues - now you can examine the payload and apply filters to mark a success/failure outcome for viewing in tracked data summaries.
Tracked data page A new tracked data page is available from the left-hand navigation menu. Use this to search for tracked entities and view their processing journey.
Save response in payload
A new save response in payload option is availabe in the response handling section of connector settings. Use this option to add the response from a request to the payload (meaning it can be interrogated subsequently using ).
By default, response information is added to payloads in a field named response but you can define your own field name if needed.
Process flows home/overview page - tracked data The tracked data panel has been removed from the right-hand side of this page. Tracked data (tracked via the track data shape or tagged endpoints) is now accessed from the new tracked data page.
Process flow settings - remove failed payloads
A new remove failed payloads option is available from process flow settings.
Now, when multiple payloads pass through a flow (for example, when receiving paginated data or batching one payload to many using ), you can use this option to remove any problematic payloads so the process flow can complete successfully.
If a process flow completes with failed payloads, its status is set to partial success - any failed payloads can be viewed and downloaded from .
Run process flow shape When a run process flow is configured, you can now access the 'called' flow from a link included in shape info on the canvas.
Settings drawer behaviour Previously when updating the settings drawer for any process flow shape, clicking outside of the drawer caused it to close - sometimes resulting in the loss of unsaved changes. Now, you must actively choose to save or cancel settings for the drawer to close.
SFTP connector - allow unsuccessful statuses
Fixed an issue where the SFTP connector was not honouring the allow unsuccessful statuses option, so a flow would fail if a file could not be moved.
Partner features support If you manage multiple linked companies (using our ), you can choose to view aggregated insights for your linked companies.
For more information please see the section.
In this release, any data type validation issues will be reported as warnings in run logs but this will not cause filter behaviour to change:
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.
Check any and shapes in your process flows now, and ensure that defined data types reflect your source data. If you find a mismatch, you can:
Apply a field transform (via a ) immediately before the filter step to convert incoming values to a different data type. Several transform functions are available which can help to change data from one type to another - please see for more information.
Check any shapes in your process flows, and ensure that defined data types reflect your source data. If you find a mismatch, action depends on whether the connector is a standard or a custom connector that was built by your own company with the :
For a standard , it’s advisable to change the data type for this value at source. If this isn’t possible, you can edit the filter within the and change the data type to match source data. However, be aware that if you subsequently install a Patchworks update for this connector, your changes will be overwritten.
For custom connectors, you can edit the filter within the and change the data type to match source data.
After the release on the 17th July 2024, please review for all of your active process flows and check if there are any warnings - for example:
If warnings are given, please check the associated process flow and make changes as detailed .
Similar to the filter validation enforcement change detailed , this release enforces the specified data type for .
With the implementation of Phase 1 on the , you will have been receiving warning messages in in the event of any transform validation errors.
If warnings are present, check any in relevant process flows and look for . Where found, check whether an expected data type is specified and if yes, ensure that defined data types reflect your source data. If you find a mismatch, you can:
1.26.0
29th August 2024 @ 9am
1.19.0
29th August 2024 @ 9am
Blueprints marketplace link When viewing the marketplace tab for blueprints you can now navigate directly to the Patchworks store to view all available blueprints.
CPT-3388
Run process flow shape The Run process flow shape has been enhanced to make version management of sub-flows easier.
When defining which sub-flow to call from the Run process flow shape previously, a specific version had to be selected. So, if that sub-flow changed in future it was necessary to edit any associated Run process flow shapes to call the latest version.
Now, Run process flow shape options have been changed so when defining a sub-flow to be called you can choose to always run:
the latest deployed version
the latest draft version
a specific version
CPT-3235
Connector shape - expect empty response
The expect an empty response setting in connector shapes is now available for GET requests (previously it was only displayed if the selected endpoint was a POST request).
CPT-2836
Cross-reference lookups - duplicate values The error message displayed when attempting to save an existing value has been enhanced. It's now clear that the reason for failure is duplication (previously a generic message was displayed).
CPT-3274
Cross-reference lookups - special characters Special characters can now be used in cross-reference lookup names and descriptions.
CPT-2779
Run process flow shape - flow variables Fixed an issue where the value provided to overwrite a flow variable did not persist.
CPT-3234
Connector shape responses tab unavailable Fixed an issue where adding a response script to a connector shape caused the responses tab to be unavailable in live run logs.
CPT-3272
Non UTF-8 characters in FTP payloads Fixed an issue when sending a payload containing non UTF-8 characters in to a script step resulted in a character set error.
CPT-3279
Error saving connector settings Fixed an issue where a missing translation caused an error when attempting to save connector shape endpoint settings using any language other than English.
CPT-3381
Expired tokens Fixed an issue where expired tokens were not being refreshed in the scenario where a token authenticates successfully in the first step of the flow but expires later in the same flow.
CPT-3315
Data usage dial Fixed an issue where the data dial colour wasn't updating to reflect usage.
CPT-3191
Managed companies list pagination Fixed page links for the managed companies page.
CPT-3340
Cloned endpoint headers Fixed an issue where endpoint headers were not copied verbatim when an endpoint was cloned.
CPT-2534
1.20.0
18th June 2024 @ 8am
1.15.0
18th June 2024 @ 8am
CPT-2931
CPT-2961
Improved logs for regex transform failures
The following transform functions use a regex expression to split strings according to a user provided delimiter: Last word, First word, split.
CPT-2954
CPT-2951
CPT-2914
MySQL database access from PHP scripts
CPT-2927
Field tags duplicated when multiple schema items are present
CPT-2765
1.24.0
7th August 2024 @ 9am
1.17.0
7th August 2024 @ 9am
Partner features subscription bolt-on A new partner features bolt-on is available for Patchworks partners to purchase. This allows Admin users to create new, linked companies for ongoing management.
When the partner features bolt-on is enabled, allowances are provided for the number of companies that can be created for different core subscription tiers. For more information, please contact your Patchworks Partner Manager.
CPT-3304
CPT-2913
CPT-2894
CPT-1921
CPT-2918
CPT-2991
CPT-2407
CPT-2932
CPT-3217
CPT-3239
CPT-3282
CPT-3282
Endpoint content types
UTF-8, ASCII and ISO-8859-1 charsets are now fully supported content types.
CPT-3085
1.22.0
24th July @ 9am
1.16.0
24th July @ 9am
Operations Historically, Patchworks usage has been tied to the number of transactions processed. In this release, transaction counts are retired and the concept of operations is introduced.
Operations are a simpler, more visible way to track your use of the Patchworks platform. An operation is counted whenever a request is made (successfully or otherwise) to send or receive a payload to/from an endpoint. This may be via connector shapes, webhooks, events, or using the Patchworks API.
You can view aggregated operations for a month via your Company insights page and per process flow run via Run logs.
CPT-3062
Process flow queues How process flow run jobs are queued has been improved to help ensure that race-condition scenarios are avoided.
Previously, it was possible to hit a race condition with flows, where an ever-increasing number of flows would simultaneously drain and compete for resources with other running flows that use the same connector instances. In this release, a concurrent process flow run limit is enforced per company - so only a certain number of flows (as determined by your subscription tier) can run simultaneously.
CPT-3157
Field mapping string transforms With two exceptions (below), all string-type transform functions will now allow empty strings to be passed in. Previously, if a string transform received an empty value, the map step would fail.
The two exceptions are country name and country code. These transform functions will still cause the map step to fail if empty values are received.
CPT-3192
Filters: enforced validation for data types Additional validation has been added for filters (wherever applied), meaning that input values must be of the expected data type.
This is a phased change. Phase 1 was implemented on the 17th July 2024. Phase 2 is implemented in this release. For more information please see the Breaking changes section.
CPT-2862
Transforms: enforced validation for data types Additional validation has been added to all transform functions, which means that input values must be of the expected type. For example, if a transform function is expecting a number value for its input and a string is provided, validation will fail. This is a phased change. Phase 1 was implemented on the 21st March 2024. Phase 2 is implemented in this release. For more information please see the Breaking changes section.
CPT-2982
Connector instance timezone & optional filters Fixed an issue where the timezone selected for a connector instance was not reflected when optional relative date filters were applied in the process flow connector shape.
CPT-3144
Initialise flow with data & a relative time variable Fixed an issue where a process flow variable defined with a relative time variable did not resolve as expected when the process flow was run via the Initialise flow with data option.
CPT-3155
1: Warning
2: Enforcement
If a process flow runs and an invalid data type is passed into a filter, an error message will be displayed in the run logs and the process flow run will fail.
24th July 2024
1: Warning
If a process flow runs and an invalid data type is passed into a transform function, a warning message is displayed in the run logs. This message includes the name of the transform function that needs to be checked/updated. For example:
Any issues identified in this way will not cause the process flow to fail at this time. However, if identified issues are not resolved, the process flow will fail when Phase 2 of this change is released.
Note: This phase was implemented on the 21st March 2024.
2: Enforcement
24th July 2024
1.17.0
15th May 2024
1.13.2
15th May 2024
Event connectors (BETA)
Event connectors can now be used to trigger process flows by listening for events that are published to message queues/topics by a message broker (e.g. RabbitMQ).
CPT-1668
CPT-2408
Map configuration import
CPT-2801
Company profile dashboard banner
CPT-2613
1.17.0
23rd May 2024 @ 9am
1.13.1
23rd May 2024 @ 9am
Event connectors (BETA)
Event connectors can now be used to trigger process flows by listening for events that are published to message queues/topics by a message broker (e.g. RabbitMQ).
CPT-1668
CPT-2408
Map configuration import
CPT-2801
Company profile dashboard banner
CPT-2613
1.18.0
30th May 2024 @ 9am
1.13.2
30th May 2024 @ 9am
Run logs - retried status
A new status retried status badge has been added to the Run logs page. This is displayed if an enabled process flow run has failed and then subsequently retried via the retry button.
CPT-2700
CPT-1813
CPT-1813
CPT-2782
CPT-2782
Sidebar navigation - additional help links
The left-hand navigation bar has been extended to include the following links under 'Help':
System status - check the current status of the Patchworks platform
API - access Patchworks API documentation
Training - log into the Patchworks training platform
CPT-2747 / 2771
CPT-2187
CPT-2486
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.14.0
11th April 2024
Patchworks dashboard (frontend)
1.11.0
11th April 2024
New features, updates, and enhancements of note are summarised by product area, below:
App install failure
CPT-2668
Missing connector information after app install
CPT-2569
CPT-1536
CPT-1322
Connector shape - configurable retries
It's now possible to configure the number of retries (between 0 and 2) that should be made when attempting to make a connection in a process flow.
CPT-2333
CPT-2702
CPT-2370
CPT-2511
CPT-2440
CPT-2452
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.16.0
1st May 2024
Patchworks dashboard (frontend)
1.13.0
1st May 2024
New features, updates, and enhancements of note are summarised by product area, below:
Custom script selection
CPT-2733
Event connectors (BETA)
Event connectors can now be used to trigger process flows by listening for events that are published to message queues/topics by a message broker (e.g. RabbitMQ).
CPT-1668
CPT-2121
CPT-2800 CPT-2799
Dynamic dates now use flow run time
Some process flow steps (connectors, filters, set variables, transforms, etc.) can be configured to use dynamic/relative dates, where the date is relative to the time the process flow is initialised.
With the recent introduction of queues for process flow runs, all process flows are added to a queue when they are initialised (either by a defined trigger, or a manual run). This means that the time a flow is initialised is not the same as the time the flow actually runs - sometimes the run will be almost instant, but in busier periods there may be some minutes between starting and running a flow.
To prevent cases where records are missed because they were added between the time a flow was started and the time it actually ran, a new Use queued time process flow setting has been introduced. This allows you to choose whether any relative dates should be based on the time that the process flow is initialised or the time it is queued.
CPT-2455
Transform functions - null values The default behaviour for transform functions has changed so that by default, if they are given null, they return null. Exceptions to this are:
Custom Dynamic Date. Returns the custom dynamic date set in the transform function.
Custom Static Date. Returns the custom static date set in the transform function.
Date Now. Returns the date now as the transform is run.
Custom Number. Returns the custom number set in the transform function.
Custom Boolean. Returns the custom boolean set in the transform function.
Fallback. Returns the custom fallback value set in the transform function.
Custom String. Returns the custom string set in the transform function.
Null Value. Returns null.
CPT-2773
Process flow version update dates
CPT-2603
SSH2 Extension
CPT-2777
Enforced MFA at company level If any company that a user is related to has MFA enabled, the user may not disable MFA. In this scenario, the Disable MFA option cannot be selected - instead, the user will see a message advising that MFA is enforced by their company.
CPT-2027
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.12.0
27th February 2024
Patchworks dashboard (frontend)
1.9.0
27th February 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-2236
CPT-2285
CPT-2373
CPT-2234
CPT-1084
CPT-2157
CPT-2380
CPT-2395
CPT-2390
CPT-2381
CPT-1161
CPT-2230
CPT-2375
CPT-2376
CPT-2378
CPT-2398
CPT-2428
CPT-2389
CPT-2388
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.12.3
29th February 2024
Patchworks dashboard (frontend)
1.9.2
29th February 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-2242
CPT-2267
CPT-2462
CPT-1221
CPT-1221
CPT-1824
CPT-1870 CPT-2046
CPT-2023
CPT-1996
CPT-1761
CPT-2448
CPT-1854
CPT-1652
CPT-1854
Script errors Fixed issues where script errors were not being displayed in run logs.
CPT-2460
CPT-2321
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.13.7
21st March 2024
Patchworks dashboard (frontend)
1.10.3
21st March 2024
New features, updates, and enhancements of note are summarised by product area, below:
This release includes preparation for an upcoming breaking change related to the validation of field mapping transform functions. Please ensure that you check the Breaking changes section.
CPT-1857
CPT-2569
CPT-2199
CPT-2119
CPT-2119
CPT-2104
CPT-1507
CPT-1901
CPT-2582
CPT-2567
CPT-2463
CPT-2439
Long company names Fixed issue where a very long company name caused UI anomalies.
CPT-2435
Extra validation has been added to all field mapping transform functions, which means that input values must be of the expected type. For example, if a transform function is expecting a number value for its input and a string is provided, validation will now fail. Previously, validation was not enforced for all transform functions.
To ensure that customers have time to address any issues with existing process flows, this change will be implemented in two phases, as below:
1
This release
2
Enforcement phase If a process flow runs and an invalid input type is passed into a transform function, the process flow will fail.
Future release (not less than two weeks later)
If you see a transform function warning message in your logs, you should access settings for the map shape and review the relevant transform function - what type of data are we expecting to be passed in?
Next, check the incoming payload for data values associated with this transform - it's likely that they are not being provided in the expected format. The resolution may involve any of the following:
Change the data type associated with this value at source (if you have the option to do so).
Add a transform function immediately before, which changes to the data to the required type. For example, cast a string to a number or a number to a string.
Use a different transform function (if applicable).
Please contact support for assistance, if needed.
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.11.0
13th February 2024
Patchworks dashboard (frontend)
1.8.0
13th February 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-1562
CPT-1245
CPT-1562
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.10.1
25th January 2024
Patchworks dashboard (frontend)
1.6.10
25th January 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-1446
CPT-922
CPT-1964
CPT-1575
CPT-2073
CPT-1945
CPT-1852
CPT-1851
CPT-1473
CPT-1449
CPT-1411
CPT-2076
CPT-1194
1.21.0
27th June 2024 @ 10.30
1.15.1
27th June 2024 @ 10.30
RabbitMQ Laravel Horizon has been removed from the Patchworks tech stack. Going forward, Supervisord runs RabbitMQ consumers.
There are no functional changes for Patchworks users however, we anticipate that this change will bring improved efficiency, with greater insight into jobs, and better issue handling.
CPT-2998
Route shape - route names Fixed issue where the route name was not retained if entered immediately prior to defining required filters for the route (after saving a filter, the route name reverted to the default setting). Route shape
CPT-2979
1.19.0
5th June 2024 @ 8am
1.14.2
5th June 2024 @ 8am
Has warnings indicator in run logs
Run logs now include a Has warnings column. If a process flow run succeeds with warnings (for example, if data of the wrong type is passed into a transform function in the map shape), a warning icon is displayed in this column.
If required, the Has warnings column can be filtered so only runs with warnings are displayed.
Run logs & queue
CPT-2701
Flow control shape - single items
When configuring a flow control shape, a new Do not wrap single records in an array option is available. Use this if you are creating payloads with a batch size of 1, and you want the output to be this:
...rather than this:
CPT-1153
Run process flow shape - variables
When using the Run process flow shape to call one process from another, it's now possible to override flow variables with meta or flow variables defined in the Run process flow shape. When configuring this shape:
payload variable and flow variable syntax can be used.
Any payload provided will override the passed payload from the previous step.
CPT-2610
Improved error reporting for script issues Logging has been extended for cases where a process flow run fails due to a custom script issue, and also if a script fails to deploy. Custom scripts
CPT-2903
Un-deployed scripts not available in map script transforms Fixed issue where only deployed scripts/versions were available for selection when configuring a script transform function for a field mapping (via the map shape).
Now, all scripts/versions are available for selection. If an un-deployed script/version is selected it is deployed, ready for use. Script transform function
CPT-2724
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.13.2
7th March 2024
Patchworks dashboard (frontend)
1.10.0
7th March 2024
New features, updates, and enhancements of note are summarised by product area, below:
Run logs Fixed issue where connector timeouts were not being displayed in process flow run logs. Errors are now reported if a connection cannot be made and the connector times out.
CPT-1963
Silent add to cache failures Fixed issue where run logs may not include enough information to troubleshoot failures on the add to cache step in a process flow. Verbose logging has now been added for this shape.
CPT-2492
Silent FTP connection failures Fixed issue where any errors produced when either failing to connect to an FTP host or trying to perform an invalid operation were not reported to the user - the connection step would fail silently with no details in the logs.
CPT-2486
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
The following prebuilt connectors have been added to the Patchworks marketplace:
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
The following prebuilt connectors have been added to the Patchworks marketplace since our previous release:
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
The following prebuilt connectors have been added to the Patchworks marketplace since our previous release:
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
This hotfix release includes updates summarised by product area, below:
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
The following prebuilt connectors have been added to the Patchworks marketplace:
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
The following prebuilt connectors have been added to the Patchworks marketplace:
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
The following prebuilt connectors have been added to the Patchworks marketplace since our previous release:
Cache lookup transform - fail on miss option
The cache lookup transform function now includes a fail on miss option. When this option is ON, the map shape will fail if the cache lookup transform function is configured to use a cache key that can't be found in the given cache. If this option is OFF, a missing cache key will not cause the map shape to fail.
Referencing a cache in mapping transformations
Script shape - script deployment & retries If a script shape is configured to use a script that needs to be re-deployed, deployment is attempted automatically. In the event that the first attempt fails, it is retried up to three times. After three failed attempts, the step fails and further checks should be made. Script shape
Logs have been enhanced for cases where one of these transforms fails because the specified delimiter is not escaped. Now, an invalid regex statement error message is provided, with details about which transform has failed.
Transform functions
My connectors pagination The my connectors page now includes pagination. If more than 50 connectors are installed, page numbers are now available so you can step through pages. Accessing your connectors
Custom scripts - write flow run logs
To provide more visibility on what a script is doing, you can now add a message to scripts for output to logs (both live and retrospective).
This is achieved using a logs array key in a script, with required output added as strings (maximum of 500 characters).
Custom script messages for logs
The PDO_MYSQL extension has been added for PHP, providing access from PHP to MySQL databases.
Custom scripts
Fixed issue where the field tags list for an endpoint would include duplicate entries if the schema includes duplicate data (i.e. where an actual payload rather than a schema was provided). Field tagging
Response scripts for connector shapes
There may be scenarios where you need to control whether a process flow shape or run should fail/continue based on information returned from a connection request. To achieve this, you can now apply a response script to your connector shape, utilising a new response_code feature to determine the outcome.
Using connector shape response scripts
Append to cache using flow variables When specifying a path for appending data to a cache, it's now possible to include a flow variable. Appending data to a cache
De-dupe shape performance Improved efficiency of the de-dupe shape for faster processing. De-dupe shape
Process flow list sorting Additional sort options have been added to the Manage your flows page so you can now sort by process flow name and enabled at date. Process flows
Custom scripts - PHP 8.2 When creating custom scripts, a PHP 8.2 template is now available for anyone wanting to use 8.2 features. Custom scripts
Custom scripts - Python requests library The requests HTTP library has been added for Python scripts. Custom scripts
Shape documentation
Relevant documentation can now be accessed directly from the settings drawer for any shape - look for the ? icon in the top-right corner.
Process flow shapes
JSON encode transform function The JSON encode transform function has been enhanced so now any data type is supported. JSON encode transform function
Version number appended to cross-reference lookups Fixed an issue where a version number was incorrectly appended to cross-reference lookups when uploaded with an app or process flow. Cross-reference lookups
Script versions in uploaded apps Fixed an issue where scripts included in apps were uploaded with incorrect version numbers. Building & uploading apps
Full stops in URL parameters Fixed an issue where full stops defined in URL parameter keys were passed as underscores. URL parameters
If a process flow runs and an invalid data type is passed into a filter, the run logs will display an error message. This message will include the ‘problem’ data type - for example: The process flow will continue to run however, it’s possible that your filters will not be applied as expected. If identified issues are not resolved, the process flow will fail when Phase 2 of this change is released.
If a process flow runs and an invalid data type is passed into a filter, an error message will be displayed in the run logs and the process flow run will fail - for example:
Event connectors can be accessed using a new Event connectors option in the left-hand navigation menu. Once configured, these connectors can be selected as Event listeners in process flow trigger shapes.
Event connectors (BETA)
Add to cache
Cached data is now stored in Amazon S3.
Add to cache shape
Fixed issue where importing a mapping file which included fields with a null label (i.e. no specified display name) resulted in errors.
Importing & exporting map shape configurations
It's now possible to add a message to be displayed as a dashboard banner for your company profile users. Users with an admin role can add/edit/remove message text (up to 255 characters) via their company profile page.
Adding & managing company profile banners
Event connectors can be accessed using a new Event connectors option in the left-hand navigation menu. Once configured, these connectors can be selected as Event listeners in process flow trigger shapes. Event connectors (BETA)
Add to cache Cached data is now stored in Amazon S3. Add to cache shape
Fixed issue where importing a mapping file which included fields with a null label (i.e. no specified display name) resulted in errors. Importing & exporting map shape configurations
It's now possible to add a message to be displayed as a dashboard banner for your company profile users. Users with an admin role can add/edit/remove message text (up to 255 characters) via their company profile page. Adding & managing company profile banners
When filtering by status, you can now choose to display all retried jobs, all retried and failed jobs, or all retried and succeeded jobs.
Run logs & queues
Map transform function - split string
A new string split transform function can be used to split a string into an array, based on a defined delimiter.
Split string transform function
Map transform function - array join
A new array join transform function can be used to join elements of an array into a string, based on a defined delimiter.
Array join transform function
Map transform function - null to string
A new null to string transform function can be used so if a transform receives null it returns an empty string. If anything other than null is received, no change is made.
Null to string transform function
Map transform function - null to zero
A new null to zero transform function can be used so if a transform receives null it returns a value of 0. If anything other than null is received, no change is made.
Null to zero transform function
Shape spacing on canvas Fixed issue where spacing between shapes in a process flow was too large. Building a process flow
Silent FTP connection failures Fixed issue where any errors produced when either failing to connect to an FTP host or trying to perform an invalid operation were not reported to the user - the connection step would fail silently with no details in the logs. Configuring SFTP connections
Fixed an issue where an app would fail to install due to an anomaly in the original creation process. This was a niche scenario around URL parameters not being cleared for connectors if the connector was changed prior to the app being uploaded to the marketplace.
Fixed an issue where connector information was sometimes missing for connectors that were installed as part of an app. This happened when the app included a process flow utilising a connector that was uploaded to a private marketplace.
Track data shape Use this shape to track data, either from a connector source, or a non-connector source (e.g. Inbound API, webhooks, or manual payloads). Tracked data is available for searching from the Process Flow Overview page.
Payload variables Payload variables now support any incoming data format (for example, JSON or text).
To mitigate connection issues due to rate limiting, you can also define a backoff value (in seconds).
SFTP logging Improved logging information for cases where a specified FTP path cannot be found.
Add to cache shape
The way in which flow run caches are cleared has changed. For process flows that are NOT deployed, the cache is cleared in a 2-hour TTL window. However for deployed process flows, flow run caches are cleared as soon as the process flow completes.
Error logging
Fixed issue where internal error was being reported following the failure of a flow where there was a valid reason for the failure. HTTP errors are now shown at the end of a failed flow run, including the status code and body of the response from the endpoint.
Run logs scroll Fixed issue where auto-scrolling stopped after 1000 logs. The run logs page now continues to scroll after 1000 entries.
Page number pagination method
The limit parameter is now optional.
Fixed issue where selecting a script in the scripts section of the marketplace could cause the page to become unresponsive.
Event connectors can be accessed using a new Event connectors option in the left-hand navigation menu. Once configured, these connectors can be selected as Event listeners in process flow trigger shapes.
Import & export map shape configuration It's now possible to export the the configuration of one map shape (including all field mappings and transformations), and then import that configuration into other map shapes. Exported configurations can be imported into map shapes within the same process flow, within different process flows for the same company profile, and within process flows for any linked company profiles.
Payload metadata size restriction A size restriction of 10240 bytes has been introduced for payload metadata. Exceeding this limit will cause the process flow to fail on the associated step.
The Use queued time option defaults to false on all existing process flows, and defaults to true for all new process flows.
Fixed issue where the updated date for process flow versions was not incremented when changes to the flow were saved.
The SSH2 library is now available when working with PHP scripts.
Scripts not deployed after app install Fixed issue where scripts would sometimes fail to deploy following an app installation.
Run queues We have introduced a run queuing system to ensure that process flows are run equitably across all companies. Now when a job is triggered to run (either manually, or via a trigger/webhook/inbound API call), the run job is placed in a queue for processing. You can view your pending runs from a queue tab within run logs.
Real-time logs
Added flow run id to the start of real-time run logs.
OAuth 2 messaging for failed authentication Connection step run logs have been improved for OAuth 2 authentication failures, so the root cause can be more easily identified.
Specific date filter Added a 'time' section to the specific date filter type, so a time can be selected with the date.
Payload storage Payload storage has moved from Elastic to AWS S3.
Run process flow shape Fixed issue where the 'triggered by' column in run logs was not updated if the process flow was initialised from another flow, via a run process flow shape.
Stopped process flow status
Fixed issue where the status of a 'stopped' process flow run could change from cancelled to success.
Trigger schedule settings Fixed issue where it was possible to set a trigger schedule to less than 10 minutes with a cron expression. The minimum schedule time is now 10 minutes via the UI or cron expressions.
Connector pagination Fixed issue where pagination could fail when the connector rate limit was exceeded. Now a connector shape will fail when a request returns a 429 rate limit message, ensuring that the process flow does not keep trying to paginate when the request can't be successful.
Peoplevox pagination method Fixed issue where it wasn't possible to set the limit for Peoplevox pagination to 10000 (the suggested setting for report data). The limit can now be set to 10000 or less.
Flow control shape Fixed issue where receipt of an empty payload by the flow control shape would cause the process flow to fail. Now an error is logged but the flow continues.
Shape settings drawers Fixed performance issue where opening shape settings drawers was slow.
Run logs
Fixed issue where date is before and date is filters were not working for run logs.
Run logs Fixed issue where UI label indicated that run logs are retained for 8 days however the actual retention period is 7 days.
Set variables shape Fixed shape colour inconsistencies.
Endpoint pagination Fixed issue where setting an endpoint pagination method to none meant that the endpoint could not be saved.
Notification group names Fixed issue where adding a full stop character to a notification group would fail (correctly) but no error message was displayed to users.
Notification group delete modal Fixed modal displayed when a notification group is deleted for UI consistency.
Help links When viewing the contents of an app, a help link is now available. This will link to useful information about this app, including any special instructions/guidance for usage.
Endpoint variables not set for installed apps Fixed issue where connector variables were not being set as expected for installed apps.
Retry failed process flow If a process flow runs and fails, a retry option is now available from the run logs page. Users can click this option to run the flow again.
Route shape filters A manual input option has been added to route shape filters for cases where the schema can't be used for field selection (e.g. for incoming payloads via the API). Meta variables are supported for this input.
Filter shape A manual input option has been added to filters for cases where the schema can't be used for field selection (e.g. for incoming payloads via the API). Meta variables are supported for this input.
Route shape - routing method Fixed issue where the follow all matching routes routing method was not working as expected.
Map shape Fixed issue where slash characters in JSON payloads were being escaped through the map shape, and also in date format transforms.
No payload from first POST connector step
Fixed issue where a connector step would fail when the first shape in a process flow is a POST request and no payload is received in response. To handle this scenario, a new expect empty response option has been added to connector shape settings - this option is only shown for POST requests.
Saving a long process flow Fixed issue where saving a shape near the end of a long process flow would reload the page back to the top, meaning that users needed to scroll back down to continue where they left off.
Filtering boolean variable values Fixed issue where filters weren’t working for manual payloads if the value provided was a boolean variable. A new variable filter type has been added which gives users the option to configure what type the value of the variable is so that it can be properly compared whilst filtering.
Deployed connector count Fixed issue where the number of deployed connectors was not displayed.
Clone endpoints A 'clone' button has been added to the endpoints list, so you can duplicate an existing endpoint and then make required changes to the new version.
Optimisation Endpoint and authentication implementation pages should now be faster to load, with fewer API calls.
Default value for optional URL parameters Fixed issue where a default value was required for optional URL parameters. Optional parameters can now be save without a default value.
User list Fixed pagination issue with multiple pages of users which blocked options to browse users.
Timeout error on connector installation Fixed issue where installing a particularly large connector would occasionally stall and eventually time out.
Connector info for private apps Fixed issue where information for private app connectors was not displayed as expected.
Download all logs for a process flow run It's now possible to download all logs for a given process flow run - access the run logs page, then click the hamburger icon for the required run and choose the download logs option. Logs are downloaded (in CSV format) and a download link is emailed to the email address associated with your Patchworks account.
Import/export cross-reference lookup values It's now possible to export and download a cross-reference lookup table in CSV format, and to import cross-reference lookup values from a CSV file. Exported files are automatically downloaded to your computer, but can also be retrieved (temporarily) from a new General settings > File downloads page.
Import/export de-dupe data It's now possible to export and download a de-dupe data pool in CSV format, and to import de-dupe data from a CSV file. Exported files are automatically downloaded to your computer, but can also be retrieved (temporarily) from a new General settings > File downloads page.
Notification links Where applicable, entries in the notification centre now link to relevant area of the dashboard (for example, an installed process flow notification links to that process flow).
De-dupe shape The de-dupe shape now supports XML payloads, as well as JSON.
Input validation for all transform functions Additional validation has been added to all transform functions, which means that input values must be of the expected type. For example, if a transform function is expecting a number value for its input and a string is provided, validation will fail. This is a phased change - in THIS release, any validation issues will be reported in run logs but this will not cause process flows to fail. In the subsequent phase, validation will be enforced, causing process flows to fail if errors are found. For more information please see the section.
Route shape filter causing route to fail Fixed issue where the next step in a route would fail if a route filter returned a null value.
Empty field mapping names in transforms Fixed issue where it wasn't possible to identify mapping fields when configuring transformations if the user has not entered a display name for the mapped field. Now, if no display name is added, the schema name is displayed when configuring a transform function.
Filter shape settings not displayed Fixed issue where filter settings were not displayed if the the associated schema is changed and becomes invalid.
Custom scripts The bcmath extension is now installed for PHP scripts.
Warning phase If a process flow runs and an invalid input type is passed into a transform function, a warning message will be displayed in the . This message includes the name of the transform function that needs to be checked/updated. Any issues identified in this way will not cause the process flow to fail at this time. However, if identified issues are not resolved, the process flow will fail when Phase 2 of this change is released.
Core subscription tiers We have introduced a new tiered subscription model for the core dashboard. Each tier is associated with allowances for deployed connectors and process flows, and also access to advanced features. For full details please see our page. If you are an existing Core user, you will be migrated to a tier that fits your current plan. If you are placed on a standard tier but have existing process flows using advanced features, those process flows will continue to run as expected. However, you will not be able to make changes to advanced shapes without upgrading your tier. Tier-based allowances for deployed connectors and process flows will apply for all tiers.
If you would like to discuss or change your tier, please .
Roles & permissions
Existing client user and client admin roles have been replaced by new user and manager roles; these are like-for-like replacements in terms of associated permissions.
Additionally, two new roles can now be applied: read-only and administrator . By default, the administrator role is assigned to whoever registers a company. For full details please see our page.
If you are an existing customer, all users associated with your company profile will be set to the manager role, which means they can do most things except create/update other users with the manager role.
If you would like an administrator role to be assigned to any of your user accounts, please .
Advanced shapes As part of our new tiered subscription model, some process flow shapes are now designated 'advanced features'. These are: Add to cache, load from cache, de-dupe, script.
Run process flow shape New shape that enables you to call one process flow from another, forming a chain. By default, the 'calling' process flow passes its current payload to the 'called' process flow however, you also have the option to pass in a manual payload.
Set variables shape New shape that provides the ability to set values for flow variables and/or metadata variables at any point in a flow (previously this had to be achieved via custom scripts).
Round number to decimal places transform A new field mapping transform function is available. This allows you to specify a given number of decimal places to which incoming values should be rounded. Round number transform function
Label character limit When creating a new label (either via label settings or process flow settings), an info message is now displayed to show your character count in relation to the limit of 20.
Unable to display large payload in run logs Fixed issue where payloads larger than 10mb could not be displayed in run logs (either in the canvas, or the run logs page). Now, if a payload is too large for display it is trimmed and a download payload option is available for offline viewing.
Unable to sort cross-reference lookup values Fixed issue where the sort option associated with value ids had no effect.
Deployed flows with no shapes stuck in run mode Fixed issue where a process flow deployed with just a trigger schedule could get stuck in run mode and never complete.
Defined webhooks not displayed on trigger shape Fixed issue where webhooks are added and saved for a trigger shape, but the trigger shape is displayed as empty on the canvas.
Label creation navigation Fixed issue where creating and saving a new label via label settings did not exit back to the label management page.
Unable to specify blank fallback value Fixed issue where a fallback transform function could not be saved if the fallback value was blank.
Extra long process flow name blocks UI access Fixed issue where the presence of an unusually long process name resulted in the user not being able to click into the canvas.
Shape instance & endpoint fields too short Fixed issue where fields for instance and endpoint selection in process flow shapes were shortened.
Blank flow variables not allowed in custom scripts Fixed issue where a custom script would fail when hitting a flow variable where no value is defined. Blank variables are now supported.
Field select UI Fixed issue where the dropdown for payload field selection could be partially hidden.
CPT-35
Today we're excited to launch a suite of features which herald an entirely new way of creating and managing data flows in the Patchworks dashboard:
This suite of features is known as Core.
Process flows are an incredibly powerful tool that you can use to define smart, flexible flows to exchange data between connector instances.
Process flows are built by dragging and dropping shapes onto a canvas, and then configuring those shapes to work in the way you need. Please take a look at our Patchworks quickstart guide to get your bearings, and then navigate to the process flows section of this documentation for more detailed information.
The Patchworks marketplace includes a range of prebuilt connectors for third-party systems, ready for you to install. Having installed a connector, you can create instances of it with your own credentials for the underlying third-party application, and then add these instances as process flow connections.
With Patchworks, you can configure and connect any of our prebuilt connectors in process flows.
But what if we don't have a prebuilt connector for an application that you need to sync? Maybe you have a bespoke, in-house system - or perhaps you want to integrate an application that's completely outside of the eCommerce arena. No problem - the Patchworks connector builder is your new best friend!
If you have technical knowledge of APIs and working with data structures, you can use the connector builder to integrate any application with REST or SOAP APIs.
If you registered for a Patchworks account before July 2023, you'll be familiar with using services to sync data between systems. Process flows include all the functionality of services and much more.
You can continue to do this but if you'd like to try process flows, please contact your Customer Success Manager, or reach out to [email protected].
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.3.6
27th July 2023
1.3.5
27th July 2023
Patchworks dashboard (frontend)
1.3.6
27th July 2023
1.3.5
27th July 2023
The focus for these releases was on bug fixes and backend improvements. There are no updates affecting frontend functionality to note.
1.7.11
16th October 2023
1.5.23
16th October 2023
Core 1.7.11 Dashboard 1.5.23 CPT-744
Core 1.7.11 Dashboard 1.5.23 CPT-926
Core 1.7.11 Dashboard 1.5.23 CPT-977
Core 1.7.11 Dashboard 1.5.23 CPT-977
Core 1.7.11 CPT-1234
Various UX improvements This release includes various improvements and tidy-ups throughout the dashboard.
Core 1.7.11 Dashboard 1.5.23
Core 1.7.11 Dashboard 1.5.23
1.8.4
5th December 2023
1.6.3
5th December 2023
CPT-1576
CPT-1576
CPT-1524
CPT-1524
CPT-905
CPT-1419
CPT-1763
CPT-1440
CPT-1519
CPT-821
CPT-1436
1.7.19
7th November 2023
1.5.3.1
7th November 2023
Core 1.7.19 Dashboard 1.5.3.1 CPT-1186
Core 1.7.19 CPT-1117
Core 1.7.19 Dashboard 1.5.3.1 CPT-1267
Core 1.7.19 Dashboard 1.5.3.1 CPT-970
Core 1.7.19 Dashboard 1.5.3.1 CPT-1393
Core 1.7.19 Dashboard 1.5.3.1 CPT-1309
Core 1.7.19 Dashboard 1.5.3.1 CPT-1066
Core 1.7.19 CPT-971
Core 1.7.19 CPT-1401
Core 1.7.19 Dashboard 1.5.3.1 CPT-1076, 1060
Core 1.7.19 Dashboard 1.5.3.1 CPT-1192
Core 1.7.19 Dashboard 1.5.3.1 CPT-1563
Core 1.7.19 CPT-1522, 1487
Core 1.7.19 CPT-1442
Core 1.7.19 Dashboard 1.5.3.1 CPT-1435
Core 1.7.19 Dashboard 1.5.3.1 CPT-1220
Core 1.7.19 Dashboard 1.5.3.1 CPT-951
Core 1.7.19 CPT-1509, 1522
Core 1.7.19 Dashboard 1.5.3.1 CPT-1485
1.7.10
5th October 2023
1.5.22
5th October 2023
Core 1.7.10 Dashboard 1.5.22 CPT-522
Core 1.7.10 Dashboard 1.5.22 CPT-1073
Core 1.7.10 Dashboard 1.5.22 CPT-1104
Process flow home/overview page now links to run logs Successful and failed process flow stats blocks now link to retrospective run logs.
Core 1.7.10 Dashboard 1.5.22
1.6.8
21st September 2023
1.5.12
21st September 2023
Core 1.6.8 Dashboard 1.5.12 CPT-234
Core 1.6.8 CPT-975
Core 1.6.8 Dashboard 1.5.12 CPT-125
Core 1.6.8 CPT-767
Core 1.6.8 CPT-780
Core 1.6.8 Dashboard 1.5.12 CPT-753
Core 1.6.8 Dashboard 1.5.12 CPT-924
Core 1.6.8 Dashboard 1.5.12 CPT-752
Core 1.6.8 Dashboard 1.5.12 CPT-870
Dashboard 1.5.12 CPT-671
Core 1.6.8 CPT-903 CPT-709
Core 1.6.8 CPT-642
Core 1.6.8 CPT-642
Core 1.6.8 Dashboard 1.5.12 CPT-643
1.8.1
16th November 2023
1.6.0
16th November 2023
Core 1.8.1 Dashboard 1.6.0 CPT-1069
Email failure alert notifications
The email message received when a process
flow run fails now includes seconds in the run
date/time, and the link provided navigates
Core 1.8.1 Dashboard 1.6.0 CPT-1480,1531
Core 1.8.1 Dashboard 1.6.0 CPT-1445
Core 1.8.1 Dashboard 1.6.0 CPT-1469
Null returns from script shape
Fixed issue where the script shape did not allow null returns, causing the subsequent step to fail. A null value is now returned as:
{“payload”:null}
Core 1.8.1 CPT-1441
Core 1.8.1 CPT-1095
Core 1.8.1 CPT-1582
Postman importer (BETA) It's now possible to build a connector from a Postman collection. The Postman importer will attempt to:
create the system/connector
create system variables
create authentication type (token/api-key/basic for now)
create authentication variables
create endpoints (including variables)
Core 1.8.1 Dashboard 1.6.0 CPT-1526
Core 1.8.1 Dashboard 1.6.0 CPT-1526
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.5.1
15th August 2023
Patchworks dashboard (frontend)
1.5.1
15th August 2023
New features, updates, and enhancements of note are summarised by product area, below:
Core 1.5.1 Dashboard 1.5.1 CPT-491
Core 1.5.1 Dashboard 1.5.1 CPT-544
Core 1.5.1 Dashboard 1.5.1 CPT-563
Core 1.5.1 Dashboard 1.5.1 CPT-589
Core 1.5.1 Dashboard 1.5.1 CPT-205
Core 1.5.1 CPT-533
Custom script timeout increased The max timeout for custom scripts has increased to 120 seconds. If a custom script runtime exceeds 120 seconds, a timeout occurs.
CPT-568 Core 1.5.1
The following prebuilt connectors have been added to the Patchworks marketplace:
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.4.4
9th August 2023
Patchworks dashboard (frontend)
1.4.4
9th August 2023
New features, updates, and enhancements of note are summarised by product area, below:
Dashboard 1.3.7 CPT-427
Core 1.4.4 CPT-337
Core 1.4.4 CPT-442
Core 1.4.4 CPT-320
Core 1.4.4 CPT-320
Core 1.4.4 CPT-320
Core 1.4.4 CPT-320
The following prebuilt connectors have been added to the Patchworks marketplace:
Add to cache & load from cache shapes
We've changed the way that the endpoint body format setting of none works.
Previously if body format was set to none and a request including body content was made, this data was not sent in the request body.
Now, body format set to none is ignored if data is found in the body. This handles scenarios where body content isn't typically expected so it's set to none, but later (for example) a custom script is introduced which adds a payload to the body.
Core 1.4.4 CPT-465
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.1.1
11th July 2023
1.1.0
3rd July 2023
Patchworks dashboard (frontend)
1.1.3
12th July 2023
1.1.2
11th July 2023
1.1.1
3rd July 2023
These releases include a raft of snag-fixes and backend updates. New features, updates, and enhancements of note are summarised by product area, below:
New
A Patchworks SFTP connector has been added to the Patchworks marketplace.
Core 1.1.0 TSYS 3835
Enhancement
Dashboard 1.1.1
The following prebuilt connectors have been added to the Patchworks marketplace:
New
Core 1.1.0
Update
Dashboard 1.1.2 CPT-201
New
Core 1.1.0 TSYS-3836
New
Core 1.1.0 CPT-114
Enhancement
Dashboard 1.1.1 TSYS-3852
Enhancement
Core 1.1.0 Dashboard 1.1.1
New
Core 1.1.0 Dashboard 1.1.1
Update
Dashboard 1.1.2 CPT-200
Enhancement
Dashboard 1.1.1
New
Core 1.1.0 Dashboard 1.1.1 TSYS-3884
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.2.0
24th July 2023
Patchworks dashboard (frontend)
1.2.0
24th July 2023
New features, updates, and enhancements of note are summarised by product area, below:
Core 1.2.0 CPT-4
The following prebuilt connectors have been added to the Patchworks marketplace:
Core 1.2.0 CPT-4
Core 1.2.0 CPT-150
Core 1.2.0 CPT-164
Core 1.2.0 CPT-187
Core 1.2.0 CPT-237
Core 1.2.0 CPT-222
N/A
N/A
1.5.4
17th August 2023
Run logs It's now possible to view retrospective logs and payloads for process flows. Logs are available for 72 hours after a process flow starts. Retrospective run logs
Dashboard 1.5.4 CPT-234
Webhook body format options If you choose to customise the body content for a trigger shape webhook, you can now choose your required format (JSON, XML and plain text options are available. Trigger shape (webhook)
Dashboard 1.5.4 CPT-628
1.8.6
14th December 2023
De-dupe shape The de-dupe shape now supports the use of variables to generate dynamic key fields. Any combination of payload, flow and metadata variables can be specified. De-dupe shape
CPT-1940
Re-auth tokens & allow unsuccessful statuses
Fixed issue where connection shapes using an authentication type that requires re-authorisation with a token, would not re-authorise if the allow unsuccessful statuses option is toggled ON.
Connection shape
CPT-1803
Multiple variables in cache key names Fixed issue where specifying more than one value to define a cache key name resulted in no data being cached. Compound variables are now fully supported - any combination of payload, flow and metadata variables can be used to form cache key names. Generating dynamic cache key names with variables
CPT-1645
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.3.4
26th July 2023
1.3.3
26th July 2023
1.3.2
26th July 2023
Patchworks dashboard (frontend)
1.3.2
26th July 2023
The focus for these releases was on mainly bug fixes and backend improvements. New features, updates, and enhancements of note are summarised by product area, below:
Improved layout for the company profile form.
Dashboard 1.3.2 CPT-382
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.3.8
31st July 2023
1.3.7
31st July 2023
Patchworks dashboard (frontend)
1.3.7
31st July 2023
The focus for these releases was on mainly bug fixes and backend improvements. New features, updates, and enhancements of note are summarised by product area, below:
It's now possible to map payloads with a single entity (previously only nested payloads could be mapped).
Core 1.3.8 CPT-420
The payload wrapping option is now available for both pull and push requests. This is to handle cases where the payload from a previous step (e.g. a manual payload) is added to the body of a pull request in the next step.
Dashboard 1.3.7 CPT-427
You can now manage caches via a new cache maintenance page A new 'caches' option is available from the left-hand navigation menu. From here you can view all caches that have been created and select any cache to view/update settings, view the current data, and clear the cache. Cache maintenance
Script marketplace You can now choose to install predefined custom scripts from a marketplace section on the scripts page. These include pre/post request scripts for connectors, and other scripts which we feel may be useful. We will be adding scripts to the marketplace over the coming weeks. The script marketplace
Process flows overview now allows selection of inbound or outbound transactions The tracked transactions chart on the process flows home/overview page now allows you to choose whether to show inbound or outbound transactions. The process flow home page
Process flows overview now links tracked data values to relevant logs Any 'in' and 'out' values displayed in the tracked data panel now link to associated run logs so you can see when the data was processed. The process flow home page
Map shape performance improvements The map shape has been enhanced so processing is now three times faster. The map shape
Pagination This update includes a number of fixes and improvements for pagination methods. Pagination methods
Patchworks marketplace The Patchworks marketplace is now your one-stop stop for all resources that you may want to install to streamline your integrations. You can now browse and install apps, connectors, process flows, and cross-reference lookups. The Patchworks marketplace
Patchworks apps This release introduced apps - install everything you need (connectors, process flows, scripts, etc.) to perform a specific task. The Patchworks marketplace
Forward slashes in cache keys Fixed issue where the forward slash character was not permitted when defining cache keys. Cache shapes
Incorrect mapping structure Fixed issue where mapping a flat array to an indexed array resulted in an incorrect structure. Map shape
Filter logs by process flow It's now possible to filter process flow run logs by process flow. Documentation coming soon
All shapes now support manual input for payload fields All shapes have been updated to include a manual input option wherever the user has the option to select a payload field. Shapes
Empty payloads
Fixed issue passing 'empty' payloads into a shape (which can happen if a null is returned from a script, or if a cache expires). As part of this fix, a new string length option is available on the filter shape.
The filter shape
Custom string transform now supports payload metadata
The custom string field mapping transform now supports payload metadata values using [[meta.unique_key]] syntax.
Referencing flow & meta variables in mapping transformations
Inbound API now supports flow variables When initialising a process flow using the Inbound API, it's now possible to pass in flow variables. Initialising a process flow manually with a payload
Installing a connector includes required scripts If a marketplace connector requires pre/post scripts, these are now included when a user chooses to install the connector (previously these would be added manually). Installing a connector
URL parameters excluded from POST requests Fixed issue where URL parameters were not being passed in POST requests. URL parameters
Stop process flow from run logs You can now stop a running process flow via the run logs page. Retrospective run logs
View failed run reason from run logs Run logs can contain a lot of information so we've added a quick summary for failed runs which shows the reason for a failure. Note that this information is only available for process flow runs that fail after this release. Retrospective run logs
Cache maintenance It's now possible to delete a cache via the cache maintenance page. Cache maintenance
De-dupe shape The de-dupe shape now handles incoming data from a manual payload. The de-dupe shape
Process flow description You can now add a description for a process flow via the process flow settings drawer. Process flow settings
Duplicate process flow now displays copy confirmation When a process flow is duplicated, the copy operation is added to a queue for completion. A confirmation message is now displayed to indicate when a copy is queued and when it is complete. Duplicating a process flow
Process flow overview statistics Statistics tiles now show clear information regarding timeframe and units. The process flow home page
Auto-generated mappings When field mappings are auto generated, mapping rows are only added if a left AND right match is found. The map shape
Multiple SFTP/FTP file transfers When an SFTP/FTP shape is used to transfer a large number of small files, a single authentication is made and then re-used for all files. The SFTP connector
Process flow overview chart The tracked data chart now refers to 'records' instead of 'transactions'. Axis labels have also been updated for greater clarity when there is a large number of data points. The process flow home page
Manual payload size The maximum number of characters allowed in a manual payload is now 100k. The manual payload shape
Process flow description
When adding or editing a process flow, the description field is now optional.
Adding a process flow
Adding connection parameters breaks pagination Fixed issue where adding parameters for an endpoint in a connection shape would break pagination (irrespective of pagination method). The connection shape
Payload meta not being passed to route children Fixed issue where payload metadata (specified in shapes via a [[meta.x]] variable was not being passed down to child shapes from a route. Payload variables & parameters
Process flow overview page not switching inbound/outbound direction correctly Fixed issue where switching to inbound from outbound transaction view or vice versa would show cached transactions for the previous selection. The process flow home page
Process flow run logs timeout Fixed issue where loading larger process flow run logs would fail. Retrospective run logs
Connector modification indicator
When a connector is installed and the setup is subsequently modified by a user, a modified label is displayed on the connector.
Updating a connector
NetSuite limit offset pagination
Fixed issues relating to NetSuite limit offset pagination.
NetSuite (prebuilt connector)
Erroneous failed to deploy message
Fixed issue where a script failed to deploy message was displayed erroneously when editing scripts.
Adding & Testing custom scripts
Duplicate process flow allows process flows to be copied between companies For Patchworks partners/agencies managing multiple companies, the duplicate process flow option now allows process flows to be copied between different company profiles. Duplicating a process flow
Duplicate process flow adds new flow of the same name with an incremental number
Previously, process flows were duplicated with the same name. Now the name is appended with a number which is incremented for each copy. For example: my process flow (1), my process flow (2), etc.
Duplicating a process flow
Additional filter options for run logs In addition to date/time, you can now filter retrospective run logs by run status and trigger type. Retrospective run logs
All-new dashboard home/overview page The dashboard home page has been overhauled - now you have more information at your fingertips to see how your process flows are performing and any actions required. The process flow home page
Tracked data When field tags are applied for the data schema associated with a connector endpoint, you can now choose if the field should be ‘tracked’. About tracked fields
Process flow run failure email notifications You can now associate a notification group with a process flow so recipients receive an email notification in the event that a process flow run fails. Email notifications for process flow run failures
Lookup cache transform now accepts incoming transform value as the cache key When defining a lookup cache transform function you can now use the output from multi-stage transform as the key for the cache lookup. Using output from a transform as the lookup cache key
Allow payload variables to be sourced from metadata It's now possible to target payload metadata in variables. Variables & parameters from payload metadata
Run logs now show incoming payload from a webhook or inbound API call If a process flow receives data from a trigger webhook or an inbound API call, the associated payload can now be viewed in run logs. Retrospective run logs
Real-time run logs now show body content for connection requests & responses The request and response tabs for real-time logs now show associated body content for a connection. Real-time run logs
Retrospective run logs now show the last seven days by default When you access run logs, logs for the last 7 days are shown by default (previously the default showed logs for the last 12 hours). Retrospective run logs
The cache retention period can now be defined when a new cache is created When you drop an add to cache shape into a process flow and choose to create a new flow-level or company-level cache, you can now define when that cached data should expire. The maximum retention period is 7 days. Add to cache shape
The connector marketplace is now accessible from dashboard navigation bar You can now browse the connector marketplace straight from the left-hand navigation bar, using a new 'marketplace' option. The Patchworks marketplace
New transform functions New transform functions include Math, string to number, number to string, boolean to string, and null value. Available transform functions
Improved UI The custom script edit UI has had a facelift, with separate code and test panes. Adding & testing custom scripts
Variables can now be passed into custom scripts for testing When testing a custom script you can now pass in variables (and flow variables) as well as a payload for testing. Adding & testing custom scripts
More information for invalid credentials If credentials cannot be validated when an instance is added, a more details option is provided so you can view the authentication request and response. Adding an instance
Introducing multi-company support It's now possible to manage multiple, linked companies via a single multi-company profile. Team members can easily switch into linked companies from their own dashboard to complete required tasks. Multi-company profiles
directly to the affected run log. Email notifications for failed process flow runs
Cache maintenance (cache content) UI When you access existing caches and choose to view details for a cache, the cache content panel has been updated. Cache maintenance
Process flow overview tracked data Links have been removed from in/out numbers in the tracked data panel. Process flow home page
Assert payload from route Fixed issue where the assert shape could fail if included in a route shape path. Assert payload shape
Map shape warnings Fixed issue where the map shape showed a configuration warning in error. An error icon is only shown if a process flow is deployed with an un-configured map shape, or if a process flow is duplicated and mapping re-configuration is needed. Map shape
enable the authentication type for all endpoints. Documentation coming soon
New 'text' body content type for endpoints
When adding body content for an endpoint, a new text option can be used.
Connector builder endpoints
Add to cache using payload variables Payload variable syntax is now supported for add to cache shape cache keys, so you can target specific elements of an incoming payload to cache.
Append to cache It's now possible to append data to a cache, rather than overwriting each time an add to cache shape is updated.
Cache transform now handles paginated caches
Customise webhook trigger body You can now customise the status code and body content that gets returned when a webhook trigger is returned.
Duplicate process flows If you want to create a new process flow that's similar to an existing flow, you can duplicate the original and use that as your start point for editing.
Round date field transformation function When mapping dates, you can now round a source date to the start/end of the day before pushing to the target field..
Add to cache & load from cache shapes Use these shapes to add the current payload to a cache, which can be referenced elsewhere in the process flow, or in other process flows. Cached payloads can also be referenced in field transformations.
Flow variables Variables can now be defined at the process flow level and referenced throughout the flow - i.e. add/update variables once and then reference multiple times. Flow variables can also be referenced in custom scripts, and in field transformations.
Custom string field transformation function It's now possible to transform a target field by passing in a custom string. You can specify a static string, or you can reference flow variables / cached data.
Custom dynamic date field transformation function It's now possible to set a target field to a date/time that's based on the current date and time (i.e. the date and time that the process flow runs). You can also define rounding and adjustments.
Custom static date field transformation function It's now possible to set a target field to a given date/time.
Custom number field transformation function It's now possible to set a target field to a given number.
Custom boolean field transformation function It's now possible to set a target field to a true/false value.
When adding a connector instance with an authentication method which contains advanced variables, these are displayed on an advanced section of the instance authentication page.
Process flows can now be initialised with incoming data via the Patchworks API.
The batch shape is renamed as flow control - functionality remains the same.
Cross-reference lookups are now implemented for process flows, and can be applied as field mapping transformations via the .
It is now possible to set connection shape variables and parameters with data from the incoming payload.
When selecting an endpoint for a connection shape, available endpoints are now grouped by entity.
Real-time logs displayed when a process flow runs have been enhanced. Log information is more detailed and new options are available to review requests and responses for each step.
A payload format setting has been added for , , and shapes, so you can set the expected format.
This handles cases where incoming data does not originate from another connection shape, but from an where the format is not necessarily JSON.
When building a new connector, basic details now include a protocol field - current options are HTTP and FTP.
Improved editor for endpoint body raw body data.
A range of pagination methods are now supported for connector endpoints.
In the event of an issue when an instance is added, any error messages displayed are more granular, so it's easier to find and fix the cause of a problem.
The process flow actions bar now includes an option to stop a process flow if it's currently running.
The trigger shape now supports webhooks to trigger a process flow to run.
If a process flow name is less than three characters, it can't be saved and an error message is displayed.
Having added a connection shape with an instance and an endpoint, any shapes added directly after which require an instance and endpoint will inherit these settings.
It's now possible to add pre and post authentication request custom scripts. This handles scenarios where some data manipulation is required before and/or after authentication requests are sent.
Cross-reference lookup rows now accept blank left or right values.
This release has been rescheduled for 14th August 2024.
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
1.25.0
8th August 2024 @ 9am
Patchworks dashboard (frontend)
1.18.0
8th August 2024 @ 9am
Introducing blueprints In this release, we introduce blueprints. Replacing apps, Blueprints are templates for automating data flows between specific systems.
The most notable change is that Blueprints can be purchased directly from the Patchworks website. Once purchased, a blueprint becomes available in your dashboard (via the marketplace) within 24 hours.
In the dashboard marketplace, you'll find that apps are now referred to as blueprints however, you will only see blueprints that your organisation has purchased via the Patchworks website.
CPT-3123
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
1.21.1
3rd July @ 9am
Patchworks dashboard (frontend)
1.15.2
3rd July @ 9am
New features, updates, and enhancements of note are summarised by product area, below:
Company insights A new company insights page provides valuable insights into the performance/efficiency of your process flows. The new page can be accessed directly using the account summary link in the left-hand navigation bar.
At a glance, you can see usage metrics and a score for process flows, connectors and shapes over any given month. Note that analysis is available from the point of this feature release onwards, not retrospectively.
CPT-2633
CPT-2753
CPT-2982
CPT-2632
CPT-2632
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
Patchworks dashboard (frontend)
New features, updates, and enhancements of note are summarised by product area, below:
Linked companies - download option If you manage multiple company profiles in Patchworks, a new download option is available when viewing your list of managed companies. Use this to download a CSV file with summary information for all your linked companies (including subscription tier, last login time, and aggregated process flow score).
Regex filter operator for strings When defining filters in either a or shape for a string, a new regex operator is available, providing greater flexibility for filter definitions. For example, the default behaviour for multiple filters is 'AND', but now you can use regex to utilise OR behaviour.
Run logs page The run logs page has been updated with a new look and new functionality for company insights. This includes a new view logs option which navigates to new-style logs showing performance insights for each flow step, with access to detailed logs.
View logs (classic) If you prefer to work with 'old style' logs, these can still be accessed from the run logs page via a view logs (classic) option.
This page summarises items scheduled for the following release to the Patchworks Production environment:
Patchworks core (backend)
1.20.1
26th June 2024
Patchworks dashboard (frontend)
1.15.1
26th June 2024
New features, updates, and enhancements of note are summarised by product area, below:
This release was postponed - please see 27th June 2024.
RabbitMQ
Laravel Horizon has been removed from the Patchworks tech stack. Going forward, Supervisord runs RabbitMQ consumers.
There are no functional changes for Patchworks users however, we anticipate that this change will bring improved efficiency, with greater insight into jobs, and better issue handling.
CPT-2998
CPT-2979
1.19.1
12th June 2024 @ 8am
1.14.3
12th June 2024 @ 8am
Add custom names to shapes in a process flow It's now possible to specify your own name for any shape that you add to a draft process flow.
To do this, access shape settings and click the 'edit' icon next to the existing name - then update the name and save settings. Note that a shape name cannot exceed 50 characters. Techniques for building process flows
CPT-2910
Cast to boolean transform function
A new other > cast to boolean transform function is available. This transform allows you to define specific overrides for values that are set to true or false.
This new option is particularly useful if string > convert to boolean or number > cast to boolean functions (which adhere to PHP's logic for conversion) don't produce desired results.
Other > cast to boolean transform
CPT-1873
Map shape - wrap payload
The map shape wrap payload has been enhanced - there are now two toggle options which can be set separately or together:
wrap input payload ON. Wraps the incoming payload in an array [ ] for processing within the map shape only.
wrap output payload ON. Wraps the outgoing payload in an array [ ] for onward processing.
CPT-2810
Run queue page improvements The queue page for pending runs has been improved so only key information is displayed. For each pending run you can now see:
Process flow name (hyperlinked)
Trigger
Queued at time
CPT-2886
Flow retry option uses queued time The retry failed process flow option has been enhanced to work better with queues.
When the retry option is used for a failed process flow run, the flow runs immediately, using the current time to calculate any relative date filters and settings defined in the flow.
This enhancement ensures that the the queued at time is assumed as the current time for process flow retries.
Retrying a failed process flow run
CPT-2838
Connector shape - endpoint filters
Fixed issue where connector shape filters may not update as expected if the source/endpoint is changed.
CPT-2668
Route shape - route names
Fixed issue where the route name was not retained if entered immediately prior to defining required filters for the route (after saving a filter, the route name reverted to the default setting).
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.13.6
13th March 2024
Patchworks dashboard (frontend)
1.10.1
13th March 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-2341
CPT-2479
CPT-2114
CPT-2531
CPT-2551
CPT-2513
CPT-2495
CPT-1171
CPT- 1599
CPT- 1765
CPT- 2003
CPT-1583
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.15.0
18th April 2024
Patchworks dashboard (frontend)
1.12.0
18th April 2024
New features, updates, and enhancements of note are summarised by product area, below:
Create app error
CPT-2746
GraphQL cursor pagination method
CPT-2672
Webhook rate limit allowance updates
CPT-2220
De-dupe shape UI
CPT-2767
Error when adding second connector
CPT-2763
Empty route shape UI
CPT-2726
Connector shape - endpoints with variables
CPT-2744
Endpoint body option 'none'
CPT-2748
Endpoint body option 'none'
CPT-1085
Private marketplaces If you manage multiple (linked) companies you can now upload resources to your own private marketplace, for sharing across your linked companies.
Error on App and Process flow Install Fixed issue with app and process flow installation where a conflict could occur where associated connectors already existed.
Shape notes It's now possible to add notes to shapes in a process flow. By default, notes are visible to your team, but can be marked as private if required. Notes are added/edited in a markdown editor, with lots of formatting options (tables, flow diagrams, etc.).
Performance improvements for large flows This update includes performance improvements to help with larger process flows.
Shape sequence at start of process flow Fixed issue where the trigger shape could be pushed down when a new shape was added to the canvas.
Endpoint body UI Fixed UI issue on the endpoint body tab where key/value options were shown for body/raw input. These options are now removed.
Optional variable filter not displayed
Fixed issue where optional parameters for a connector endpoint were not shown in connector shape settings if the parameter is defined as a variable type.
Field mapping display names The display name for field mappings is now optional - a default is no longer set when a field is selected.
Field mapping display names Fixed wrapping issue with long display names for field mappings.
Dynamic date flow variables Fixed issue where dynamic date units were not being retained.
Filter shape hidden when parent route added Fixed issue where adding a parent route shape to an existing filter shape would hide the filter shape.
Notification groups Updated notification group options in line with core UI.
Fixed issue where selecting a process flow to include in an app could cause the page to become unresponsive, in certain circumstances.
A new GraphQL cursor pagination method has been added for use with the .
Rate limit allowances for webhooks now vary by core tier.
Fixed UI issue where editing de-dupe shape settings and changing the entity and data pool values appeared to discard given values.
Fixed issue where adding a second connector to a process flow could result in an error under certain circumstances.
Fixed issue where adding two routes to a route shape and then updating the left route with shapes would cause the entire right side of the canvas to be clickable (rather than just the pending empty shape).
Fixed issue where selecting an endpoint from connector shape settings caused the page to become unresponsive if the given endpoint had associated variables.
Fixed issue where setting the body format to none for an endpoint resulted in an invalid format error.
Fixed issue where setting the body format to none for an endpoint could still result in logs showing that raw body content was passed in. This could happen in cases where an endpoint was previously defined to include raw body content and then subsequently changed to none. Now, when an endpoint is saved with body content set to none, any existing raw body content is cleared.
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.13.1
7th March 2024
Patchworks dashboard (frontend)
1.10.0
7th March 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-2471
CPT-1840
CPT-2383
CPT-2453
CPT-1875
CPT-2247
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.9.0
9th January 2024
Patchworks dashboard (frontend)
1.6.8
9th January 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-2051
CPT-1871
CPT-1898
CPT-1992
CPT-1945
CPT-1110
Auto-complete disabled for confirm delete operation Previously, choosing to delete entities in the dashboard (for example, a connector instance), a 'confirm' popup would be displayed and the user was required to enter the word 'confirm' to complete the operation. Having done this once, this popup would auto-complete for any subsequent delete requests. With this release, the 'confirm' popup no longer auto-completes - the user must type the word 'confirm' to complete the delete operation.
CPT-1556
CPT-1934
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.10.0
18th January 2024
Patchworks dashboard (frontend)
1.6.9
18th January 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-1912
CPT-1545
Per second rate limiting Per second rate limiting is now fully supported with/without pagination for connector endpoints.
CPT-1338
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.9.0 (hotfixes)
12th January 2024
Patchworks dashboard (frontend)
1.6.8 (hotfixes)
12th January 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-1838
CPT-2069
Duplicate connectors from app install Fixed issue where installing a marketplace connector could result in multiple copies of the same connector.
CPT-2067
CPT-1912
CPT-2028
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.8.8
21st December 2023
Patchworks dashboard (frontend)
1.6.6
21st December 2023
New features, updates, and enhancements of note are summarised by product area, below:
CPT-1576
CPT-1576
CPT-1940
CPT-1645
CPT-1817
UI improvements for map shape The map shape UI has been updated to tidy up field alignments and validation.
CPT-746
The following prebuilt connectors have been added to the Patchworks marketplace since our previous release:
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.8.9
4th January 2024
Patchworks dashboard (frontend)
1.6.7
4th January 2024
New features, updates, and enhancements of note are summarised by product area, below:
CPT-1897
CPT-1897
CPT-1993
CPT-1979
Tree component exceeds drawer width Fixed issue where a long tree component (typically displaying a data schema for value selections) would sometimes exceed the drawer. This affected the following shapes: map, flow control, split, de-dupe, together with connector endpoint data path selections.
CPT-35
The following prebuilt connectors have been added to the Patchworks marketplace since our previous release:
Connector shape - expect empty payload A new expect empty payload option has been added for endpoints that call a POST request. When selected, the process flow will continue when no response is received from the request.
Process flow scrolling on mobile Fixed process flow scrolling issue on mobile.
Connector filters in process flow versions Fixed issue where it wasn't possible to view filter settings defined for previously deployed process flows (i.e. flows which were previously deployed but have been replaced with subsequent versions). Now when viewing process flow versions, you can view defined filter values in all version states (DRAFT, INACTIVE and DEPLOYED).
Run process flow shape variables Fixed issue where endpoint variable settings were not retained after the shape was saved.
NetSuite SOAP pagination A new pagination method has been added for NetSuite SOAP pagination.
Audit logs Fixed issue where linking one company to another was not shown in audit logs.
Unable to download apps associated with scripts or cache transforms Fixed issue where apps could not be downloaded if they included a script or cache transform.
Timezone selections for flow variables and date transforms not applied Fixed issue where the selected timezone for a dynamic date flow variable or custom dynamic date field transformations was not being applied.
Webhook trigger only displayed after page refresh Fixed issue where a newly applied webhook trigger was not displayed on the trigger shape until the page was refreshed.
Map shape UI was not handling long endpoint names elegantly The map shape UI has been updated to handle very long endpoint names. Now, if an endpoint name is too long to display, the first part is shown as normal and the the full name can be viewed via a tooltip.
Cross reference lookup sort by ID no working Fixed issue where choosing to sort cross reference lookup values by ID has no effect.
Cross reference lookup edit icon Edit icon added to cross reference lookups For clarity, an edit icon has been added to cross reference lookup entries.
Endpoint name validation Fixed issue where endpoint name validation behaviour was different between adding a new endpoint and updating endpoint details. Name validation is now consistent, wherever required.
Translations Fixed missing translations throughout the dashboard.
Caches not shown in dashboard Fixed an issue where some caches were not shown in the dashboard, but would load correctly into a process flow via the load from cache shape.
Instance creation as part of app installation It's now possible to create instance for app connectors as part of the installation process. A new 'add instance' option is available for all connectors on the view app page - select this option to add your authentication credentials for the associated third-party system. Note that creating instances as part of the app install process is optional - if preferred you can still just install the app and add instances later in the usual way.
Allow empty map shape to be uploaded to app store Fixed issue where a process flow containing an empty map shape could not be uploaded to the apps marketplace.
De-dupe shape validation Fixed issue where it was possible to save a de-dupe shape without specifying a data pool.
Connector re-authentication failure when calls are too frequent Fixed issue where attempting to re-authenticate a connector instance during a process flow run would fail if there were multiple other calls being made.
Patchworks marketplace The Patchworks marketplace is now your one-stop stop for all resources that you may want to install to streamline your integrations. You can now browse and install apps, connectors, process flows, and cross-reference lookups.
Patchworks apps This release introduces apps - install everything you need (connectors, process flows, scripts, etc.) to perform a specific task.
Prebuilt process flows This release introduces prebuilt process flows - a range of template flows which include everything you need (connectors, scripts, etc.) to run the flow.
Variable support for de-dupe shape
You can now define a key field value using any combination of static text, payload, meta and/or flow variables.
Variable support for add to cache shape
You can now define a cache key value using any combination of static text, payload, meta and/or flow variables.
Variable support for fallback transform function
You can now define a fallback value using any combination of static text, payload, meta and/or flow variables.
First & Last word field transforms Fixed issue where first word and last word field transformations were not working correctly.
Format date field transform Fixed issue where converting from Unix timestamp to any other format was not working correctly.
Marketplace - apps Fixed issue with erroneous count of app components in detail view.
Marketplace - apps Fixed issue where choosing to exclude process flows from installing could still result in assets for those flows being installed.
Xero provides cloud-based accounting software for small businesses.
Commerce Layer is an API-first commerce engine that makes it easy to incorporate full eCommerce functionality into your existing tech stack.
Fluent Commerce is a leading order management system which optimises fulfillment and solves inventory visibility issues.
Freshdesk is a cloud-based customer engagement solution for streamlining customer support.
Google BigQuery is a fully managed enterprise data warehouse that helps you manage and analyse your data.
GXO Logistics is a leader in cutting-edge warehousing and distribution - designing, managing, and optimising supply chains and delivering customised, tech-enabled solutions.
Happy Returns (by PayPal) is a software and reverse logistics company that works with online merchants to handle product returns.
Octopus Energy Group is a British renewable energy group specialising in sustainable energy.
OrderWise is an integrated ERP system that connects business functions, enabling customers to take control across all stock and order activity in a single system.
Torque are eCommerce supply chain specialists, offering comprehensive solutions and services to optimise supply chains, from warehouse to doorstep.
Trello is a web-based, kanban-style, list-making application and is developed by Trello Enterprise, a subsidiary of Atlassian.
Clarus WMS is a leading provider of warehouse management systems for businesses.
Google Pub Sub is used for streaming analytics and data integration pipelines to load and distribute data.
RabbitMQ is an open-source message-broker.
Sage is the market leader for integrated accounting, payroll, and payment systems
Sanity.io provides a modern CMS that transforms content into a competitive advantage.
Sitoo is a cloud-based POS and Unified Commerce Platform for global retailers.
Voyado is a customer experience platform helping retailers with marketing automations, loyalty schemes, campaign management, and more.
InPost provides a network of Automated Parcel Machines (APMs) across the UK, allowing customers to send, return, and collect parcels.
InPost provides a network of Automated Parcel Machines (APMs) across the UK, allowing customers to send, return, and collect parcels.
Returnless is an all-in-one returns platform to handle returns faster, lower costs and prevent future returns.
Visual Next is a leading software solutions provider tailored to the apparel, footwear, uniform, sportswear and fashion accessories industry.
Quickbooks is a cloud-based accounting solution.
Tempo project, product, & portfolio management solutions are designed to enhance Jira by helping teams collaborate, plan, budget, track, and work smarter.
.svg?alt=media&token=f3a37103-1d33-40fb-a915-a31952359168)
.svg?alt=media&token=9ae1601b-5623-4cef-8fc4-4604b3d91371)
.svg?alt=media&token=d55c33f1-e55f-49eb-a559-6aac7dc64538)
.svg?alt=media&token=4815143d-36d4-4c35-94c3-50dff40c2922)
.svg?alt=media&token=2d8d5eaa-fa36-47f8-9d49-25986066c861)
Salesforce Commerce Cloud enables businesses to set up eCommerce sites, drive more automation and provide customers with seamless shopping experiences.
The is used to build integrations into existing eCommerce platforms.
is a fully integrated, cloud-based inventory management solution that streamlines stock management across multiple channels.
Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.3.1
25th July 2023
1.3.0
25th July 2023
Patchworks dashboard (frontend)
1.3.1
25th July 2023
1.3.0
25th July 2023
New features, updates, and enhancements of note are summarised by product area, below:
Core 1.3.0 CPT-309
The following prebuilt connectors have been added to the Patchworks marketplace:
This connector requires some additional setup before use. Please see our Descartes Peoplevox documentation for full details.
Dashboard 1.3.0 CPT-342
Dashboard 1.3.0 CPT-353
Dashboard 1.3.0 CPT-190
The information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:
Patchworks core (backend)
1.7.12 - 1.7.18
26th October 2023
Patchworks dashboard (frontend)
1.5.25 - 1.5.30
26th October 2023
New features, updates, and enhancements of note are summarised by product area, below:
Core 1.7.18 CPT-970, CPT-1032, CPT-1102, CPT-1223, CPT-1320, CPT-1403
Dashboard 1.5.30 CPT-1066
Core 1.7.14, 1.7.18 CPT-1031
Core 1.7.18 Dashboard 1.5.30 CPT-1315
Core 1.7.18 CPT-1439
Dashboard 1.5.30 CPT-788
Flow variables in filter shape Fixed issue where flow variables were not referenced correctly in the filter shape.
Core 1.7.18 CPT-1246
Core 1.7.18 CPT-1250
Core 1.7.17 CPT-1406
Dispatching multiple payloads from route shape Fixed issue where payloads from shapes after a route shape were processed in parallel, rather than serially.
Core 1.7.17 CPT-1286
Core 1.7.14 CPT-1314
Core 1.7.11 CPT-1374
NetSuite pagination Fixed issues with URL parameters and ensuring signature is valid for OAuth1.
Core 1.7.12 CPT-1154
Core 1.7.14 CPT-1305
The following prebuilt connectors have been added to the Patchworks marketplace:
Core 1.7.14 CPT-1305
Core 1.7.17 CPT-1376
Core 1.7.17 Dashboard 1.5.28 CPT-1376
General improvements to connector marketplace layout.
When a route shape is added to a process flow, any defined route labels are now displayed on the process flow canvas.
If a process flow shape generates multiple payloads (for example, when the flow control shape is used to batch data), the payloads tab in the logs panel now makes all generated payloads available to view.
Multi-language support has been introduced for the dashboard. Use the language switcher at the top of the page to view the dashboard in English, Spanish, French, or Italian.
De-dupe shape A new de-dupe shape is available for use in process flows.
UI improvements for process flow overview page Text has been added to clarify statistics.
Email notification for failed process flows The email notification received when a process flow run fails has been enhanced with more information, improved styling, and a link to the affected process flow.
Cache maintenance UI improvements The cache maintenance page now displays more specific information for cache keys.
Improved run logs for cache shapes When add to cache and load from cache shapes are processed, logs now reflect which key is updated/loaded.
Run logs now include seconds Process flow run logs now include seconds within time values.
Flow variables in script transforms Fixed issue where flow variables referenced in a mapping transform could not be accessed.
Route paths not duplicated between companies Fixed issue where duplicating a flow with a route shape did not copy child route shapes if duplicating between companies.
Flow control data path Fixed issue where setting the data path to anything other than root level was not handled properly.
Cache maintenance keys Fixed issue where cache keys were not updating in cache maintenance.
Variables in pre-auth scripts Fixed issue where script updates to variables could not be saved, causing an error when the pre-auth script ran while attempting to add an instance.
Variables in pre-auth scripts Fixed issue where script updates to variables could not be saved, causing an error when the pre-auth script ran while attempting to add an instance.
Inbound API version ID now displayed in process flow settings It's now possible to obtain the id for a process flow version directly from the versions panel in process flow settings.
Inbound API version ID Fixed issue where initialising a process flow with the inbound API did not consider the version id.
