...
Batch processing in closing an AQ Batch record are causing these issues
Multiple updates on triggering record and is causing Apex CPU Limit to exceed.
Multiple updates on triggering record and is causing duplicate updates on a single record.
Multiple updates on triggering record and is causing SOQL Limit to exceed.
Multiple updates on triggering record and is causing SOQL Limit to exceed.
Joining accounts using the Join Utility on Contact page is causing Apex CPU Limit to exceed.
Unit testing:
This unit testing steps can produce multiple gift and transaction records that would typically fail on the last build before this Jira’s fix
This unit testing aims to check that no errors and failures of the above issues would come out of the testing
Intial records creation
Create a single batch record and create multiple batch item records across multiple accounts
different Entry Types
different Schedule Types, this is to sample multiple Transaction records to be created
Confirm that the batch successfully closes
if the batch fails, Utility log log record will be created
Payment batch creation
Create a single batch record to create a payment across all created transactions under all the gift records in all the accounts from the intial batch created
Confirm that the batch successfully closes
confirm to see that all gift records' balances are 0 and transactions are created to act as payment to the intial transaction records created
if the batch fails, Utility log log record will be created
Payment reversal batch creation
Create a single batch record to create reversal payment across all created transactions under all the gift records in all the accounts from the payment batch created
Confirm that the batch successfully closes
confirm to see that all gift records' balances are 0 and transactions are created to act as payment to the intial transaction records created
if the batch fails, Utility log log record will be created
...