Bookings 1.8.32

Released 20/05/2022

Improvements

• BPAY-1051 - Payment reconciliation has been enabled for the Civica, Worldpay and Capita SCP Multi-Item payment field types. Users making bookings won't notice any difference in the booking process, but in the background additional calls are made to the payment provider portal to confirm the success of the payment, releasing the tickets if the payment is not successful. See the upgrade steps below for important information

Fixes

• BPAY-1044 - Users are no longer presented with an error when they cancel a booking through user requests.
• BPAY-1048 - Ensure the booking reminder email is not sent when a booking has been cancelled by a staff user. A cancelled booking will no longer send any form or reminder emails
• BPAY-1049 - Do not send the reminder email if the time it would have been sent is in the past. Previously, these were sent when the booking was made
• BPAY-1055 - Ensure the main booking form doesn't redirect users to the basket if a plugin has been enabled on an occurrence - it should be the plugin that takes care of the redirect
• BPAY-1061 - Ensure the update occurrence settings form will let an occurrence be updated to allow cancellations by the booker. This previously didn't work if no CTM template existed for "Cancel Booking Success Message"
• BPAY-1065 - Ensure the update occurrence settings form will allow a plugin to be removed from occurrences

Upgrade Steps

BPAY-1051 - Payment reconciliation requires the following steps to be completed once all of the content resources have been installed:

1. Configuration End Points
   • Civica (CIVICA) - config.[environment].BookAndPay.getConfig add the URL of the Query Payments API to the baseUrl property
     config.civicaSettings.settings = [{
    settingsId: "1",
    baseUrl: "https://www.civicaepay.co.uk/MyOrganisationXMLTest",
    callingApplicationId: "GOSSTest"
}]
     The IP address of the iCM site needs to be whitelisted with Civica before the payment API can be used. This is a breaking change
   • World Pay (WORLDPAY)- If payment reconciliation is not already set up, a configuration End Point needs to be created at config.[environment].Worldpay.getConfig with the following:
     function(params, credentials) {
    return {
        credentials: [{
            username: "example",
            password: "example"
        }],
        defaults: {
            username: "example"
        }
    };
}
   • Capita SCP Multi-Item (CAPITA_MULTI)- If payment reconciliation is not already set up, a configuration End Point needs to be created at config.[environment].CapitaSCP.getConfig with the following:
     function(params, credentials) {
    return {
        keys: [{
            id: 456,
            secret: "my==secret"
        }],
        defaults: {
            key: 456
        }
    };
}
2. All website users who need to pay for bookings must be added to a user group called PAYMENT RECONCILIATION for the reconciliation workflow to start
3. A Data Retention Policy should be set up for the Payment Reconciliation process. The schedule cannot be set up until the first process has started (because the DRM looks for existing histories)