Release Notes - 2024
1.15 - Tuesday 25th June 2024
- New: Platform Event has been enabled for API Queue and is now the default behaviour on new package installs. This means that users no longer need access to the API Queue or the Named Credential to work with the SmarterPay package.
- Update: First Collection Amount is no longer required on the Recurrence Schedule Flow for Ongoing Collections. If one is not provided, the value from Amount will be used.
- Update: Recurrence Schedules may no longer be reactivated once set to Inactive.
- Update: Recurrence Schedule Instalments field is now deprecated and replaced with the Schedule Instalments field. This new field is a picklist so reduces the possibility of user mistakes when setting up on the Payment Plan.
- Update: All out-of-the-box flows are now 'Overridable'. This means that the 'New' buttons on records and Utility Bar on the SmarterPay App can be customised.
- Update: Users are now guided to select the correct 'Cancel' status on a Mandate. Previously it was confusing which option to select.
- Fix: Resolved issue where the API Queue could be run in parallel. Additional checks are now made to completely stop this occurring.
- Fix: The API Queue now correctly handles parent and child records within the same batch of callouts. Previously, because the SMPC Id of the parent was unknown the child record callout would fail.
- Fix: Card Payments now work correctly on all Digital Experiences.
- Fix: Multicurrency now works correctly by defaulting all Bacs related objects to GBP.
- Fix: Recurrence Schedule 'Preview' now works correctly taking into account if it using a new or old Mandate.
- Fix: Mandate Flow now applies the selected Originating Bank Account correctly.
- Fix: 'Duplicate Id In List' error that can occur on Webhook processing has now been fixed. This issue would occur when two updates on the same record were being processed at the same time. We now process these webhook events in order correctly.
1.14 - Thursday 09th May 2024
- Fix: 'Type' on the API Queue object is no longer a restricted picklist allowing addons to the API Queue in SmarterPay Extension Packages and subscriber's Salesforce Orgs.
1.13 - Thursday 18th April 2024
- Update: API Queue layout to include all relevant information.
- Fixed: API Queue 'SMPC Id' formula fields are now correctly identifying blank lookups.
1.12 - Wednesday 17th April 2024
- New: Bacs Input Reports added.
- Update: Raw Request and Response now saved to API Queue for easier problem solving.
- Update: Webhook JSON now stored in 'pretty' format for easier problem solving.
1.11 - Thursday 21st March 2024
- New: Named Credentials now included in package, reducing initial configuration time.
- New: API Queue can now be extended to allow additional callouts for SmarterPay Extension Packages or bespoke subscriber requirements.
- Fixed: Card Payments on Experience Communities not reporting result of transaction correctly.
1.10 - Wednesday 21st February 2024
- Update: Enabled Adyen payment gateway for Card Payments.
- Fixed: Issue causing an additional unnecessary callout to SmarterPay Cloud when a Recurrence Schedule is inserted due to blank spaces in Upcoming Payments JSON.
1.9 - Wednesday 07th February 2024
- Recurrence Schedules
- End Date may now be removed from the schedule. Previously clearing this field would result in an error and users were required to set a date far in the future.
- Bank Account
- Enabled field is now defaulted to false to ensure that related records, such as Mandates, may only be created after the bank account is confirmed valid in SmarterPay Cloud.
- Account Number and Sortcode is now emptied on receipt of a webhook if the 'Store Bank Details' setting is switched off.
- Reporting
- Introduced a series of standard reports to help users understand what is currently happening in the SmarterPay application.
- Security/Setup
- 'SmarterPay Setup' tab introduced to allow users, with the SmarterPay Admin permission set, to update Webhook Private Key and API Key Fallback settings. Current values are not visible and may only be updated.