25th July 2024 #
Improvements #
Connectors > Authenticating – OAuth could incorrectly use a blank Client Id
In some situations, a Connector using the OAuth AuthorizationCode flow would use a blank Client Id as it appeared to have been provided so it wouldn’t be requested when authenticating the Connector, resulting in it being unauthenticated.
Connectors > Custom Connectors – Custom Object Category Lookup Triggers weren’t saved
If using Custom Object Categories in a Custom Connector, setting Lookup Triggers on the Category weren’t being saved.
Connectors > Custom Object Categories – Lookups displayed error
When copying a Custom Object Category that uses a Lookup to select the item to work with, an error was displayed instead of a dropdown being shown.
15th July 2024 #
Highlights #
Console > Templates/Accounts > Cycles – more export and import options
Through Cyclr’s interface, exports of Templates can now be imported directly into Accounts as new Cycles. Also, Cycles in Accounts can be exported and then imported back into a Console as a new Template or into another Account as a new Cycle.
Cyclr’s API now has 2 new endpoints to allow Cycles to be exported and imported programmatically:
GET /v1.0/cycles/{id}/exportPOST /v1.0/cycles/import
Console > General Settings – new OAuth2 Refresh Token Expired Webhook
Cyclr can now be set to make an HTTP POST Request when an appropriately configured OAuth2.0 Connector reaches its Refresh Token expiry date, enabling you to be alerted when they may need manual intervention to keep them authenticated.
Improvements #
Connectors – Request Body can be sent in GET Requests
Cyclr can now include a Request Body as part of a GET Request. This is available to Connector Methods as well as the http_request() Script function.
Connectors – solution for LAUNCH and OAuth with Chromium-based browsers
Chromium-based web browsers are implementing “storage partitioning” which was impacting OAuth authentication from within Cyclr’s LAUNCH feature.
Console > Templates – resolved error when installing Template using Custom Object Category Method
Corrected some logic which could prevent installation of a Template that used a Method from a Custom Object Category.
Builder > Switch Step – modifying a Switch Step could prevent Builder loading
Previously, if a Switch Step’s Case was deleted in one browser, another user could still link to that Case in their browser which resulted in the Builder encountering an error and not loading the integration. Cyclr will now ignore linking to a Case that’s been removed.
LAUNCH/Marketplaces – Templates with no mappings could fail to install
In certain situations, if a Template didn’t contain any mappings, it could result in an error when installed through LAUNCH or Marketplaces.
Internal – supported SSH Message Authentication Codes updated
Enables our FTP Connector to make SFTP connections to sites hosted by AWS.
1st July 2024 #
Highlights #
Connectors > Script-only Methods themselves don’t count towards Task Usage
Connector Methods defined as Type “Script” no longer automatically count torwards your Monthly Task Usage when used in an integration. If the Script defined on them makes use of the http_request() function, then each call to that function will count towards your Task Usage.
Console > Templates – exporting option to include only mapped or all Custom Fields
When exporting a Template, you can now choose to only include Custom Fields that have been mapped (default behaviour), or to have Cyclr include all Custom Fields of the Connector Methods used by the Template.
Improvements #
Console > Templates – exporting includes all mapped Fields
In certain situations, exporting a Template could previously have missed some mapped Custom Fields, resulting in them not being included in the exported JSON file.
Console > Console Users – new Permission to hide Cyclr API Request Body content
A new Console User Permission of “Cyclr API Requests” has been added. Disabling that for a Console User will prevent them from seeing potentially sensitive Request Body content when viewing calls to the Cyclr API from within the Console at Reports > API Report.
Console > Reports > Connector Report – clearer explanation of Connectivity Tools’ usage
When using Cyclr’s Connectivity Tools, the Console’s Connector Report now displays entries for “Event Triggers” and “Linking” when using those tools, rather than the previous single “System Managed Connector“ entry which encapsulated them.
Builder > Delay Step – correctly showing time set
Delay Steps were always displaying their time as seconds.
Cyclr API > Marketplaces – blank Partner-level OAuth details now ignored when authenticating
In certain situations, blank Partner-level OAuth ClientId and ClientSecret values could be used, ignoring values stored on an Account Connector, resulting in authentication failing when installing an Integration Package through Marketplaces.
Cyclr API > “Cycles” endpoints – performance improvements
Performance improvements when Cyclr obtains data for the ErrorCount and WarningCount properties returned by the GET /v1.0/cycles and GET /v1.0/cycles/{id} endpoints.
Webhooks > Synchronous Responses – Script using return false; resulted in timeout
If you use a Webhook and a Synchronous Response in an integration and have Script on the Webhook Step which might return false; (stopping execution of a Transaction) then Cyclr previously wouldn’t return a Response so the inbound connection would eventually timeout. With this change, if Cyclr reaches a return false; it will now return a Response of “Rejected by script" and close the connection.
Script functions – cyclr_encrypt() now supports SHA512 hashing
The ”cyclr_encrypt()” Script function can now perform SHA512 hashing, along with the existing MD5, SHA1 and SHA256 hashing.
Internal efficiencies around Step Data when processing Transactions
Improved retrieval of Step Data when processing Transactions during periods of very high activity.
Internal improvement to initial Transaction handling
If a Cyclr Scheduler didn’t shutdown cleanly and a Transaction was being retrieved at exactly that point, it could result in it being locked in a Queueing state. Cyclr will now automatically resolve that condition and allow the Transaction to continue.
