# 2023 10 05 release notes (core)

## Release summary

The 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.7.10          | 5th October 2023 |

**Patchworks dashboard (frontend)**

| Release version | Release date     |
| --------------- | ---------------- |
| 1.5.22          | 5th October 2023 |

New features, updates, and enhancements of note are summarised by product area, below:

* [Process flows](#process-flows)
* [Prebuilt connectors](#prebuilt-connectors)

## Process flows

<table><thead><tr><th>Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Update" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option></select></th><th width="388">Summary</th><th>Version &#x26; Ref #</th></tr></thead><tbody><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Duplicate process flow allows process flows to be copied between companies</strong><br>For Patchworks partners/agencies managing multiple companies, the duplicate process flow option now allows process flows to be copied between different company profiles.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""> <a href="/pages/pYScpgY8PusDda3ju8dF">Duplicating a process flow</a></td><td>Core 1.7.10<br>Dashboard 1.5.22<br>CPT-522</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Duplicate process flow adds new flow of the same name with an incremental number</strong><br>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: <code>my process flow (1)</code>, <code>my process flow (2)</code>, etc.<br><img src="/files/MexWutUpX0IvLKh7ZgY1" alt=""> <a href="/pages/pYScpgY8PusDda3ju8dF">Duplicating a process flow</a></td><td>Core 1.7.10<br>Dashboard 1.5.22<br>CPT-1073</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Additional filter options for run logs</strong><br>In addition to date/time, you can now filter retrospective run logs by run status and trigger type.<br><a href="/pages/RVdm7LuBhWXjhM0Cyuq9"><img src="/files/MexWutUpX0IvLKh7ZgY1" alt="">Retrospective run logs</a></td><td>Core 1.7.10<br>Dashboard 1.5.22<br>CPT-1104</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Process flow home/overview page now links to run logs</strong><br>Successful and failed process flow stats blocks now link to retrospective run logs.</td><td>Core 1.7.10<br>Dashboard 1.5.22<br></td></tr></tbody></table>

## Prebuilt connectors

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

<div align="left"><figure><img src="/files/44vmUSZRGoH7weeTyWeB" alt="" width="75"><figcaption></figcaption></figure> <figure><img src="/files/ZcyvWN3g5hK4CWvRgWxC" alt="" width="75"><figcaption></figcaption></figure> <figure><img src="/files/hSDZWBMFF0CzjWWunGb8" alt="" width="75"><figcaption></figcaption></figure> <figure><img src="/files/MvZVM8K62AY6Hn2nMX5I" alt="" width="75"><figcaption></figcaption></figure> <figure><img src="/files/xzrLQiZJI3dDhF17Rtnl" alt="" width="75"><figcaption></figcaption></figure></div>


---

# 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/core-release-notes/2023-10-05-release-notes-core.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.