Content Comparison

...

1. Process Builder - Automate task for GA for Pledge (v2) - replaced by USYD Automate task for GA for Pledge (subflow) )

2. Process Builder - Description - HOLD RECEIPT (v4) - replaced by USYD Description - HOLD RECEIPT (subflow)

3. Flow - AQC Donor Contact Type Auto-Updater (v2) - replaced by USYD AQC Donor Contact Type Auto-Updater (subflow)

4. Flow - (Affinaquest) Update Gift Designations (v1) - this is still active in PROD

Expand
title Screenshots of the errors that were encountered

...

Result: The above SOQL, when summarized resulted in 5 Gift/Pledge Records, which already has automatically created Task records. No manual record update or record creation done.

Second check: SOQL to check if there are Gift/Pledge that are in ‘Pending review’ based Transaction records' related Receipt’s creation date (vs Receipting date).

...

A Total of 62 receipts were voided in error as a result of the receipting utility creating consolidated receipts that were performed on July 6th and 7th of 2023. There currently is no option to set the utility to not automatically void receipts. Below are the only settings that Admins can configure in Affinaquest:

1. Receipting Enabled turns receipting on or off for the organization.  The default is off.

2. Maximum % allowed for Quids sets the percent of the gift total that the quid can be for the donor to get a tax receipt.  In Canada, the quid cannot be valued at more than 80% of the gift for a receipt to be issued.  Receipts will not be generated for gifts where the quid exceeds this percent.  If you do not wish to have a limit, leave this blank.

3. Maximum Amount Before Approval is Needed is the threshold at which a receipt will need approval.  Receipts that need approval are flagged and not generated automatically with other receipts.  This can be manually checked on each gift.  If the gift exceeds the threshold, it will be flagged even if not manually flagged during gift entry.  If you do not want any receipts to be flagged for approval, set this field to -99.  If you want all flagged, set to 0.

4. Signator Required allows you to set the field of Signator as a required field during data entry.  The Signator is the Contact on the Account with the legal credit for the gift. Every transaction will have a signator, but if this flag set to yes, it requires the user to populate the field for pledge payments and added transactions during gift entry.  If not set to yes, the system will determine the signator based on the distribution of the legal credit on the Account.

...

Hence, a Manual Update was necessary. The erroneously voided receipts were restored manually as a batch bulk via the data import wizard tool. This manual update essentially updated values of the Receipt object fields: Voided, Void Note, Voided Date.

...