Release “R24-15” #
Available from 14th October 2024
Highlights #
Accounts > Cycles – Search feature added
You can now search Cycles within an Account using the text box added at the top of the page.
Templates > Template Library – Search feature added
You can now search the Template Library using the text box added at the top of the page.
Improvements #
Connectors – consistent behaviour when Methods used as Custom Field Lookups
There were some differences in how a Method would function when used directly and when used as a Custom Field Lookup. Behaviour has been changed to make it consistent.
Connectors – Last Successful Run Date now available to Custom Field Lookup Methods
The last_successful_run_date Script variable is now available for use when a Method is executed as a Custom Field Lookup Method.
Custom Connectors – deleting an in-use Release delayed showing an error
If deleting a Custom Connector with a single Release which is in use, the Release wouldn’t be deleted, but the user wouldn’t immediatley be shown an error until they returned to the Custom Connector. Now the error is displayed immediately.
Cycle Execution – complex mappings with Collection Splitting could result in an error
Previously, when mapping from a Response Field that referenced a property in nested array, Step Errors could occur when Collection Splitting was enabled, but only a single item existed in that array.
Cyclr API – Account Usage endpoint’s “incidents” value corrected
Calling the Cyclr API’s GET v1.0/accounts/{id}/usage endpoint would previously use the most recent recorded value for incidents, rather than the value for the current billing period.
Cyclr API – “Edge” endpoints include Switch Step Case details
Can now retrieve and set Switch Step Cases when working with the Cyclr API’s “Edge” endpoints.
Templates – Builder incorrectly showing “Backwards Incompatible” warning
Previously, the Builder could show the “Backwards Incompatible” warning when no changes had been made to a Template Release.
Templates – installing could result in Custom Categories being combined on a single Connector Method
When installing a Template which has the “Include Unmapped Custom Fields” option enabled and uses Methods from a Custom Method Category, it was possible for the Custom Fields to be merged onto a single Method on the Account Connector, resulting in the Template installation failing.
