This page summarises items scheduled for the following release to the Patchworks Core Production environment.
New features, updates, and enhancements of note are summarised by product area, below:
This update includes a potentially breaking change for connectors, which could disrupt some flows if updates are not made. Please check the Breaking changes section below and review your configuration prior to this release.
This release is currently in development - keep an eye on this page for more items!
When configuring connector endpoints which are set to SEND
data via the request body
, behaviour associated with the body format
/ none
setting will change.
Currently, if a connector endpoint includes static body content - or if your API passes payloads into the body - this is passed into the request body even if the body format
option is set to none
.
Following our release on the 16th October 2024, all request body content will be ignored if the body format
option is set to none
.
If you have built your own connectors (using our connector builder) with an API that SENDs incoming payloads in the request body
, you may be affected. Please check all SEND requests for your custom connectors and, where necessary, make the changes detailed below.
If you have installed connectors from the Patchworks marketplace, please check the list below. If you use any endpoints shown here, make the changes detailed below.
Step 1 Log in to the the Patchworks dashboard, send select process flows > connectors & instances:
Step 2 Click the settings icon associated with a connector that you want to update:
Step 3 Click the endpoints tab:
Step 4 Click the name of the endpoint that you want to update:
If the connector includes a lot of endpoints, use CTRL+F to search for a specific part of the endpoint name.
Step 5 Click the body tab from the endpoint setup page:
Step 6 Click in the body format field and select raw from the dropdown list:
Step 7 Set the data type field to JSON, then in the body content field, enter the following:
Step 8 Click the save and go back button at the bottom of the page:
Type | Summary | Ref # |
---|---|---|
Connector | Endpoint |
---|---|
Release version
Release date
v2024-10-16
16th October 2024 @ 9am
BigCommerce
Create a Bulk Pricing Rule
Create an Order For Checkout
Clarus WMS
Delete a Task
Emarsys
Get Contact Data
EVA
AdjustStock
UpdateStock
FTP
FTP PUT
inriver
Delete a Category
Delete a CVL
Klaviyo
Create or Update Client Profile
Add Profile To List
Create List
Mailchimp
Send campaign
Customize signup form
Mapp
Create Contact
Update Contact
Create Related Data Record
Update Related Data Record
NetSuite REST
Restlet
Ometria
Create Order
PagerDuty
Create a webhook subscription
RabbitMQ
Set vhost Definition
Delete Parameter on vhost
Delete a Queue
Delete queue contents
ReturnGo
Add comment to RMA timeline
Set RMA status
Update Webhook details
Create Webhook
Set Shipment Details
Delete Shipment
Returnless
Approve a request
Update a tag
Reveni
Validate Return
Tracking Return
Update Store Preferences
Delete Webhook
Create Webhook
REVIEWS.io
Unsubscribe a user from Review invitation emails
ScaleFusion
Custom properties
Sitoo
Update Order Delivery
The Edge By John Lewis
Acknowledge an order
Create Test Order
Update Stock Availability
Dispatch an order
Veeqo
Update Order Detail
Create An Order
Create a new order note
Update product detail
Create Properties
Create Customer
Update Customer Detail
Create Product
Update Property Detail
Virtualstock
Acknowledge an order
Create Test Order
Update Stock Availability
Xero
Allows you to delete a specified linked transactions billable expenses
Allows you to retrieve a history records of an quote
ZigZag
Create RetailerOrder
CPT-3167
Try/catch shape Our new try/catch shape gives you full control over how process flow exceptions are handled. Errors are caught, removed from the flow and sent down your defined path (for example, you might use the notify shape to alert contacts about issues and/or add exceptions to a cache for follow-up processing). Documentation in progress