We are happy to present the FinDock March ’20 Release.
- Release to Sandboxes: February 23, 2020
- Release webinar: February 28, 2020
- Release to Production: March 1, 2020
In this release, we have three major features and a few enhancements.
- New features:
- Salesforce Guest User Security updates CRITICAL!
- Payment Request Generator
- Enhancements and bug fixes:
- Payment API performance
- Very large Pain.002.001.03 file handling
- Payment profile in API calls
On March 1st 2020, Salesforce will begin a phased deployment of Guest User Security updates on all sites accessed by guest/unauthenticated users. If you use FinDock in combination with a donation page (through the payment API), then you may be impacted by these Salesforce changes.
To be ahead of the game, FinDock implemented a solution to handle the new Guest User Security functionality already now. Please note that customization outside of FinDock's scope can also be impacted by these Salesforce changes. Therefore, we encourage you to test your Payment API when this FinDock release goes to sandboxes. For more information about the upcoming Salesforce changes, please refer to this Salesforce article.
If you experience issues after Salesforce has deployed the restricted Guest User's Sharing Settings and Record Access, you may need to opt-out by disabling the new setting as instructed by Salesforce. Please note that during this year, these changes will become mandatory with no opt-out option.
The Reference Generator that was being piloted is launched now for general availability and renamed Payment Request Generator. With this feature, valid payment references that comply with official rules and checks can be generated for different payment methods and ‘stamped’ on any Salesforce record. This can be on the standard Salesforce object but also on your own custom objects.
The generated payment reference can be included, for instance, in outgoing communication or on a payment slip. Via Guided Matching they can be easily matched to incoming donations. With this release the ‘Acceptgiro’ and ‘ESR’ payment references are available in the Payment Request Generator. For detailed information, see Payment Request Generator in our knowledge base.
We have significantly improved the baseline performance of the Payment API. API calls are now processed up to 8 seconds faster. Org-specific configurations, data, PSP performance and so forth impact performance, so actual speed varies. However, we expect all customers to see considerable improvement.
Issue: Extraordinarily large Pain files did not fit in the raw XML field. This was the case when the file had a batch level tag (OrgnlPmtInfAndSts) with lots of transaction entry level tags (TxInfAndSts). The total characters exceeded the 131,000 character limit of the XML field.
Solution: FinDock no longer stores the raw XML on batch level, rather only on entry level.
Issue: When initiating a payment through the Payment API with both account and contact information in the message, the wrong payment profile was linked to the installment. This was caused by the API selecting a payment profile only based on the bank account number related to the account, without considering contact information. This mostly impacted payment through Buckaroo.
Solution: The Payment API now selects the payment profile based on the contact data and bank account number provided in the API call.