v2.15

internal reference title customer facing notes \[md 31] fix xss merchant group issue without validation in salesforce classic so all special char allow in group namesalesforce general bugfix \[md 45] clarify help text on "next payment date" field (payment schedule) help text on "next payment date" fields updated to "the due date of the first or next payment the system will update this date automatically on the final day, it may be updated to a date after the final payment date; this is expected and no future payments will be taken unless the schedule is reinstated " \[md 47] add help link for merchant groups further guidance and help was provided for using merchant groups, with a link added in the package \[md 48] rename "add new connection" button on the "asperato setup" tab, the button labelled "add new connection" has been re labelled "new psp connection" to provide further clarity to its function \[md 53] "delete" links should align on asperato setup page this is a visual enhancement only \[md 55] allow a payment using authorisation against a 'pending' direct debit introduced an option to process direct debit payments for authorisation records with status ‘pending’ this was previously only possible for ‘in force’ authorisations and did not allow payment processing with newly created direct debits \[md 56] show psp status as they're received, not all at once psp connection status is now confirmed in the order that the responses from payment gateways are received connection status is displayed as a green tick or a red cross on asperato setup page \[md 62] need to remove e commerce url from authorisation detail page ecommerce url is no longer displayed by default on the authorisation detail page this can be added to the detail page from the page layout on authorisation object, as required \[md 79] remove development references from remote site settings remote site settings have been corrected to remove development references and make the values less confusing for customers \[md 81] new sandbox creation class a new, optional class has been added to prevent live configuration settings from being copied over to sandboxes when ran, the class will delete any content in the ‘asperato one protected settings' and modify the content of the ‘asperato one settings’ so that the field ‘is running live’ is unchecked and the ‘server url’ is set to ‘test protectedpayments net’ and the field ‘customer id’ is blanked out \[md 120] payment schedule while creating a new record, by default the "active" option should be selected the status value for all new payment schedules is now set to “active“ by default when records are created in classic and lightning \[md 140] add new asperato logo in package new logo has been added to the asperato one package \[md 194] change server option should be available in custom settings "edit page" option has been moved from the salesforce setup dropdown menu (the setup cog) on asperato setup page to the custom settings \[md 1] add help text fields across the package help text fields have been added across the package objects payment, payment schedule, authorisation and refund to make the interface more user friendly \[md 50] enable the use of authentication with asperato details for supported psp types an option to use asperato gateway details has been added for supported psp test connections users can now choose between adding their own payment gateway details or using asperato test account when setting up new connections from asperato setup page \[md 34] validation message does not appear for same connection in one group in classic platform when more than one psp connection was added for the same payment mode from classic ui, the relevant record did not show up and therefore the details were not consistent with the same in lightning a fix has been put in place to address this issue \[md 35] while creating psp connection, for mandatory fields validation message does not appear this fix addresses the issue where it was previously possible to create a new psp connection without filling in some required fields by not selecting them for example, when creating a new connection for stripe with currency, mode, psp fields populated it was possible to complete the process without adding a value to secret api key field \[md 36] in classic platform correct tab does not get highlight while creating/selecting group when selecting or creating merchant groups from asperato setup tab, the selected tab was incorrectly switching to 'home' in the salesforce ui this was a visual defect affecting users in classic mode only \[md 37] scroll payment page modal to top when processing when processing transactions in salesforce by filling in the details on paypage dialog and pressing the pay now button, users could not see the confirmation window with cogs indicating that the request is in progress the issue has been fixed and it is no longer necessary to manually scroll up in order to see the processing screen \[md 38] ensure payment & authorisation currencies match before sending a payment for batch processing payments with a currency that does not match the linked authorisation are no longer sent for batch processing the fix will prevent further issues down the line where the currency is not updated consistently after the payment is complete \[md 42] remove unneeded elements from refund page layout some elements have been removed from the refund page layout to make the content more relevant by default in classic the "clone" button is no longer present, whilst in lightning "new contact", "new opportunity", "new case", "new lead" and "clone" quick actions have been removed \[md 44] add validation rule to ensure every payment & authorisation has a "customer id" field set a validation rule has been added to prevent users from attempting to process transactions without setting up asperato configuration first "there has been an error" was previously displayed when trying to process a payment/authorisation which was not very helpful \[md 46] when users try to refund the amount using "standard permission set", then the error message is not correct users with the asperato standard permission set are no longer presented with an incorrect error message "class lrefundcontrollerextension, object refund c" when attempting to process refunds \[md 49] ensure payment & authorisation currencies match for an initial payment before loading the payment page it is no longer possible to process the initial payment if the payment and linked authorisation records have different currencies this was fixed to prevent inconsistencies in both records after the payment is complete \[md 60] while creating psp connection for direct debit, description does not appear for gocardless the description is now visible on asperato setup page for gocardless after the details have been populated and a new psp connection has been set up \[md 63] difference in classic and lightning platform layout “sharing” button has been added to the payment and authorisation page layout in lightning to make the available options match the classic ui \[md 65] inconsistency in error messages related to refund a fix that addresses the issue with inconsistent error messages that are displayed to the user when attempting to process refunds \[md 69] apex batch job failure a fix that addresses the issue with batch job running user which generates "\[insufficient access on cross reference entity] access to entity 'aggregateresult' denied entity is not api accessible" the error is generated when an invalid user is set to run the batches as part of the postinstall script in the asperato one package \[md 72] decimal places on refund currency field the refund field no longer allows three decimal places for currencies that only support two, i e gbp this issue was affecting records created in lightning \[md 84] unable to refund complete total amount when using partial refund a fix that addresses the partial refunds issue with decimal digits where the total amount does not exceed the original payment amount \[md 87] process authorisation and payment payment issue due to merchant group name special characters can now be used in the merchant group name without encountering the "no payment route is set up for this currency" error when attempting to process payments or authorisations \[md 128] asperato setup screen doesn't work in classic mode a fix that addresses the issue with asperato setup page not being displayed correctly in classic \[md 143] correct mode name does not appear while deleting the psp connection an incorrect payment mode was displayed on the confirmation dialog when attempting to delete a psp connection the issue affected classic users only and has been fixed to no longer show the last payment mode for a particular currency \[md 164] on loading the asperato setup page for psp section correct ui does not appear for some time ui related fix that corrects the psp connection section where an option to set up groups was displayed before the initial configuration was completed \[md 165] classic platform after login correct tab does not get highlight home tab is no longer shown as selected after the initial configuration has been set up from asperato setup tab this was a similar issue to \[md 36] \[md 175] the batch will fail if it tries to process more than 50,000 payments in one go the batch job processing is no longer failing when the total number of records exceeds 50,000 in a single attempt \[md 176] upgrade from lower version to 2 15 or direct install 2 15 setup page for with full admin permission does not appear with proper content the issue has been fixed where asperato setup page was not displayed correctly in winter '21 after full admin permission set is granted and a user attempts to upgrade from an older package version, i e 2 11 or 2 14 \[md 177] upgrade from lower version to 2 15 or directly install 2 15 refund pop up with standard user permission set does not work properly a fix for the payment refund dialog that is not displayed correctly after the package upgrade to 2 15 in salesforce org with winter '21 \[md 199] under authorisation, for payment schedule and payment records should appear in descending order the order of the payments that are linked to an authorisation has been fixed to show the most recent at the top \[md 231] inconsistency of redirection in lightning & classic, when payment is done through using payment using authorisation a ui fix that makes the page redirection more consistent when using the ‘payment using authorisation’ option on an authorisation record at the end of the process a user now remains on the authorisation record page, instead of being redirected to the payment record the process is now identical in classic and lightning