February 2024 - Version 6.13
  • 28 Feb 2024
  • 3 Minutes to read
  • Dark
    Light

February 2024 - Version 6.13

  • Dark
    Light

Article summary

Once the updates listed below have been reviewed, please follow the upgrade instructions to upgrade your Payments application.

Salesforce Release Update Known Issue

Enable Secure Static Resources for Lightning Components is a Salesforce Release Update that has been postponed indefinitely. Test Run on this Release Update should remain disabled in order to use our Virtual Terminal components. This is due to a Salesforce Known Issue.

Upgrade Instructions

To upgrade Payments to the newest version, go to the Blackthorn Candy Shop.

Important Update

The Smart Scheduler (Blackthorn Base package) was added to the Blackthorn Candy Shop. Messaging customers can now use Smart Scheduler without downloading the Events or Storefront apps.

Bug Fixes

  • When using an Authorize.net payment gateway, the customer's information will be captured and added to the customer's billing information section on the Transaction Detail page (in Authorize.net). Previously, the collected address information wasn't sent to Authorize.net even though the payment was received. (Known Issue: 000003103)
  • The auto-renew payment schedule will generate a new Transaction if the initial Transaction is paid with an ACH transfer. The payment schedule will also be updated appropriately after the Transaction is completed. Previously, a new Transaction was not generated, and the payment schedule was not updated correctly. (Known Issue: 000002886)

Line Item Object

  • The Line Item’s Total field will be calculated correctly when the record is created or updated. Previously, the Total field contained an incorrect value.
  • The Line Item’s Total description and help text have been updated.
    • Description: The Total amount, calculated as the Net amount plus Tax, less any written off amounts.
    • Help Text: The Total Amount including Tax, less any discounts and written off amounts.

Virtual Terminal Custom Settings

  • In the Blackthorn Payments | Virtual Terminal custom setting, the help text for the Disable New Payment Method and Default New Payment Method fields was updated to remind users not to enable both options simultaneously.
    • Default New Payment Method: Shows the "New Payment Method" screen when loading the Virtual Terminal. Can't be enabled with "Disable New Payment Method."
    • Disable New Payment Method: Disables the ability to create a new Payment Method in the Virtual Terminal. Can't be enabled with "Default New Payment Method.”
  • In the Blackthorn Payments | Virtual Terminal custom setting, help text for the Show Address field was added. Help text: "When enabled, additional address fields (Street, City, State, and Country/Region) will be visible on the Payment Method creation page in the Virtual Terminal. These fields are required for certain Spreedly gateways.”

Enhancements

  • The introduction of high-volume batch processing resolves the issue of scalability with our batch processes. Previously, batch processes were limited to one record at a time to ensure that Payments was compliant with Salesforce's limits. The new protected custom setting is in Blackthorn Pay – Features.
    • Field Label: Auto-Change Batch Size
    • API Name: Auto_Charge_Batch_Size__c
    • Data Type: Number(3,0)
    • Description: Controls the batch size of the scheduled job. The default setting is 1. Currently, the maximum supported value is 75.
  • The labels of the Virtual Terminal versions have been updated to match the naming convention of the other custom components. Previously, both versions were similarly named and difficult to tell apart.
    • Blackthorn Virtual Terminal -> BT Payments Virtual Terminal
    • BT Payments Virtual Terminal -> BT Payments LWC Virtual Terminal

Update

We received reports from some customers that Invoices were not loading correctly after the February release. While we investigate the issue, we have rolled back the DocumentLink webapp to the January release. The previously listed bug fix will be included in the next release.

If you have any questions about this or need help with testing, please don't hesitate to reach out to Blackthorn Support.