v2.21 (Spring '23)

financialforce integration important note this release is not compatible with the financialforce integration package due to the merchant group changes detailed below we have chosen not to list this release on the app exchange due to this reason however our package remains fully security checked and verified in line with salesforce procedures we do not recommend that you upgrade to this if you are a customer using the financialforce/asperato integration until summer 23 if you are a non financialforce customer, and you want to upgrade then please contact our support team and we will be able to advise you with the upgrade merchant group field changes in response to feedback from customers, we have made changes to the merchant group fields on both the authorisation and payment objects why this feature is so important we have made the merchant group a picklist field driven by the values on the setup page this means instead of a free text field, in which users can potentially mistype the merchant group or having to create a validation rule to enforce correct naming convention, the value can be simply selected from the picklist if you change your merchant group name in the setup page, the picklist values are automatically updated as a note, if you do need to change your merchant group names, you will need to update previous records to select the new value as the system will remove the old value from the picklist but will not amend records previously created if you try to process a previously created payment or authorisation with a merchant group name that no longer exists, the payment will error how it works create your merchant groups via the setup tab in the usual way navigate to the authorisation or payment record page by selecting the object > new the merchant group field will be a picklist where you can select the appropriate value adding a new merchant group on the setup page will add a new value to the picklist deleting a merchant group will remove that value from the picklist value set setup if you are installing versions from 2 22 onwards, then you do not need to do anything, the correct field on both objects will be on the page layout for you if you are upgrading from a previous version then navigate to setup > object manager > authorisation and make sure you remove the existing merchant group text field from any page layouts you are using, and add the merchant group picklist field to the page layout instead repeat for the payment object asperato object names now are prefixed with 'asperato' we have renamed our objects to start with 'asperato' so that they are easy to identify when users have multiple salesforce packages installed their api names remain the same for anyone with pre existing code customisations relying on these, but their labels have been changed to make it easier to identify them in the app launcher setup page currency enhancements we have changed our setup page so that it considers the currencies which have been first created on the salesforce org why this feature is so important in order to make in easier to setup and get started with asperato, we have changed the setup page so that it allows you to create merchant groups containing only the currencies which are already created in the salesforce org this will prevent any mistakes downstream when attempting to create payments or authorisations in currencies which do not exist in salesforce outbound (supplier/vendor) payments we have amended the authorisation custom page to allow users to be able to add custom fields using a field set why this feature is so important customers using this version can now add their own custom fields to our page to make it more usable for their own business requirements eg if they have a lookup to the account or contact records for each authorisation then they can add this to our page how it works navigate to setup > object manager > authorisation select field set add your custom field to the field set and select 'save' your field will be reflected on the authorisation custom page how to upgrade to 2 21 as mentioned at the top of this document this release is not compatible with financialforce asperato integration package due to the new merchant group picklist if you wish to upgrade, please contact our support team via support\@asperato com or raise a freshdesk ticket and they will provide you with the installation link 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