v2.19 (Summer '22)

release features default settings for payment page navigation asperato have added the ability for our clients to control where their customers navigate to when using the payment & authorisation pay pages why this feature is so important the end point fields control the redirection of an end customer to specific urls depending on whether the pay page transaction is successful, failed or cancelled these previously had to be set using a flow or apex on each payment or authorisation record which had to be written by an implementation partner or consultant we have made this easier by adding a custom setting for these fields so that each record will default from those if they are set, however each record can be overwritten if required based on your specific business requirements if you are not using these end points, the custom settings can remain unpopulated and the record level fields can also remain unpopulated without causing any issues to your user journey these fields are simply an additional enhancement you may wish to use if you are currently using a custom flow to populate the end point fields at a record level these new custom settings will not affect that you can optionally choose to deactivate your flow and use these instead, however it is not required to do so how it works if you wish to use org defaults for these end point fields, simply navigate to custom settings and set url values in the following settings authorisation cancel authorisation fail authorisation success payment cancel payment fail payment success create your payment or authorisation records as normal in asperato, you’ll see the custom setting value populates on the record in the endpoint fields if you wish to overwrite these at record level then you are able to do tha by simply editing the record level field values set up you will need to add the following fields for the endpoints to either the authorisation or payment page layouts as required if you wish to override them at individual record level success endpoint (asp04 success endpoint long c) fail endpoint (asp04 fail endpoint long c) cancel endpoint (asp04 cancel endpoint long c) ‘add payment method’ button image included on authorisation why this feature is important asking your customers to provide you with a preferred payment method is something you will do time and time again this button makes the customer experience of providing you with card details, or setting up a bank mandate better how it works we have added logic for an out of the box authorisation button which you can use, rather than having to create your own this image (which can be replaced with your own) is displayed on the authorisation record in the field ‘authorisation image’ simply decide how you want to expose this image to your end customers for them to create authorisation details with minimal clicks amending the 'add payment method' button in this release to use your own image, all you need to do is navigate to set up → static resources, upload your own image in here the size of the image is 150 wide and the height will be taken from the image you upload so bear that in mind for correct rendering of any images then go to setup → custom settings → asperato one settings and check the ‘use custom auth image’ checkbox create a custom field on the authorisation object of type 'formula' the formula should look something like this (as an example) if( asp04 ecommerce url c != null, hyperlink("https //" + $setup asp04 asperatoonesettings c asp04 server url c + "/pmweb1?pmref=" + asp04 customer id c + "\&aid=" + id + "\&locale=" + text(asp04 language c) +"\&dit=" + asp04 data integrity token c , if( $setup asp04 asperatoonesettings c asp04 use custom pay now image c , image("/resource/paynowimage1", 'auth online', 1,150) , image(" https //live protectedpayments net/donationline/images/auth img png ",'pay online', 1,150)) ), null ) your custom image will now be displayed on the authorisation record in the custom field packaged reports and dashboards we have created some packaged reports within the asperato one app for ease of set up these reports and dashboards are in the asperato reports folder within the standard salesforce reports we have created one dynamic dashboard to give your users some useful information about the asperato payments & collections if you already have existing dynamic dashboards in your org, then please refer to the 'upgrade considerations' section in this document for further information failed collections failed/successful collections card details expiring in the next 3 months failed payments failed/successful payments note these reports will only have data within them if outbound payments is being used within the organisation renamed payment date fields from feedback from our customers, we have now renamed some of our date fields on the payment object to make them more easily understood these are label changes only from ‘process date’ to ‘scheduled process date’ and ‘payment date’ to ‘payment processing date’ api names have stayed the same you do not need to do anything for these changes to take effect on upgrading these field names and updated help text will be changed gocardless customers new features for our gocardless customers we have made the following changes to our asperato one package cancel mandate can now be called with code, rather than via the button we have made changes to the cancel mandate functionality which now allows this process to be called via apex code or a flow why this feature is so important the previous functionality was a button accessed from the authorisation record directly called ‘cancel mandate’ as a result of customer feedback, we have now allowed this feature to be called via apex or a flow so that it can be included in any process automation how it works if you want to use custom code or a flow to call the cancel mandate functionality, you need to use this asp04 cancelmandateprocess cancelmandate('a022z000002fq3aaas'); //replace with actual payment id flexibility on payment retries with success+ success+ with gocardless is an existing supported feature within the asperato one package, however we have made some changes to this to allow individual payment records to be excluded from the intelligent retry process why this feature is so important previously the success+ feature with gocardless worked at org level with no way to exclude certain payments from this process in this release, we have made it possible to exclude these payments, so you can have full control over your retry process how it works once this has been enabled for you, payment records which are created after that will have the ‘success+enabled’ checkbox set to true by default if you wish to exclude certain payment records, then use the edit option to untick the value in success+enabled checkbox setting up success+ you need to enable success+ separately for each currency from gocardless dashboard contact gocardless support for further information on setup and testing of this feature contact asperato support team at support\@asperato com to enable this for you within the asperato one package add the following fields to the page layout success+enabled approx next retry date the 'attempt retry' field is set by the value in the custom setting and could be different to the 'success plus enabled' checkbox the payments will only be retried if the value in the 'success+enabled' field and the 'attempt retry' field are both checked outbound (supplier/vendor) payments asperato have built an outbound payments feature in conjunction with financialforce to automate the payments to third party suppliers/ vendors, or expense payments to staff this functionality drops the reliance on downloading and uploading bank format files, instead making payments directly to your vendors via apis in versions 2 18 1 and 2 19, this is available to financialforce customers using the financialforce and asperato integration package we are looking for early adopters in north america only at this stage to upgrade to this existing new feature and provide feedback we’re also interested in speaking to customers wishing to use this feature outside of financialforce if you are interested in being an early adopter or understanding what this feature entails contact support\@asperato com mailto\ support\@asperato com for financialforce customers go to our getting started guide https //docs google com/document/d/1be4wxvqwtjuqoukatbq0sikqhg1lblgxkrabsbercva/edit# for help and guidance \ bug fixes other minor bug fixes \ how to upgrade to r2 19 upgrade to the latest version 2 19 from appexchange https //appexchange salesforce com/appxlistingdetail?listingid=a0n3a00000ecronuaj or with link here https //login salesforce com/packaging/installpackage apexp?p0=04t1n000001pi4a https //login salesforce com/packaging/installpackage apexp?p0=04t1n000001pi4a other considerations if you are running a package older than 2 16 then refer release notes for all the releases in between to know the configurations for features released in between up to release 2 17 if you have dynamic dashboards in your salesforce org, and you try to install this version you may encounter an error to get around this issue you can either contact salesforce to increase your dynamic dashboard limit, or please deactivate one of your existing dashboards, then when you install asperato one summer 22, you can then choose to de activate our dashboards to reinstate your existing one 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