2024 12 16 release notes (core)
Last updated
Last updated
This page summarises items scheduled for the following release to the Patchworks Core Production environment.
v2024-12-16
16th December 2024 - starting between 8-9am
New features, updates, and enhancements of note are summarised by product area, below:
​
This release is in the final stages of testing, therefore items detailed below are subject to change. This page will be updated up to the time of release.
CPT-3409
CPT-3253
CPT-3746
CPT-3077
CPT-3478
CPT-3767
CPT-3720
Company creation Fixed an issue where creating a company via the dashboard could occasionally result in the company being partially created in the database.
CPT-3821
Peoplevox uses SOAP authentication with tokens. Typically, this works by authenticating once and sending a valid token in response - this token is included in all subsequent requests until it expires. When the token expires, a 401 (authentication failed) A response is returned, and we will re-authenticate with the next request.
However, Peoplevox doesn't send a 401 response when a token expires - a 200 (success) code is returned and the outcome is included in the response body. So, we need an alternative approach to manage these requests.
This approach is reliable but not optimal in terms of performance.
The script runs every time a connection is attempted and checks the <AuthenticateResponse><AuthenticateResult> section of the SOAP response body to determine success or failure. If authentication has failed, the connector step retries the request and re-authenticates for a new token. If authentication is successful, no re-authentication is required.
In this way, we only re-authenticate requests when necessary.
If you receive or send data from/to Peoplevox in process flows, follow the steps below to implement this enhancement.
Step 2 Apply this script to any process flow connector shapes where Peoplevox is defined as the source or target instance.
Skip option for process flow shapes
To help when designing/testing process flows, a new skip option is available for all process flow shapes (except for ). This is a toggle option at the top of the settings drawer - when toggled on, the associated step is skipped whenever the flow runs.
Documentation in progress
Delete inactive process flow versions
It's now possible to delete inactive versions of a process flow.
Each time a process flow is deployed, the previously deployed version becomes inactive. All inactive versions are retained indefinitely, so if you have lots of flows with multiple iterations, it can be useful to remove older, inactive versions.
Documentation in progress
Postman importer The maximum file size allowed for import has increased from 5MB to 50MB. The Postman importer is now out of BETA.
Flow variables can now be made secret It's now possible to mark string-type flow variables as secret. This means that any value provided for this variable is not displayed anywhere in the system, and is stored securely. Documentation in progress
Company insights - CPU usage For greater clarity, CPU usage bars now display usage figures. Documentation in progress
Relative dates in scripts
Fixed an issue where relative date flow variables used in scripts were reset to -0 seconds.
Peoplevox re-authentication In this release, we've added a feature to enhance performance for Peoplevox re-authentication. This is an 'opt-in' feature - please see the notes for details and implementation requirements.
We currently authenticate every Peoplevox request to ensure that valid tokens are always present. This happens automatically because a is applied for the SOAP authentication method on the Peoplevox connector.
In this release, the presence of a no longer triggers authentication for every request.
A new has been developed, which should be applied to any connector steps in your process flows(s) where Peoplevox is used.
Don't worry if you can't make these changes immediately - process flows with Peoplevox connectors will continue to run normally, though not optimally. For more information, please see .
Step 1 Install the Peoplevox Re-Authentication Response Script from the .
Step 3 Raise a ticket with for the Enhanced Peoplevox Re-Authentication feature to be switched on for your organisation.
