Content Comparison

...

• 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:

1. When a Transaction record is created or updated, when all conditions are met:Intial records creation

   1. Create a single batch record and create multiple batch item records across multiple accounts

      1. different Entry Types

      2. different Schedule Types, this is to sample multiple Transaction records to be created

         Image Added

   2. Close this batch and check to see that the batch closes as expected

   3. After successful closing of batch, confirm to see that related Gift records are created along with their corresponding transactions

2. Payment batch creation

   1. 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

   2. confirm to see that all gift records' balances are 0 and transactions are created to act as payment to the intial transaction records created

3. Payment reversal batch creation