Connection pools
For systems where concurrency limits are important (e.g. NetSuite), you can now define connection pools to dispatch simultaneous requests based on a given concurrency limit. Connection pools are configured (via a new navigation menu option) and then assigned to connector instances.
Even if your integrations don't require concurrency limits, this feature can also be useful when testing process flows where lots of data is sent at the same time. With a connection pool, you control how many requests are sent.
Connection pools
A new
production flow toggle option is available in process flow settings. Activating this allows Patchworks to receive alerts which may be analysed to understand trends and for future enhancements. Process flow settingsPayload variables now support XML payloads. The syntax is the same for both JSON and XML - e.g.
[[payload.xyz]]. Payload variablesAll scheduled process flow runs are added to your run queue and then run when a slot becomes available. When jobs are run depends on several factors, including a platform-wide
FLOW_QUEUE_FREQUENCY - this is the frequency at which run jobs are picked from your queue. In this release, the FLOW_QUEUE_FREQUENCY is reduced from 30 seconds to 20 seconds, which means consecutive flow runs are faster. Working with your run queuePreviously, if a connector step received a 401 response (failed authentication), it would re-authenticate, fail the step, and then retry with new authentication details. Now, re-authentication happens without failing the step.
Connector shapeGauge labels have been updated for greater clarity.
Company insights