Release Notes

SmarterPay for Salesforce is continuously being developed and patched. Release notes shown in this section highlight the major additions, or changes, that would be of interest to our customers.

• 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.