v2.23.5 (Winter '23)

update authorisation from salesforce gocardless in response to feedback from our gocardless customers, we have made some changes to our package to allow the update of customer email and billing address fields from salesforce to the customer details within the mandate in gocardless why this feature is so important previously, any updates to the customer email or billing address on an existing authorisation record created a new authorisation in gocardless meaning that within the gocardless portal there were unnecessary mandate records containing old/redundant information which needed to be manually updated by clients now clients can update the email or billing address directly from within salesforce saving duplicated admin effort how it works you must be a gocardless customer to use this feature, it is currently unavailable for any other psp navigate to an existing 'in force' authorisation click 'update authorisation' enter new details in pop up and click save customer details are updated on the authorisation record and also in the mandate within gocardless setup in set up > object manager > asperato authorisation > page layouts > authorisation layout > mobile & lightning actions > drag and drop the 'update authorisation' button onto the page required outbound (supplier/vendor) payments custom page enhancements we have created a custom page for our outbound authorisations to help customers easily enter the correct information needed to create beneficiary records within the psp, airwallex in order to use this enhanced ui, navigate to set up > asperato authorisation > buttons, links, and actions > for edit and new > click 'edit' > replace the lightning experience override with 'lightning component' overrideedit and overridenew respectively > click 'save' permission set changes in this version of asperato one, we have made some changes to how we handle the checking of permissions within our code to allow permission set groups to be used by customers we also made a change to the permission set check for the installing user to have asperato admin permissions this is now removed, and so non admins can install the asperato one package use of asperato paypage in a lwc we made some changes to our codebase to allow our paypage to be easily used within a lwc for further information on this please see this article how to use the paypage a more technical guide https //payonomy freshdesk com/a/solutions/articles/43000694387 defect fix for merchant group being unable to be set as 'default' there was a defect which prevented a merchant group value being set as the default on the object settings we have made a change in 2 23 2 (service pack) which has fixed this issue to set the default value however you must do this by record type for both the asperato authorisation object and the asperato payment object if you are not using outbound payments you only need to do this for inbound record type in set up > object manager > authorisation/payment object > record types > inbound > picklists available for editing > 'merchant group' > edit and set the merchant group you wish to use as your default in the 'default' box at the bottom of the picklist qr code rendering issue we fixed an issue in 2 23 5 which impacted the rendering of the qr code field on both authorisation and payment objects if you use this field, please ensure you are on at least version 2 23 5 to resolve this issue how to upgrade to asperato 2 23 5 if you are upgrading from versions prior to 2 22, then please ensure you follow the steps in the release notes for each version in particular release 2 21 https //payonomy freshdesk com/a/solutions/articles/43000701091 documentation https //payonomy freshdesk com/a/solutions/articles/43000701091 around the merchant group fields this is critical to the smooth running of this version the installation link is here https //test salesforce com/packaging/installpackage apexp?p0=04t1n000002gvfp https //test salesforce com/packaging/installpackage apexp?p0=04t1n000002gvfu to install in production swap the 'test' prefix for 'login' or directly install our package from the app exchange other considerations if you are running a package older than v2 16, please refer to release notes for all the releases in between to ensure all upgrade steps have been completed up to the latest version record type changes in version 2 18 1 we made some changes to introduce two new record types of inbound and outbound to our payment and authorisation objects the current collections functionality is now classed as a record type of inbound you must add the correct record type to any existing asperato user’s profiles upon upgrade to version 2 18 1 and beyond if you are not using outbound payments simply remove the outbound record type from the payment and authorisation objects ( https //payonomy freshdesk com/support/solutions/articles/43000723282 removing outbound record types from payments authorisations https //payonomy freshdesk com/support/solutions/articles/43000723282 removing outbound record types from payments authorisations we recommend following salesforce best practices on app upgrades by installing the package for admins only and in sandbox orgs first before deploying to production the salesforce setting 'enable notifications in lightning experience and salesforce mobile app' needs to be set as follows