> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/release-information/core-release-notes/2023-07-14-release-notes-core.md).

# 2023 07 14 release notes (core)

## Release summary

Information detailed on this page refers to updates included in the following releases to the Patchworks Production environment:

**Patchworks core (backend)**

| Release version | Release date   |
| --------------- | -------------- |
| 1.1.1           | 11th July 2023 |
| 1.1.0           | 3rd July 2023  |

**Patchworks dashboard (frontend)**

| Release version | Release date   |
| --------------- | -------------- |
| 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:

* [Connectors & instances](#connectors-and-instances)
* [Process flows](#process-flows)
* [Connector builder](#connector-builder)
* [General](#general)

## Connectors & instances

<table><thead><tr><th width="188">Type</th><th width="388">Summary</th><th>Version &#x26; Ref #</th></tr></thead><tbody><tr><td>New</td><td>A Patchworks SFTP connector has been added to the Patchworks marketplace.</td><td>Core 1.1.0<br>TSYS 3835</td></tr><tr><td>Enhancement</td><td>When adding a connector instance with an authentication method which contains advanced variables, these are displayed on an <strong>advanced</strong> section of the instance authentication page. <a href="/pages/8b0V4AbjjCtqyMhraqE5"><img src="/files/MexWutUpX0IvLKh7ZgY1" alt="">Adding an instance</a></td><td>Dashboard 1.1.1</td></tr></tbody></table>

### Prebuilt connectors

The following prebuilt connectors have been added to the Patchworks marketplace:

<div><figure><img src="/files/JJb6oQQ819rkYpOFHCLL" alt=""><figcaption><p>BigCommerce</p></figcaption></figure> <figure><img src="/files/Cbs7qNEi11YFVQNWHmIZ" alt=""><figcaption><p>BrightPearl</p></figcaption></figure> <figure><img src="/files/2xk4ijsnzSc6XTuU00KA" alt=""><figcaption><p>CommerceTools</p></figcaption></figure> <figure><img src="/files/4JRLLGwAAQ9NR9DXkNWz" alt=""><figcaption><p>Lightspeed</p></figcaption></figure> <figure><img src="/files/vEqjrGhe0iLbZSn5Z3DC" alt=""><figcaption><p>Linnworks</p></figcaption></figure> <figure><img src="/files/8SZTOkxuTK4UTSUEJ3sp" alt=""><figcaption><p>Lionwheel</p></figcaption></figure> <figure><img src="/files/l6BwBdB6MnCGgptiZ7rl" alt=""><figcaption><p>NetSuite</p></figcaption></figure></div>

<div><figure><img src="/files/SVvrbgOMGum8oXjkPDP9" alt=""><figcaption><p>Ometria</p></figcaption></figure> <figure><img src="/files/cHA2HfirgYmKtA87NE46" alt=""><figcaption><p>SFTP</p></figcaption></figure> <figure><img src="/files/QsHvBzVUGPEsMO9NOmW7" alt=""><figcaption><p>Rebound</p></figcaption></figure> <figure><img src="/files/qGpCrLoKvBZYkry2swFL" alt=""><figcaption><p>Shopify</p></figcaption></figure> <figure><img src="/files/HotkG33qlElaPUDktr40" alt=""><figcaption><p>Shopline</p></figcaption></figure> <figure><img src="/files/wuPagxuetmTH9OrOAGp0" alt=""><figcaption><p>SparkLayer</p></figcaption></figure> <figure><img src="/files/BDPkfn5rRD5J0cDaVOXM" alt=""><figcaption><p>TikTok Shop</p></figcaption></figure></div>

<div align="left"><figure><img src="/files/mKLNyY3LtkVAT0BdpadR" alt="" width="75"><figcaption><p>Twilio</p></figcaption></figure> <figure><img src="/files/efAoGXc2YyvgwPkspJFS" alt="" width="75"><figcaption><p>WooCommerce</p></figcaption></figure></div>

## Process flows

<table><thead><tr><th width="188">Type</th><th width="388">Summary</th><th>Version &#x26; Ref #</th></tr></thead><tbody><tr><td>New</td><td>Process flows can now be initialised with incoming data via the Patchworks API.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/HJrazDrV7Ylp2LlLz1Ie">Inbound API for process flows</a></td><td>Core 1.1.0</td></tr><tr><td>Update</td><td>The <strong>batch</strong> shape is renamed as <strong>flow control</strong> - functionality remains the same.<br><a href="/pages/uNI6ZNhC4NnwLaAhP1yN"><img src="/files/MexWutUpX0IvLKh7ZgY1" alt="">Flow control shape</a></td><td>Dashboard 1.1.2<br>CPT-201</td></tr><tr><td>New</td><td>Cross-reference lookups are now implemented for process flows, and can be applied as field mapping transformations via the <a href="/pages/sDacY10PFWZPapzdTUvr">map shape</a>.<br><a href="/pages/uNI6ZNhC4NnwLaAhP1yN"><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""></a><a href="/pages/8trpSpsBHu5AxTBZNK3d">Cross-reference lookups</a></td><td>Core 1.1.0<br>TSYS-3836</td></tr><tr><td>New</td><td>It is now possible to set connection shape variables and parameters with data from the incoming payload. <img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""> <a href="/pages/HC31VdrWhJMUz0LwmCJx">Setting variables &#x26; parameters from a payload</a></td><td>Core 1.1.0<br>CPT-114</td></tr><tr><td>Enhancement</td><td>When selecting an <strong>endpoint</strong> for a connection shape, available endpoints are now grouped by entity. <img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/ksVeuo8Bz6ah8fn0PpJx">Connection shape</a></td><td>Dashboard 1.1.1<br>TSYS-3852</td></tr><tr><td>Enhancement</td><td>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.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/TNXwUbW0xLxu1LBHW23w">Process flow logs &#x26; payloads</a></td><td>Core 1.1.0<br>Dashboard 1.1.1</td></tr><tr><td>New</td><td><p>A <strong>payload format</strong> setting has been added for <a href="/pages/fQWZMN73bKUIontUN4LA">split</a>, <a href="/pages/7qvE65C5mdtXjrbB4swe">route</a>, and <a href="/pages/W8dQNd0BPMY9SOSg7haK">filter</a> shapes, so you can set the expected format.</p><p>This handles cases where incoming data does not originate from another connection shape, but from an <a href="/pages/HJrazDrV7Ylp2LlLz1Ie">inbound API request</a> where the format is not necessarily JSON.</p></td><td>Core 1.1.0<br>Dashboard 1.1.1</td></tr></tbody></table>

## Connector builder

<table><thead><tr><th width="188">Type</th><th width="388">Summary</th><th>Version &#x26; Ref #</th></tr></thead><tbody><tr><td>Update</td><td>When building a new connector, basic details now include a <strong>protocol</strong> field - current options are <code>HTTP</code> and <code>FTP</code>. <a href="/pages/oUsnYK3hlu3dokVNBSTb"><img src="/files/MexWutUpX0IvLKh7ZgY1" alt="">Connector basic details</a></td><td>Dashboard 1.1.2<br>CPT-200</td></tr><tr><td>Enhancement</td><td>Improved editor for endpoint body raw body data. <a href="/pages/iy0aV6jHyghqeRUAZhoc"><img src="/files/MexWutUpX0IvLKh7ZgY1" alt="">Endpoint options | body</a></td><td>Dashboard 1.1.1</td></tr><tr><td>New</td><td>A range of pagination methods are now supported for connector endpoints.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""><a href="/pages/t9u1O2xBdLFQHBya7sMB">Endpoint options | pagination</a></td><td>Core 1.1.0<br>Dashboard 1.1.1<br>TSYS-3884</td></tr></tbody></table>