# 2022 10 10 release notes (dashboard)

## Introduction <a href="#introduction" id="introduction"></a>

This page summarises release information for the Patchworks release to Production dated: **10th October 2022**.

## New features <a href="#updated-connectors" id="updated-connectors"></a>

### ​Troubleshoot services

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:

<figure><img src="/files/KkNa5ZyEz2D2l7pG4rMm" alt=""><figcaption></figcaption></figure>

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:

<figure><img src="/files/diZ5DeGv7nZYP4KENv6C" alt=""><figcaption></figcaption></figure>

If these options are set, download options are displayed in the service log (which auto-refreshes every 5 seconds) when the run completes.

{% hint style="warning" %}
This tab is only available for **admin users**.
{% endhint %}

{% hint style="info" %}
Please see the [How to run a service manually](broken://pages/6aS8WSYhNiQCMk3z2fhp) page in our product documentation for more information on this feature.
{% endhint %}

### Service notes

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:

<figure><img src="/files/ypZkx29yC8A9gdzBH6BN" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please see the [service notes](#service-notes) page in our product documentation for more information on this feature.
{% endhint %}

### Clone service

If you need to add a service with similar attributes to one that already exists, it's now possible to clone an existing service:

<figure><img src="/files/miC4Gmyu1vCM3JZe10J0" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please see the [cloning an existing service](broken://pages/nYvjUbh3nnBHA6epEpys) page in our product documentation for more information on this feature.
{% endhint %}

### Stop a running sync from the services list

It's now possible to stop a running sync from the service **summary** tab:

<figure><img src="/files/yq2qhlHeutX3CgspbjG8" alt=""><figcaption></figcaption></figure>

### Sync failure email notifications

A daily 'sync failure' email can now be sent to defined recipients for example:\
\
![](/files/tSG8TwW967cbZS7CviLE)

Optionally, these emails can include a preview of the [sync report](broken://pages/ERQiR95xfEQQ0zFnZVxl), 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:

<figure><img src="/files/X2Bu5TZ3dGFQ73sD5bpv" alt=""><figcaption></figcaption></figure>

To receive these emails, recipients must be added to a [notification group](/product-documentation/general-settings/notification-groups.md) and then this group must be added to your [company profile](/product-documentation/company-management/accessing-your-company-profile.md).&#x20;

{% hint style="info" %}
Please see the [sync failure email notifications](broken://pages/cVonS8RM40E3OIuvz8fN) page in our product documentation for more information on this feature.
{% endhint %}

### Connector health check

When working with a connector you can check its current status from the **summary** tab: :

<figure><img src="/files/CpKtt0CXxlvBkh1841mp" alt=""><figcaption></figcaption></figure>

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.         |

{% hint style="info" %}
Please see the [anatomy of a connector](broken://pages/vQPDn4dqvUDt2ga2xzrc) page in our product documentation for more information on this feature.
{% endhint %}

### My company profile

Accessing your company details (including [groups](broken://pages/jZdqx8MTOZe4Ht1XQiGc) and [users](/product-documentation/users-roles-and-permissions/updating-general-details-for-an-existing-user-account.md)) is now easier, via a new **my company profile** option in **settings**:

<figure><img src="/files/1WtFZ9xsghxP6dEZ6dVQ" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please see the [accessing your company profile](/product-documentation/company-management/accessing-your-company-profile.md) page in our product documentation for more information on this feature.
{% endhint %}

### Welcome email messages

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.

## Updated features <a href="#updated-connectors" id="updated-connectors"></a>

### Service list improvements

The **services list** now identifies **sweeper** and **standard** services:

<figure><img src="/files/s8X3chqnjYFgzrmT1JSV" alt=""><figcaption></figcaption></figure>

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:

<figure><img src="/files/hgg6ODbxuaUnyX3ZXeYY" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please see the [services list](broken://pages/vARUqvebMqq9DPJ85wXd) page in our product documentation for more information on this feature.
{% endhint %}

### Service summary tab includes pending & running syncs

**Running** and **pending** entries are now included in the sync list, on service **summary** tabs:

<figure><img src="/files/4wNOt6GXqPss1Mwn8DZE" alt=""><figcaption></figcaption></figure>

### Service logs&#x20;

#### New columns for the service summary sync list

When viewing [summary logs for a service](broken://pages/Mxy4TuUh4yrQagEPmUrk), you will now see **total count** and **processed count** columns - for example:

<figure><img src="/files/PbrW5W9Pk5LFSiEwniMB" alt=""><figcaption></figcaption></figure>

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.&#x20;

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.

#### Enhanced detailed logs

[Detailed service logs](broken://pages/Mxy4TuUh4yrQagEPmUrk) 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:

<figure><img src="/files/JcTbnbkkBZffcV1BeyPi" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please see the [service sync log](broken://pages/Mxy4TuUh4yrQagEPmUrk)s page in our product documentation for more information on this feature.
{% endhint %}

### Field mappings

#### Improved mapping page layout

The service [field mapping page](broken://pages/aFD7HG99aJ7F0brssLwc) is now easier to use, with fields displayed in logical categories based on the **destination** connector - for example:

<figure><img src="/files/Q8FFfPpcJryTcvQ0Zb0B" alt=""><figcaption></figcaption></figure>

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:

<figure><img src="/files/ow0mEDSTCZ42mRkpuHNn" alt=""><figcaption></figcaption></figure>

...when mappings are saved, all new items take their natural place in the list.&#x20;

#### Mapping transforms can now be created without a source field

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:&#x20;

<figure><img src="/files/YzTQvZSmyQLozvm9Q1MF" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please see the [field mappings](broken://pages/E9hoqNhjpHrrERPhLaTi) page in our product documentation for more information on this feature.
{% endhint %}

### Password validation

Password validation now includes checks to determine if the password specified for registration or reset is compromised.&#x20;

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. &#x20;

## New connectors

#### Sitoo

<table><thead><tr><th width="374">Push to other systems</th><th width="374">Pull from other systems</th></tr></thead><tbody><tr><td>Fulfillments</td><td>Orders</td></tr></tbody></table>

## Bug fixes <a href="#updated-connectors" id="updated-connectors"></a>

<table><thead><tr><th width="204">Affected feature</th><th width="407">Summary</th><th>Patchworks #</th></tr></thead><tbody><tr><td>Password validation</td><td><p>Password validation was not working as expected. This is now fixed and the following rules apply:</p><ul><li>A minimum length of 8 characters </li><li>At least 1 lowercase letter (a - z) </li><li>At least 1 uppercase letter (A - Z) </li><li>At least 1 number (0 - 9) </li><li>At least 1 special character (!, $, #, or %)</li></ul></td><td>TSYS-1794, 1795 </td></tr><tr><td>Dropdown behaviour</td><td>In some circumstances, dropdown lists were not behaving correctly.</td><td>TSYS-2173</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/release-information/tapestry-release-notes/2022-10-10-release-notes-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.