v2.22.4 (Summer '23)

asperato release package name changes in our bid to make our upgrade process as seamless as possible for customers, we have changed our package release naming convention all releases going forwards will be numbered in the format year 01 for spring, year 02 for summer and year 03 for winter this asperato summer release is 2023 02 and going forwards winter will be 2023 03 this will make it easier for our customers to understand the time of year the release relates to and the period of time in which is was released in app help & guidance in this release we have implemented the salesforce in app help & guidance feature for our core asperato objects, giving you helpful information on our objects, fields and best practices why this feature is so important in app help & guidance is critical to help us provide users with easy to consume and context specific help directly from within salesforce how it works the various prompts are displayed listed in the org and will be displayed to the user according to the permission set they have for a determined time frame/frequency each prompt will be displayed to the users the prompt timings can be amended by the system administrator according to the training needs of the users we have set this to once a day for 5 days upon initial installation of asperato one but this can be configured to each businesses need's setup configure your org to show in app guidance (setup > userengagement > in app guidance >settings) once you have configured in app help and guidance to be on the prompts listed will be displayed once per day for 5 days after installation reset the metrics of any of the prompts to ensure that users see this prompt again with its updated content if they have previously dismissed or completed it if you need additional help with this see 'monitor in app guidance in lightning experience' https //help salesforce com/s/articleview?id=sf customhelp lex prompt monitor htm\&type=5 for further details additional display of connected user on the asperato set up page we have added the connected user field onto the asperato set up page why this feature is so important the connected user is the user that has performed the connection to the asperato server previously this was not visible from within salesforce and if that user had been subsequently deleted or de activated within the org then it could cause issues, especially within the certinia connector package with the creation of cash entries processed by our scheduled job we recommend that the connected user is an active user within the org if you are upgrading to summer 23 or later versions from previous versions, for the connected user to be shown on the set up page you must first click 'reconnect salesforce' and then enter the connected user's credentials the user will then be shown as in the above screenshot outbound (supplier/vendor) payments custom page enhancements commitment to providing the easiest to use payments offering in the eco system is at the heart of our product philosophy our outbound payments feature is being further enhanced with an improved ui for authorisations how to upgrade to 2023 2 if you are upgrading from versions prior to 2 21, 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 https //payonomy freshdesk com/a/solutions/articles/43000701091 documentation https //payonomy freshdesk com/a/solutions/articles/43000701091 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 //login salesforce com/packaging/installpackage apexp?p0=04t1n000002aedl https //login salesforce com/packaging/installpackage apexp?p0=04t1n000002aedl https //login salesforce com/packaging/installpackage apexp?p0=04t1n000002wsvv 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 ( steps on how to do this outlined in the knowledge article here) 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