April 2024 - Version 6.17
- 17 Apr 2024
- 2 Minutes to read
- Print
- DarkLight
April 2024 - Version 6.17
- Updated on 17 Apr 2024
- 2 Minutes to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
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.
Bug Fixes
- A valid Payment Method can now be removed from a Spreedly gateway using the Salesforce UI. An error message will be displayed when a user tries to remove a Payment Method that was already deleted. Previously, when a user tried to remove a Payment Method, the process wasn’t successful. (Known Issue: 000003046)
- When processing a payment using a Stripe gateway, the Payment Intent’s
Payment Method
andPayment Gateway Customer
fields will contain the associated Payment Method and Payment Gateway Customer records. Previously, the Payment Intent was created without the related Payment Gateway Customer and Payment Method. (Known Issue: 000003189) - Users can now click the Remove From Gateway button to remove a Payment Method from Salesforce without creating a duplicate Payment Method. Previously, a duplicate Payment Method was created with
Payment Method Status
= “Valid” while the original Payment Method correctly showedPayment Method Status
= "Deleted from Payment Gateway". (Known Issue: 000002803) - Clicking the
Stripe URL
field on a Payout Transactions record will take the user to the corresponding Stripe page. Previously, clicking the Transaction’sStripe URL
field took the user to a Stripe error page that said, “Sorry, something went wrong.” - If the Payments, Events, and Storefront apps and the Base package are installed, and a user applies a Code with a Code Eligibility to a single Store Product, the resulting Invoice will be created successfully. Previously, the user received the following apex error in a Blackthorn Log, and the Invoice failed to be created. “Insert failed. First exception on row 1; first error: FIELD_INTEGRITY_EXCEPTION, Event Item: Id value of incorrect type: a3L79000000ab5mEAA: [conference360__Event_Item__c]”
- If a Payment Processing Fee is applied to a paid Event and a discount Code less than 100% off is applied to the Event Item, the following will occur. The related discount Line Item and calculations will be correctly reflected on the Invoice, and the Attendee will be charged the correct amount. Previously, Attendees saw the correct amount due, but they were charged the full amount during checkout. (Known Issue: 000003499)
If you have any questions, please don't hesitate to reach out to Blackthorn Support.