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
Affinaquest Release Version V29
To be compliance with the university guideline for the 3rd party vendor version (N or N-1 version management) as well as compliance with industry guideline on salesforce compliance and cyber security, after consulting with AQ professional service for best practice, we are conducting assessment to upgrade to V29. https://sydneyuni.atlassian.net/browse/TAPSS-2281
Execution Decision with Timeline (TBD)
Q4 2024
Do not introduce any new features beyond V26 but perform a technical upgrade V29 to be compliance with University and Industry guideline.
https://sydneyuni.atlassian.net/browse/TAPSS-2379 Assess ‘Gift Bulk Corrections’ function to confirm whether we can deliver this enhancement as it is a confirmed high priority to reduce the current business manual steps for multiple scenarios as below:
Object | Vendor | Scenario | Observation/Issue | Work Around | Impact/Risk |
Smartbatch | AQ | Modifications - bequests | Paid bequests cannot be modified in a pledge correction batch | Multi step mod process using 3 batches: | increased workload and processing times |
Smartbatch | AQ | Modifications - Pledges | Paid pledges cannot be modified in a pledge correction batch | Multi step mod process using 3 batches: | increased workload and processing times |
Smartbatch | AQ | Modifications - Grant | Paid grants cannot be modified in a pledge correction batch | Multi step mod process using 3 batches: | increased workload and processing times |
Batch Item | AQ | Gift pledge correction - Bulk Entry | When modifying multiple gifts from holding to a new account we are unable to search by gift number or account. | Search by designation or date and delete all the unwanted transactions. | Time consuming |
Business UAT timeline (TBD)
2025 Q1
Q1 2025
Focusing on Smart Batch 2.0 and Gift process enhancements with the business to go through the current manual process and deploy any necessary change, version upgrade and testing per priorities.
*Smart Batch 1.0 will be deprecated from the managed package with the Winter ‘25 – Version 31 in early 2025. *
Combined New features for V27,28,29
Gifts & Smart Batch 2.0 Enhancements
V27
Gift Processors
Gift Bulk Corrections
In 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.
For additional information on Gift/Pledge Corrections Batches with Bulk Entry please see Mass Changes to Gifts (Bulk Entry).
Data entry screens configuration
Personal and Real Property gift processing in Smart Batch 2.0
Gifts of Services processed in Smart Batch 2.0
Matching Gifts
Convert Gift to Pledge Payment
Add Transaction to Existing Gift
DAF Gifts
Consolidated Gifts
V28
Streamlined data entry for multiple security payments on pledges
Gift Date option for batch entry
Close Batch added to data entry screen
The Smart Batch 2.0 field is now checked by default when creating a new batch
V29
Streamlined data entry for multiple security and crypto gifts.
Instrument Descriptor added to Planned Giving entry screen.
Clicking 'Save Without Linking' on Imported Batch Items no longer results in duplicate GRCs.
Engagement score
Additional buckets for Engagement Score on Accounts and Contacts
Prospect Queue
Mass Assignment and Reassignment can be done in the Prospect Queue
Communication Channel
The Communication Channels screen is now configurable on both Accounts and Contacts.
Contact utility
The Decease Utility has been rewritten as a Lightning Web Component.
Merge assistance
New Utility to merge record on Contact page layout
Opportunity Component Change
New fields and function related to recognition option offer function
Alternative Channel
New Record types
GA Batch &Smart Batch Defect Fixes & Minor enhancements (24 total)
V27 | V28 | V29 |
---|---|---|
|
|
|
Decision for configuration
In order to minimize any impact, the proof-of-concept and user stories and below comparison analysis for V29 were conducted and prepared with a cope of V29 version upgrade with V26 configuration.
V26 vs V29 Gifts Scenario Comparison
Category | Steps | V26 UAT SB1.0 | V26UAT 2.0 | V29POC |
---|---|---|---|---|
Smart Batch 2.0 Default checkbox | Create ‘Batch’ record |
|
| |
Available Method Comparison https://sydneyuni.atlassian.net/browse/TAPSS-2387 |
| Entry:
|
|
|
Pledge | Create pledge using smart batch |
|
|
|
Closing Batch | closing the batch and confirm batch item and transaction creation |
|
|
|
Payment | create a payment to pledge |
|
|
|
Batch Correction | create batch correction for pledge/partially paid pledge |
|
|
|
Voids and Corrections |
|
|
|
Voids and Corrections
|
Soft Credit | Create pledge and calculate with soft credit with foundation for a Houshold and confirm automatically created soft pledge records upon closing. |
|
|
|
Batch Approval/Closing Report (Closing report not used) |
|
|
|
|
Batch Reports | Make sure all the Batch reports are working |
|
Batch Control Verification - Pledges | Batch Control Verification - Payment Batch Control Verification - Pledges |
Gift Date & Gift Credited Date fields in Smart Batch | When ‘Gift Date’ and ‘Gift Credited Date’ are ticketed, Smart Match 1.0 display these fields in Batch Item UX. |
| Gift Date Not available in Smart Batch 2.0
| Available in Smart Batch 2.0
|
Batch Validations | Check UAT Peoplesoft integration | PeopleSoft Integration, Validation
| Check UAT environment for PeopleSoft integration | Check UAT environment for PeopleSoft integration |