/
Proposed Changes on Consolidated Receipt

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

Proposed Changes on Consolidated Receipt

There are 3 improvements that is proposed:

Parametrization of Period and Year on Merge Action

so that they don't need to be updated on template

  1. update template

  2. Update Merge action with Parameter and Match fields

 

Update MSR with Salutation Java which applies 4 salutation rules

  1. If Contact does not have a salutation, use the Dear Name

  2. If Name is only one character, use Dear Supporter

  3. If Salutation is standalone, use Dear Salutation (i.e. Dear Chancellor)

  4. Else, use the usual Dear Salutation Surname

 

Prevent reporting multiple rows for for gifts with multipleGRC record

  1. So that we don’t pull in multiple GRC records into two rows we Show this step's records in 2 column blocks

     

  2. Because we changed the structure of step 3, we will have to update the Calculated Step fields to refer to the correct “Step”

    1. Email Priority
      Gift Recognition Credit. bcecomes Gift Recognition Credit 1.

      {!Gift Recognition Credit 1.Contact Credited.Best Contact Email} ? {!Gift Recognition Credit 1.Contact Credited.Best Contact Email} : ({!Gift Recognition Credit 1.Donor Account.Email} ? {!Gift Recognition Credit 1.Donor Account.Email} : "")
    2. LC-S

      ({!Gift Recognition Credit 1.Gift Recognition Credit.Legal Credit %}== 100) && ((({!Account.Secondary Contact.Name}+{!Account.Secondary Contact.Best Contact Email})==({!Gift Recognition Credit 1.Contact Credited.Name}+{!Gift Recognition Credit 1.Contact Credited.Best Contact Email})) || ({!Account.Secondary Contact.Name}=={!Gift Recognition Credit 1.Contact Credited.Name})) ? "S" : ""
    3. LC-P

      ({!Gift Recognition Credit 1.Gift Recognition Credit.Legal Credit %}==100) && ((({!Account.Primary Contact.Name}+{!Account.Primary Contact.Best Contact Email})==({!Gift Recognition Credit 1.Contact Credited.Name}+{!Gift Recognition Credit 1.Contact Credited.Best Contact Email})) || ({!Account.Primary Contact.Name}=={!Gift Recognition Credit 1.Contact Credited.Name})) ? "P" : ""

       

    4. LC Both Same Last Name

    5. LC Both Different Last Name

    6. Salutation

    7. Salutation - Java

    8. To support standalone salutation https://sydneyuni.atlassian.net/browse/TAPSS-913

    9. on Step 1 added the following fields



    10.  

 

Related content

TAP Receipting Blueprint - Techno Functional
TAP Receipting Blueprint - Techno Functional
More like this
GA Consolidated Receipts EOFY Process
GA Consolidated Receipts EOFY Process
More like this
TAPSS-830 Retaining Original Receipt Name on Receipt
TAPSS-830 Retaining Original Receipt Name on Receipt
More like this
2023-10-26 AQ Consultation Session 1
2023-10-26 AQ Consultation Session 1
More like this