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-830 Retaining Original Receipt Name on Receipt
Description
Persona + Need + Purpose
As a
GA User
I want to
I would like to track the original Receipt Name on Receipt
So that
so that it can be tracked and reported specially when a receipt needs to be reissued to the account name the receipt was issued on at that time.
AC:
Create a new field to store the Original Receipt Name at the time the Receipt is created. Call the new field as "Original Receipt Name". The value of the Original Receipt Name should be taken from the field AQB__Gift__c.GRC_roll_up__c GRC_roll_up__c. This field takes the following value from Flow: Gift Pledge Update - V6
Trigger: Gift/Pledge Created or Edited
If GRC exist:
concatenate contacts’:
Contact.Receipt Name
or
Contact.FirstName Contact.LastName
else:
Account.Account Name
lock this field and only allow edit by GA users.
Apsona report to be changed for Receipting to map the new Account Name field from Gift instead of Account lookup field. (better a use a condition if the field is null, in case we don’t migrate all records)
Update the following Apsona Items:
Apsona Multi Step Report : Merge Action : Document Template
Receipt - Email : Generate Email and Attach to Record : USYD_New Standard Receipt Template - Aug 26th _ 2022.docx
Receipt - Non Email : Generate Document and Attach to Record : USYD_New Standard Receipt Template - Aug 26th _ 2022.docx
Reprint Receipt : Reprint Receipts : USYD_New Standard Receipt Template_Reprint - Edited - BP.docx
For all the receipts, whenever the Account Name is referenced in the Receipt, it should check if the new field (Original Receipt Name” is filled then it should take that value else take the AQB__Gift__c.GRC_roll_up__c GRC_roll_up__c.
Refer to Confluence page TAP Receipting Blueprint - Techno Functional
Update all the historical gifts. Update the New field with the Account Name by comparing the Account field history tracking and date and time creation of gifts. If no field history for Account Name then update the current Account Name. I think priority can be given to non household account. Sample account is Woodend Pty Limited.
Caveat, if the renaming of account is a typo, user need to update the “Gift creation Account Name” field on the gift.
Business Value: Be able to reissue a receipt with the name of the account that the gift was given under at that time.
Technical Design:
Create a new field “Original Receipt Name”
Provided access via Admin, Read Only profiles and Permission set USYD_SmartBatchGiftEntry
Added the field to the page layouts in use
Created a Receipt Before Save flow - to update the Receipt->Gift/Pledge->GRC Rollup to the new field
Test Scenario 1:
Create a Receipt using the Standard Process by going to the “Receipting” tab
Provide Batch/Gift Number and click on Create Receipts
Check the Receipt created find the “Original Receipt Name” - It should display the Gift-GRC Rollup value
Test Scenario 2:
Update the Account Name linked to above gift from New Test 123 to New Test 123 Swathi
Check the Receipt record “Original Receipt Name” if changed (It shouldn’t change)
Test Scenario 3:
Update the created Receipt and check if the Original Receipt name is altered.
Test Scenario 4:
Check if except GA and Admin anyone able to edit the Original Receipt Name
Note: All admins, GA team, BI-DRS will get edit access to field and also any users with Advancement Service Permission set Group will automatically get access
Why DO Laila has Advancement Services permission set group.
Test Scenario 5:
Run Apsona Receipting template and check if the Account Name mapping is changed to new field.