eSuite v168.0
Below are the product development updates within this release. Should you wish to get a live demonstration of any of the functionality, please contact your Account Manager.
Number of tickets deployed: 27
The eSuite platform has been updated to version v168.0.
This release does not contain any new features, and consists primarily of bug fixes and system optimisation tickets to continually improve both the performance, usability and stability of the platform.
Release Service Pack
- When selecting which roles a report is visible to, additional validation has been added to prompt users to select 'visible to' roles
- Improved performance loading offers with large numbers of vouchers
- Added support to reactivate soft-closed subscriptions when notified by Google Play of the customer's request
- API keys are now locked down from configuration settings to Super Users only
- Ability to move subscription to another service when using additional advanced acquirer configurations
- The error response for Create Account API on version 10.0 has been improved and now prevents users from making concurrent API calls with the same email address, and duplicating accounts - this now displays a 403
- Calling the GET Account Subscription API on REST now successfully returns all relevant account subscription information, and now does not throw a NullReferenceException
- Payment schedules against an account will now successfully reactivate when disabled and then re-enabled
- eSuite HQ UI has been adapted to ensure that 100 records per page always display
- The Virtual Terminal confirmation page now successfully pulls through the currency against the order about to be purchased
- Improved support for patching account details
- When localisation settings are toggled to Japanese, upon loggin in names will now format correctly within eSuite HQ displaying Surname First name
- Additional validation added to eSuite SDK to prevent any unexpected flows triggered upon the user refreshing the page
- Against version 11.3 of REST API, integrators will be able to dictate which currency a card will be authorised in using endpoint POST api/accounts/{accountReference}/payment-details/card
- The GET /api/subscriptions API against version 11+ now returns the correct resource reference code to use in additional requests
- Calling PATCH api/accounts/accountReference/subscriptions/subscriptionReference/move now presents the correct error response when no session is passed, and session is now set as a mandatory parameter
- The /api/accounts/{accountId}/subscriptions/{subscriptionReference}/moves/Confirmed endpoint now returns the correct priceId mapped to the MatrixID, not ServicePriceID