Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
All K8s customers migrated to AWS.
Added support for NetSuite concurrent processing, and more.
Dashboard look & feel refresh.
Introduced Patchworks BI, payload-level custom scripting, and more.
Added the Plytix connector.
Added SparkLayer and Voyado connectors.
Added multiple connectors including TikTok Shop and The Edge by John Lewis.
Introduced new run service feature, service notes, and more.
Introduced field-level custom scripting.
Introduced the Inbound API connector, and more.
This page summarises release information for Patchworks releases to Production between 8th November 2022 and 31st January 2023.
Patchworks BI is a secure, fully hosted and managed Reporting as a Service (RaaS) solution, managed by a dedicated team of BI analysts and data engineers.
Built upon the Microsoft Power BI platform with data hosted in a cloud data warehouse, fast, accurate, meaningful data insights are delivered via a suite of reports covering:
Order management
Inventory management
Customer insights
Digital spend
Engagement
Customers can subscribe to one of three Patchworks BI tiers: standard, professional and enterprise.
Patchworks BI launches at the end of January 2023, whereupon Patchworks customers can upgrade to a BI subscription plan. To read more, please see our product documentation. If you would like a demo, don't hesitate to get in touch with the Patchworks Sales team.
Payload-level custom scripts can be used for cases where you need to manipulate the payload that gets pulled from a source system before it is pushed to your required destination.
For example, you might add a Patchworks service to sync products between two systems, but need to exclude certain SKUs from the sync. If your source system does not support filtering at this level, a payload-level custom script can be defined to perform this operation.
Payload-level scripts are added and tested within the custom scripts area, before being added to required services.
For further information, please see our product documentation.
An audit log is now available for every custom script. If an existing script is changed and saved, those changes are logged and differences can be viewed in an audit log via a new view changes button:
From here, you can choose to restore a previous version.
For further information, please see our product documentation.
A new add connector wizard steps you through the process of adding a connector in a fresh, intuitive way:
For further information, please see our product documentation.
For customers using our Stockr application to align stock levels across multiple Shopify stores, a new Stockr summary is available within the Patchworks dashboard:
Here, you can view transaction totals and associated costs for any given time period. You can also download transactions in CSV format.
For further information, please see our product documentation.
Audit logs have an updated UI and more events are logged - for example:
Events are . Each event is shown with ' in a shaded header bar.
Header bar shading reflects the nature of the event:
Green - added/created
Orange - updated
Red - deleted
Click the associated for an event to view a detailed log:
For further information, please see our product documentation.
The auto-refresh frequency for sync logs has been increased as below:
In certain areas of the Patchworks dashboard (for example, service source/destination settings and mappings), a JSON editor is available.
Typically, these editors are only required by Patchworks administrators however - upon request - users may be assigned a new advanced editor role which provides access to JSON editors throughout the dashboard.
This page summarises release information for the Patchworks release to Production dated: 24th October 2022.
This release is for new connectors only.
| Push to other systems | Pull from other systems |
|---|
| Push to other systems | Pull from other systems |
|---|
| Entity | Pull (as source) | Push (as destination) |
|---|---|---|
| Entity | Pull (as source) | Push (as destination) |
|---|---|---|
| Sync status | Auto-refresh frequency (seconds) |
|---|---|
| Affected feature | Fixed issue with... | Patchworks # |
|---|---|---|
| Push to other systems | Pull from other systems |
|---|
| Push to other systems | Pull from other systems |
|---|
| Push to other systems | Pull from other systems |
|---|
| Push to other systems | Pull from other systems |
|---|
| Push to other systems | Pull from other systems |
|---|
| Push to other systems | Pull from other systems |
|---|
| Push to other systems | Pull from other systems |
|---|
| Push to other systems | Pull from other systems |
|---|
Credit memos
Yes
Yes
Customers
Yes
Yes
Fulfilments
Yes
Yes
Item receipts
Yes
Yes
Orders
Yes
Yes
Products
Yes
Yes
Purchase orders
Yes
-
Returns
Yes
Yes
Stock
Yes
Yes
Transfer orders
Yes
Yes
Purchase orders
Yes
-
Item receipts
-
Yes
Pending
15
Running
05
Complete
No refreshes
Shopify OAuth2 authentication
Shopify OAuth2 authentication.
TSYS-2490
User management
A user account could be created without assigning a role.
TSYS-2527
Inbound API
Sending products with the same SKU to two different target systems.
TSYS-2586
Custom scripts
Save option not available for client admin users
TSYS-2477
Run service manually
Default filters were not applied if 'run service' was triggered without changing any options.
TSYS-2494
Sparklayer connector
Default selection on existing credentials for list options.
TSYS-2517
Lightspeed connector
Unable to add connector.
TSYS-2753, TSYS-2760
Price Lists | N/A |
Prices |
|
Orders | N/A |
Customers |
Returns |
Orders | Fulfilments |
Products | ItemReceipt |
Purchase Orders | Stock |
Returns | Orders |
Transfer Orders | Products |
Returns |
Stock |
TROFulfilment |
Fulfilments | Fulfilments |
Inventory Adjustment | Orders |
Invoices | Products |
Item Receipt | Purchase Orders |
Orders | Stock |
Products | Warehouse Receipts |
Stock |
Fulfilments | Categories |
Orders | Customers |
Refunds | Products |
Stock |
Fulfilments | Orders |
Orders | Products |
Stock |
Fulfilments | Orders |
Prices | Refunds |
Products |
Stock |
Products | N/A |
Asns | Asns |
Orders | Fulfilments |
Products | Products |
Returns |
Orders | Orders |
This page summarises release information for Patchworks releases to Production during March 2023.
When syncing sales orders into NetSuite, options are now available to utilise NetSuite's concurrent processing functionality for improved throughput speed.
This is achieved using new , which are available within service destination settings: /
These options are only displayed when NetSuite is defined as the destination connector and sales orders are the entity being synced.
When these options are set together, multiple, concurrent requests are sent to the NetSuite API and then processed by NetSuite concurrently.
For further information please see our NetSuite concurrency page.
When a service is created, you are immediately directed to the service canvas page. From here, you can see a visual representation of the service flow and access key options:
Options on the run service tab can be used to run an active service manually. Previously, this tab was hidden for inactive services. Now, this tab is always visible however, it is greyed out for inactive services:
For those Patchworks customers who have been migrated to our Kubernetes infrastructure, the filter by unique ID field has been removed from the run service tab. If you need to run a service for specific entity IDs, you should add an IDs filter - for example:
Detailed service logs have been updated to include a custom scripts log section. If a payload-level custom script is associated with a service, activity relating to the script is shown here. For example:
If the service was run manually and you opted to download custom script payload (or any other type of payload) a link to the generated file(s) will be available in this log information. For example:
This link can be accessed using a GET API request, authenticated with a Patchworks token. All download links expire 24 hours after the service run has completed.
For further information please see our viewing logs for custom script activity page.
This page summarises release information for the Patchworks release to Production dated: 26th September 2022.
If you have more complex needs for transforming data and development experience in-house, our new custom scripting feature can be used to write and maintain your own scripts:
Using the integrated editor with IntelliSense, you can code in a choice of languages - currently:
When the script is complete and your code is tested, it can be added as a transform function for field mappings:
Please see the Custom Scripts section of our product documentation for more information.
This page summarises release information for the Patchworks release to Production dated: 10th October 2022.
A new run service tab is available within a service, to help admin users troubleshoot sync queries. Here, you can define a range of settings to run a service manually and work with the results:
You can enter specific ids to be pulled, define filters and set from/to options to determine how the service should run.
Options are available to stop the service run before the push phase and/or to force a push irrespective of any retry limits that may be set. Another really useful setting is the ability to download payloads for the push and pull operations:
If these options are set, download options are displayed in the service log (which auto-refreshes every 5 seconds) when the run completes.
This tab is only available for admin users.
Please see the How to run a service manually page in our product documentation for more information on this feature.
It's now possible to add notes for a service - select the required service, access the settings tab and scroll down to the service notes panel:
Please see the service notes page in our product documentation for more information on this feature.
If you need to add a service with similar attributes to one that already exists, it's now possible to clone an existing service:
Please see the cloning an existing service page in our product documentation for more information on this feature.
It's now possible to stop a running sync from the service summary tab:
Optionally, these emails can include a preview of the sync report, displaying up to 50 failures. Whether or not these emails include a preview of the sync report can be set at the service level, via the alerts tab:
To receive these emails, recipients must be added to a notification group and then this group must be added to your company profile.
Please see the sync failure email notifications page in our product documentation for more information on this feature.
When working with a connector you can check its current status from the summary tab: :
Possible connector statuses are:
Please see the anatomy of a connector page in our product documentation for more information on this feature.
Accessing your company details (including groups and users) is now easier, via a new my company profile option in settings:
Please see the accessing your company profile page in our product documentation for more information on this feature.
Two new 'welcome' emails have been added in this release:
When a new company registration is completed for Patchworks, a welcome email is sent to the person who completed the registration.
When a new user is added to their company's Patchworks system, they will receive a welcome email which includes a link to set their own password.
The services list now identifies sweeper and standard services:
It also includes a separate category for other services - these are custom services that Patchworks set up for clients, typically for cases where clients need to integrate a system that's not available in the dashboard:
Please see the services list page in our product documentation for more information on this feature.
Running and pending entries are now included in the sync list, on service summary tabs:
When viewing summary logs for a service, you will now see total count and processed count columns - for example:
The total count is the number of records retrieved from the source for processing and the processed count is the number of records actually processed by the sync.
These numbers may vary for a number of reasons. For example, if a service is run manually with filters to pull all records from the last hour but a scheduled sync completed ten minutes previously, the manual sync will contain records that have already been processed so they won't be processed again.
Detailed service logs have been improved to show more information, with auto-refresh every five seconds. This means that if you access a log for a service that's running, you have a live view of the sync:
Please see the service sync logs page in our product documentation for more information on this feature.
The service field mapping page is now easier to use, with fields displayed in logical categories based on the destination connector - for example:
When a new row is added, it is shown in a new section at the end of the page, so you can see what's been added at a glance:
...when mappings are saved, all new items take their natural place in the list.
A transform can now be added for a field mapping without the need for a source field to be present. This is useful for cases where a value needs to be passed to a destination system but there is no relationship with a source field. For example:
Please see the field mappings page in our product documentation for more information on this feature.
Password validation now includes checks to determine if the password specified for registration or reset is compromised.
Checks are made using the haveibeenpwned.com service with the k-anonymity model, to determine if a password has been leaked.
If a specified password is found to be compromised, it cannot be used and you will be prompted to try again.
This page summarises release information for the Patchworks release to Production dated: 23rd August 2022.
Our API empowers real-time connectivity, ensuring absolute control and access to any system or data source - you can build against an iPaaS and connect to any system of choice, securely.
You can now create and publish secure API endpoints (completely code-free!) with error handling and guaranteed delivery.
All of this is achieved using an intuitive .
With this, you configure a custom entity to define what information Patchworks should expect to receive in a payload. Once this is done, the connector is ready to use in Patchworks services. Add the Inbound API Connector as a service source, choose a destination connector, define field mappings between the two and enable a secure endpoint for your API requests. Easy!
The services list has been optimised and is now 50x faster to load. Additionally, the services page has a fresh, new look:
Organised by source connector, each service (and associated options) is displayed as a single line.
| Affected feature | Summary | Patchworks # |
|---|---|---|
| Language | Version(s) |
|---|---|
A daily 'sync failure' email can now be sent to defined recipients for example:
| Status | Summary |
|---|---|
| Push to other systems | Pull from other systems |
|---|---|
| Affected feature | Summary | Patchworks # |
|---|---|---|
For further information and instructions, please see our documentation: .
| Push to other systems | Pull from other systems |
|---|
| Connector | Summary | Patchworks Ref |
|---|
| Affected feature | Summary | Patchworks # |
|---|
Company groups
Fixed pagination issue which meant that filter lists did not show a full list of company groups where a large number of company groups is present.
TSYS-3388
Service sync pull count
Fixed issue where the pull count on the service sync summary was erroneously set to zero.
TSYS-3417
Inbound API
Fixed issue where users could not access settings for the Inbound API connector.
TSYS-3435
Field mappings UI
Fixed issue where duplicate mapping elements on the mapping UI could override earlier elements (reversal of logic).
TSYS-3461
Field mapping UI
Reinstated the ability to filter source/destination fields by a given value.
TSYS-3195
Javascript
Node 16
Javascript
Node 17 (Latest Supported)
PHP
7 and 8
Connector Operational
The system can be reached and authenticated with the details provided.
System Unreachable
The URL provided for this connector cannot be reached.
Failed Authentication
Authentication cannot be completed using the details provided.
Fulfillments
Orders
Password validation
Password validation was not working as expected. This is now fixed and the following rules apply:
A minimum length of 8 characters
At least 1 lowercase letter (a - z)
At least 1 uppercase letter (A - Z)
At least 1 number (0 - 9)
At least 1 special character (!, $, #, or %)
TSYS-1794, 1795
Dropdown behaviour
In some circumstances, dropdown lists were not behaving correctly.
TSYS-2173
Customers | Customers |
Orders | Orders |
Unsubscribed contacts | Products |
Prima | Refactoring. | TSYS-2043 |
Inbound API Connector | Under certain circumstances, the name entered for a new Inbound API connector could not be saved. | TSYS-2048 |
Authorisation for connector credentials | Following recent updates to handle multiple authentication types, authorisation for a new connector using existing credentials could fail. This is because existing credentials would not have a setting for the authorisation_type property. A fallback has been added whereby the first related system authorisation type is set if none is found. | TSYS-2012, 2114, 2019 |
Seko API connector | Internal updates for API service and authorisation type. | TSYS-1995 |
Field mappings
Fixed issue where it was not possible to add a transform function to locked rows. Now, source/destination fields are locked but transform functions can be added.
TSYS-2382
Transform editor
Fixed issue where the transform editor was not displaying correctly.
TSYS-2925
Connector status
Fixed issue where connector status incorrectly showed 'authorisation failed' for connectors authorised with oAuth.
TSYS-2941
Field mapping UI
Fixed issue where field mappings without a source but with a transform were displayed with a red border (incorrectly indicating that a source field is required).
TSYS-3036
Advanced editor
Fixed issue where users with the advanced editor role may not be able to save service source/destination changes.
TSYS-3070
Run service
Fixed issue where download custom script payload options were cleared too early.
TSYS-3076
Transform editor
Fixed issue where unable to save a transform which runs a field-level custom script.
TSYS-3130
Custom scripts
Fixed issue where payloads larger than 100kb returned a 500 exception. The maximum size for a script is now 100MB.
TSYS-3144
Run service
Fixed issue where specifying a unique ID could overwrite service filters.
TSYS-3159
Custom scripts
Fixed issue where unable to create a custom script longer than 5000 characters.
TSYS-3167
Service filters
TSYS-3185
New registration
Fixed issue where pressing enter rather continue to confirm password on registration logs into a previous session.
TSYS-3187
Manage users
Fixed user creation error.
TSYS-3191
Run service
Fixed issue where changes made to service destination options were not being applied to the run service tab.
TSYS-3192
Field mapping UI
Reinstated the ability to filter source/destination fields by a given value.
TSYS-3195
Service sync logs
Number of logs returned from database increased from 100 to 1000.
TSYS-3211
Run service filter options
Fixed issue where a specified ID may not persist for the run.
TSYS-3225
Run service
Fixed issue where remaining on the run service page after a run has completed could result in the page continually attempting to retrieve logs.
TSYS-3227
Detailed service logs
Fixed issue where logs displayed an error message if (legitimately) no custom script logs were found.
TSYS-3243
Transform editor
Fixed issue where a string type was not accepted for functions.
TSYS-3300
SFTP connector
Fixed issue where it was not possible to add a service with the Patchworks SFTP connector.
TSYS-3311
Fixed issue for non-K8s customers where targeting a specific ID could overwrite default service filters. The run service tab now includes a merge service filter option - when toggled on, any given ID filter is merged with existing service filters when the service runs.
