2022 10 10 release notes (dashboard)
Last updated
Last updated
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:
| Status | Summary |
|---|---|
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. |
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.
| Push to other systems | Pull from other systems |
|---|---|
Fulfillments | Orders |
| Affected feature | Summary | Patchworks # |
|---|---|---|
Password validation | Password validation was not working as expected. This is now fixed and the following rules apply:
| TSYS-1794, 1795 |
Dropdown behaviour | In some circumstances, dropdown lists were not behaving correctly. | TSYS-2173 |
A daily 'sync failure' email can now be sent to defined recipients for example:
