New Features included in 2.16
- Support for GoCardless Schemes
- PAD and ACH
- Support for GoCardless features
- Success+,
- Cancel mandate from Salesforce
- View mandate from Salesforce
- Withholding email notification from GoCardless platform for payments.
- Access Payout Reference number, against a payment, generated by GC on payment record in SF
Language Support for French
Customization for English language
Added ability to define separate pay-page templates for each merchant group.
How to Upgrade to latest package 2.16
- Upgrade to the latest version 2.16 from AppExchange (from 6 April 2021) or with the package link provided to you.
- After upgrade, 'if you are a GoCardless user' then ask your SF admin to make following changes in Asperato package
Update the Authorisation object
Add Quick actions (In lightning) and buttons (In classic) - View Mandate and Cancel Mandate on page layout.
Add “Submitted for Cancellation” picklist value in Status field.
Update Payment object
Add "Retry in Progress" picklist value in the “Payment Stage” field.
Add fields - Attempt Retry, Suppress PSP Notification on page layout
Update Process Payment Screen (available from Authorisation object) to add
Field - Suppress PSP Notification
RELEASE NOTES
| Internal Reference | Type | Title | Customer facing notes | Documentation links |
| MD-279 | Usability | Correct use Payor and Payee | Corrected terminology to clarify the difference between a Payor and Payee. The update has been applied to the user documentation and product interface, i.e. payment record details. Payor : a person who pays Payee: : one to whom money is or is to be paid | N/A |
| MD-280 | Bug | Classic platform - on Asperato setup page "reconnect salesforce" option should be present | “Reconnect Salesforce” option has been added to the Asperato Setup page for Salesforce Classic UI. Previously customers had to switch to Lightning in order to reconnect the connection/configuration. | N/A |
| MD-429 | New Feature | GoCardless Success+ Feature Support | The package now supports GoCardless Success+ which is inactive by default. Certain steps must be taken to enable this feature. Package Changes
| Open in a new tab Open in a new tab |
| MD-458 | New Feature | Ability to withhold GoCardless messaging on "subscription or instalment" transactions | Allow customers to limit the email notifications that are sent for subscription or instalment payments by optimising the use of GoCardless API. Package Changes
| Open in a new tab Open in a new tab |
| MD-487 | New Feature | GoCardless Support for PAD | Pre-Authorized Debit (PAD) scheme support has been added and is now available via GoCardless. | Open in a new tab |
| MD-498 | New Feature | GoCardless Support for ACH | GoCardless ACH / eCheck support has been added by updating the API, statuses, fields, webhooks etc. | Open in a new tab |
| MD-94 | New Feature | Internationalisation for French | The package UI is now able to run in French on Salesforce Orgs where this language has been configured accordingly. The Translation Workbench compatibility allows the customer to adapt the translation as required. | N/A |
| MD-105 | New Feature | Customization for English language | The Translation Workbench support has been added to allow the customer to adapt the translation for the package UI on Salesforce Orgs that are configured to run in English. | N/A |
| MD-404 | New Feature | Package Changes - Ability to cancel a GoCardless Mandate | The ability to cancel GoCardless mandates from within the package has been added. Previously this was only possible from the GoCardless dashboard. Package Changes
| Open in a new tab |
| MD-430 | New Feature | Different pay-page template configuration for each Merchant Group | Multi-merchant integrations now support different paypage templates for Merchant Groups. Customisation options include paypage logos, colours, styles etc. | Open in a new tab |
| MD-437 | New Feature | Package Changes - Ability to View GoCardless Mandate from Salesforce | GoCardless mandates are now available to view on authorisation records by using the “View Mandate” Quick Action button. Package Changes
| Open in a new tab |
| MD-442 | New Feature | Package Changes - Add a payout reference number on the payment record | Payment records now reflect the payout reference number that is generated by GoCardless when a payment has been completed. Package Changes
| Open in a new tab |
| MD-147 | Usability | Inconsistent behavior of payment and authorisation record, after they get processed individually. Payee details get updated in Payment but not in authorisation | A fix to address the issue where payment and authorisation records were not updated correctly after individual processing. | N/A |
| MD-273 | Bug | Setup page issue on reconnecting salesforce connection with different users | Fixed the issue where Merchant Groups / PSP connections were incorrectly displayed after Salesforce Org was reconnected to Asperato via a different user account. | N/A |
| MD-275 | Bug | In classic. Blank setup page appears on setup configuration with 2 different users | Fixed the issue where Asperato Setup appeared as a blank page in Salesforce Classic after the configuration was initially completed by a different user. | N/A |
| MD-306 | Usability | Immediate data does not get update after processing authorisation and payment using process button | Fixed the issue where the data was not updated immediately on authorisation and payment records after “Process authorisation” and “Process payment” buttons were used. Previously the page had to be refreshed manually in order to see the details for each record. | N/A |
| MD-317 | Bug | Inconsistency behavior of refund in classic and lightning platform | Fixed the issue where the default amount was not correctly displayed for the refund page/pop up on a successful payment in Classic & Lightning. | N/A |
| MD-318 | Bug | In Lightning, payment value does not round off when record gets created through Payment using Authorisation | Fixed the issue in Lightning UI where payment value does not round off correctly when a record gets created through the 'Payment Using Authorisation' button. | N/A |
| MD-329 | Bug | Source does not appear when payment gets failed through batch process | Fixed the issue where Source field is not being populated when a payment that was created through payment schedule (batch process) has failed. | N/A |