Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Skip to end of banner
Go to start of banner

TAP-902 CPU Time limit Simulation and Analysis

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Defects for TAPSS-891

891-002

  1. 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 that the batch successfully closes

      1. 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. if the batch fails, Utility log log record will be created

Record Involved:

  • 1 Batch record

  • 11 Batch Items

  • WIP Batch Items Transactions c/o anderson.pagtabunan - pls plug in the average records

All steps should be executed successfully

FAIL

Batch 0076229 | Batch | Salesforce

20230529-2338 | UtilityLog | Salesforce

 

Current Batch class by AQ (Managed packaged), code is hidden:

MS tried to replicate the batch processing with lower batch size parameter of 1 in this record:

Batch 0076241 Record in SIT (10 batch items, with average of 35 to 45 Batch Items Transactions

  • No labels