Brickwork User Guide - Release Notes

Release 6.50 | October 2022

Brickwork now translates fully to French. This means if you are using Salesforce in French language, the Brickwork application will also be in French
Resolved an issue that was preventing an Automatic Collection record from running when time period was set to 'Day of the Week'
Added new custom setting field to prevent recurring donation end date from automatically being set to current date for NPSP Enhanced Recurring Donations.
Fixed an issue with Salesforce Locale setting that was throwing an error when accessing iATS Settings and Button

Additional elements of the Brickwork application on Salesforce will now translate to French
Unknown property error affecting Recurring Donation virtual terminal resolved

Introducing Automatic Collections, a way to reattempt and collect failed recurring transactions. Read more here.
Resolved a bug for single payments via Aura to Brickwork that may have a close date and opportunity name showing the following day.
Resolved a bug for frequency being incorrectly set to Monthly when using saved payment details
Resolved an issue with the iATS Settings page not being displayed if there is a blank 'iATS Log' record or one that doesn't pertain to batch processing

Added Brickwork Onboarding for new users to get step-by-step instructions to install Brickwork correctly
Batch Processing updated to compensate for NPSP Enhanced Recurring Donations (previously was only for legacy Recurring Donations)
Utilization of NPSP Recurring Donation object 'End Date' field. This field is now populated via Aura to Brickwork processing, virtual terminal recurring setup creation/update, and batch processing. The field is also utilized to pre-populate the Recurring Donation virtual terminal if the 'Pre-populated Virtual Terminal Recurring Fields' field is set to true on the iATS Settings page.
Fix for ‘First error: Start did not return a valid iterable object.’ Error in apex jobs.
Fix for issue in which NPSP Enhanced Recurring Donations were occasionally being set to Closed after creating a recurring payment setup via the Recurring Donation virtual terminal.
Fix for NPSP scheduling that wasn't shown as an option if Weekly was the schedule, and the frequency was 3 on the related Recurring Donation record.
Fix for when the recurring payment setup (customer code) was set to 'Off' via the Virtual Terminal, it wasn't setting the related Recurring Donation 'Status' field to Closed if the client wasn't previously on legacy Recurring Donations.

Resolved a bug where an email was sent by error if the mapped email address is blank
Resolved a bug where Withdrawn opportunity stage is not updated to Approved stage after iATS Transaction status updated
Resolved an issue with Virtual Terminal when data format set to ‘English (Canada)’
Resolved an issue which was automatically clearing credit card numbers

Added the ability to clone existing payment information to create a new customer code on a recurring donation record.
Ability to use advanced recurring frequency options (called as NPSP scheduling) that are not currently available via iATS scheduling in Brickwork. Currently, donors can only choose from weekly, monthly, quarterly or yearly recurring donation frequencies, but with our new update donors will be able to set advanced frequency schedules such as biweekly, 1st and the 15th, semi-annually etc.

Ability for clients to save donor’s credit card information without a transaction
Ability to attribute a new online form transaction to a primary campaign on salesforce
Ability to send any custom parameter via the post back URL or Hosted Aura link to Salesforce
Easier Batch Processing with customer code lookup feature

Added compatibility with new NPSP enhanced recurring donations.
- Clients migrating to the new Enhanced Recurring Donations will require this new version of Brickwork (v5.45); however, clients who remain on classic will have no issue with the new version.