5.1.0 September 29, 2025
Will be released on September 29.
Features/Improvements
Ability to fix grammar and revise content using AI in Support Ticket replies
Test API in Beta Systems is made more user friendly with the ability to test with params and url arguments.
Users can seamlessly switch between any system versions. Previously, only one level upgrade or downgrade was supported.
In API Call Duration Analysis Section of Logs Page, System Name has been added along with usage count and average time for new synchronizations.
Version management in beta systems has been improved, allowing users to delete entire systems, remove specific versions, or mark versions as deprecated
Ability to use authentication tokens in the request body of API Call has been added.
3 New Beta Public Systems (EvolutionX, BigCommerce and Federal Inland Revenue Service) are added.
Support for Electronic Data Interchange(EDI) systems to receive and transfer EDI data is coming soon.
Minor Improvements & Bug Fixes
Multiple Documents can now be uploaded in Project Documents and in Support Tickets
Design improvements are made in dynamic payload section of dynamic workflow, in collaborators of support tickets and in System Builder
To avoid conflicts, system names are now required to be unique across all old and new beta systems.
Many bug fixes and improvements have been made in New Systems. The highlights include:
Automatic caching issue in case of credential form fields is now removed.
Issues around credential expiry and during upgrade or downgrade of public systems with private APIs are now addressed.
In case of upgrade/downgrade, previous version credentials are now retained for 24 hours. After 24 hours, these credentials will expire and be permanently deleted. Users can revert to the previous version within 23 hours using the retained credentials.
System Builder can publish OAuth 2.0 and Token Auth systems only after a successful test connection. Builder Credentials can now be used to publish beta systems.
Content-Type is set to application/json by default in all API headers. You can edit this in API common fields under the API Manager section or override it at the API level by adding a new header. Auto-suggestions are provided for common headers like application/json.
For credential input fields marked as Sensitive, values are hidden after the first save and can only be updated, not viewed.
Order of credentials is now based on the last updated timestamp
Last updated
Was this helpful?