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 | Version & Ref # |
|---|---|---|
The following prebuilt connectors have been added to the Patchworks marketplace:
| Type | Summary | Version & Ref # |
|---|---|---|
1.4.4
9th August 2023
1.4.4
9th August 2023
Dashboard 1.3.7 CPT-427
Core 1.4.4 CPT-337
Core 1.4.4 CPT-442
Core 1.4.4 CPT-320
Core 1.4.4 CPT-320
Core 1.4.4 CPT-320
Core 1.4.4 CPT-320
Add to cache & load from cache shapes
We've changed the way that the endpoint body format setting of none works.
Previously if body format was set to none and a request including body content was made, this data was not sent in the request body.
Now, body format set to none is ignored if data is found in the body. This handles scenarios where body content isn't typically expected so it's set to none, but later (for example) a custom script is introduced which adds a payload to the body.
Core 1.4.4 CPT-465
Add to cache & load from cache shapes Use these shapes to add the current payload to a cache, which can be referenced elsewhere in the process flow, or in other process flows. Cached payloads can also be referenced in field transformations. Cache
Flow variables Variables can now be defined at the process flow level and referenced throughout the flow - i.e. add/update variables once and then reference multiple times. Flow variables can also be referenced in custom scripts, and in field transformations. Flow variables
Custom string field transformation function It's now possible to transform a target field by passing in a custom string. You can specify a static string, or you can reference flow variables / cached data. Custom string transform function Referencing flow variables in mapping transformations Referencing caches in mapping transformations
Custom dynamic date field transformation function It's now possible to set a target field to a date/time that's based on the current date and time (i.e. the date and time that the process flow runs). You can also define rounding and adjustments. Custom dynamic date transform function
Custom static date field transformation function It's now possible to set a target field to a given date/time. Custom static date transform function
Custom number field transformation function It's now possible to set a target field to a given number. Custom number transform function
Custom boolean field transformation function It's now possible to set a target field to a true/false value. Custom boolean transform function
