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 |
---|---|
Patchworks dashboard (frontend)
Release version | Release date |
---|---|
New features, updates, and enhancements of note are summarised by product area, below:
Type | Summary | Ref # |
---|---|---|
Type | Summary | Ref # |
---|---|---|
Type | Summary | Ref # |
---|---|---|
1.14.0
11th April 2024
1.11.0
11th April 2024
App install failure
CPT-2668
Missing connector information after app install
CPT-2569
CPT-1536
CPT-1322
Connector shape - configurable retries
It's now possible to configure the number of retries (between 0
and 2
) that should be made when attempting to make a connection in a process flow.
CPT-2333
CPT-2702
CPT-2370
CPT-2511
CPT-2440
CPT-2452
Fixed an issue where an app would fail to install due to an anomaly in the original creation process. This was a niche scenario around URL parameters not being cleared for connectors if the connector was changed prior to the app being uploaded to the marketplace. The Patchworks marketplace
Fixed an issue where connector information was sometimes missing for connectors that were installed as part of an app. This happened when the app included a process flow utilising a connector that was uploaded to a private marketplace. The Patchworks marketplace
Track data shape Use this shape to track data, either from a connector source, or a non-connector source (e.g. Inbound API, webhooks, or manual payloads). Tracked data is available for searching from the Process Flow Overview page. Track data shape
Payload variables Payload variables now support any incoming data format (for example, JSON or text). Payload variables
To mitigate connection issues due to rate limiting, you can also define a backoff
value (in seconds).
The connector shape
SFTP logging Improved logging information for cases where a specified FTP path cannot be found. SFTP connections
Add to cache shape
The way in which flow run
caches are cleared has changed. For process flows that are NOT deployed, the cache is cleared in a 2-hour TTL window. However for deployed process flows, flow run
caches are cleared as soon as the process flow completes.
Add to cache shape
Error logging
Fixed issue where internal error
was being reported following the failure of a flow where there was a valid reason for the failure. HTTP errors are now shown at the end of a failed flow run, including the status code and body of the response from the endpoint.
Run logs
Run logs scroll Fixed issue where auto-scrolling stopped after 1000 logs. The run logs page now continues to scroll after 1000 entries. Run logs
Page number pagination method
The limit
parameter is now optional.
Page number parameter pagination