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
TAPSS-2037 - AQ Version 25 UAT Testing
- rommel.ngo
- Ana Simic
Scenario | Expected | Result |
|---|---|---|
TAPSS-2037-001 AC1 Preupgrade and post upgrade steps are carried out 
| UAT in v25 Campaign Influence turned on Campign influece records exist | pass 
|
TAPSS-2037-002 AC3 SmartBatch 2.0 is deployed but user won’t have access to it yet as it is not fully functional on v25 | SmartBatch 2.0 is not enabled, no option to switch to SmartBatch 2.0 if swtiched the flag in the backend, it would hit an error as permission has not been provisioned for SmartBatch 2.0 Objects | pass
|
TAPSS-2037-003 AC4 Pledge Soft Credits Written Off when Pledges are Written Off in Contact Utilities
| Pledge Soft Credit has been written off | pass
|
TAPSS-2037-004 AC5 Primary and Secondary Contact checkboxes throw component errors when toggled
| This error message do not appear
| pass GA-PASS |
TAPSS-2037-005 AC6 Receipting Utility Date fields work as expected for orgs in Australian timezone
| receipting utility should pick up the transaction as transaction for that day rather than yesterday | pass
|
Smart Batch 1.0 testing (Complex Scenarios) | ||
TAPSS-2037-006 AC2 (GA process remains the same and unaffected by the upgrade) Gift from a foundation with soft credit to a multi contact household with 50/50 LC
| gift and soft credit are created Soft Credit has GRC Legal credit should be 0
| pass GA-PASS |
TAPSS-2037-007 Accidentally discovered as having been fixed in v25 Indirect Contact Auto Gift Recognition
| GRC credit awarded without error for Org with indirect contact GRC for reference, in v24 it would give this error icon and cannot close the batch
| pass GA-PASS |
TAPSS-2037-008 AC2 (GA process remains the same and unaffected by the upgrade) Transferring an Org Gift or an fully paid pledge from holding to a new designation with soft credit to a household account
| Note that this is a hypothetical scenario which results to two GRC on the same contact, one through GRC on Soft Credit and the other is through automatic award of GRC on the Gift itself. User should be aware not to do this as it duplicates the GRC records. User should choose either to award GRC through the indirect relationship or through the creation of Soft Credit Gift Pledge Soft Credit
As mentioned this scenario resulted to two GRC on the contact
| pass GA-PASS @rommel.ngo the GRC to the contact who is indirectly linked has duplicated after gift modification.
|
TAPSS-2037-009 AC2 (GA process remains the same and unaffected by the upgrade) Continuation from previous test
| Pledge is paid Soft Credit also paid
| pass GA-PASS |
/TAPSS-2037-0010 AC2 (GA process remains the same and unaffected by the upgrade) Continuation from previous test
Note that in version 27, user can use Batch Correction to correct a paid pledge with Bulk entry. Eliminating the process of voiding the payment, transferring to a new designation and entering the payment again. Bulk CorrectionsIn Gift/Pledge Corrections Batches, Gifts and Pledges can now be searched for on Gift/Pledge Number allowing for the update of Gifts and Pledges (including closed Pledges) to be done in a single step for change of Designation.
| Payment and Soft Credit Pledge are Voided After Batch Correction, both Pledge and Soft Credit Pledge are corrected After entering the new payment on new Designation
| pass GA-PASS |
TAPSS-2037-0011 AC2 (GA process remains the same and unaffected by the upgrade) Convert a gift to pledge payment
| Gift has been voided
payment has been applied to pledge
| pass GA-PASS |
TAPSS-2037-0012 AC2 (GA process remains the same and unaffected by the upgrade) ASOP recurring gift payment Batch |
| GA-PASS |
Smart Batch 1.0 testing (Simple Scenarios) | ||
TAPSS-2037-0013 AC2 (GA process remains the same and unaffected by the upgrade) PeopleSoft Integration, Validation
| Batch Should be either Validated Successfully or Not
| ga-pass |
TAPSS-2037-0014 Establishing a new recurring gift.
| New recurring continuity pledge has been created and linked to the recurring gift object. The payment schedule is active and linked to the recurring gift object. The BT transaction due date and recurring gift due date match.
| GA-PASS |
TAPSS-2037-0015 Auto creation of a credit card batch
| New transaction would authorise successfully. New transaction would capture successfully. Batch will auto create with batch item and batch item transaction. Batch is auto assigned to the user who captured the transaction. Batch item is linked to the BT transaction that was captured. | GA-Pass |
TAPSS-2037-0016 Create and modify from holding a 3rd party pledge payment.
| 3rd party payment would successfully pay down the instalment on the pledge. 3rd party payment and pledge would successfully transfer to the new designation. | ga-pass @rommel.ngo as per the final screenshot on this test, the payment number for payment number 1 has changed to number 6 now. Is that normal is modifications? I haven’t noticed it before. |
TAPSS-2037-0017 Creating a Bequest budget with zero legal credit on the direct contact.
| Able to close a batch with zero legal credit to the deceased signator contact. | ga-PASS (scenario not covered by this upgrade)
16/9 @Ana Simic , as communicated, this is actually a different issue which was raised to AQ. kindly update the result for this scenario
|
TAPSS-2037-0018 Create a Multi designation pledge and add a payment.
| Pledge is successfully created with multiple designations. Pledge is successfully paid down with one payment splitting into the two designations. | Ga-pass |
TAPSS-2037-0019 Run reports from smartbatch e.g batch approval report, imodules batch proof, credit card batch proof.
| Successfully run all reports from the batch.
| ga-PASS Only 1 of 3 reports was successful:
16/9 @Ana Simic can you please recheck this, if still persist can you do a clear cache, I am able to run the merge action without the error on my end @rommel.ngo all 3 reports are working now. |
TAPSS-2037-0020 Cheque batch - (check custom fields) add cheque details in description field and check that they appear in the corresponding fields in the batch item. Change cheque dates using the 'Usyd Batch date' option on the batch details screen. Add a bequest intention task to a cheque gift from the batch item transaction screen.
| Check details transfer automatically from the description field into the batch item bank, BSB and drawer fields. New bequest task is created successfully from the batch item transaction screen. Batch dates, batch item dates and batch transaction dates are all updated to the date entered into the Usyd Bank date change function. | ga-pass |
TAPSS-2037-0021 Receipting
| Receipt object is successfully created. Apsona report generated a reciept, attaches the PDF receipt to the receipt object and emails the donor using the email receipt template. | ga-PASS Apsona not working: 16/9 @Ana Simic this is now fixed, can you please retest @rommel.ngo thank you, I can successfully run Apsona and generate and attach the print receipt but the email receipts won’t attach the pdf to the receipt object due to the email function being turned off in UAT.
|
