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

[Draft] Affinaquest Release Version V29

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

« Previous Version 34 Next »

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. TAPSS-2281 - Getting issue details... STATUS

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.

TAPSS-2379 - Getting issue details... STATUS 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:
Voiding payments
Modify bequest
Reentering payments

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:
Voiding payments
Modify pledge
Reentering payments

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:
Voiding payments
Modify grant
Reentering payments

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 the change and testing per priorities.

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

  • Save and Add New Schedule does not calculate payments correctly in display.

  • DAF Gifts paying down Pledges do not also reduce Pledge Soft Credits

  • Grant Soft Credit's 'Record Type' change from "Pledge Soft Credit" to "Soft Credit" after Corrections are processed

  • GRC Adjustments not saving consistently on processed gift

  • Corrections Batch data entry on Bulk Entry is now using a new component for picklists and lookup lists.  The new component gives a smoother user experience.

  • Corrections Batch Soft Credits are not added to adjusted Pledges

  • 1.0: Pledge Payment Transactions for Anonymous Pledges do not have the 'Anonymous?' checkbox selected

  • 2.0: Partial Pledge Write Offs not creating adjusted Pledge Soft Credit Transactions

  • 'Third Party Payoff' no longer checked on Soft Credit Transactions paying down Pledges after Void and Correction

  • Using DAF method to reduce a Pledge on another Account does not check "Third Party Payment" on the Gift

  • Default Designation overwriting manual Designation entry on Pledge Payment Batch Item Transactions

  • Failed to Load Opportunity Error on Void and Correct

  • Smart Batch Correction:

  • Pledge Soft Credit records don't update correctly after Corrections Batches are processed

  • Pledge Amount fields process incorrectly after Corrections are made to Paid Pledges w/ partially paid Transactions

  • 2.0:

  • Clicking 'Save Without Linking' on Imported Batch Items results in duplicate GRCs

  • If there is an error in legal credit amount and batch cannot be closed, after adjusting the recognition credit value, the error is not gone

  • Pledges w/ 3 Soft Credits cannot have Payments processed ("Duplicate id in list" error being thrown)

  • Adding a pledge for "Add Transaction to Existing Gift" to an existing pledge doesn't have the correct payment number

  • 'Third Party Payoff' no longer checked on Soft Credit Transactions paying down Pledges after Void and Correction

  • Matching Gift Payments cannot be processed when non-AdvRM custom fields are on the Batch Item Transaction object

  • 'Credited Opportunity' field on Transaction records is not populated when Opportunities are linked

  • Using Add Payment with a Pledge, if the Account with the Hard Credit Pledge has an Automated Soft Credit Account, the Soft Credit is Added as a Payment on the Hard Credit Pledge

  • Deleting a record on the Batch Item datatable does not refresh the grid

  • Batch Default Entry Type component errors

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

image-20241105-000407.png

image-20241105-000407.png

image-20241105-000423.png

Available Method Comparison TAPSS-2387 - Getting issue details... STATUS

Entry:

image-20241104-034217.png

image-20241104-034245.png

image-20241104-034310.png

image-20241104-034243.png eg. No ‘Personal Property’

image-20241104-031609.png

image-20241104-031707.png

image-20241104-031726.png

image-20241104-031744.png

image-20241104-025234.png

image-20241104-025308.png

image-20241104-025326.png

image-20241104-025356.png

image-20241104-025424.png

image-20241104-025448.pngimage-20241104-025459.png

Pledge

Create pledge using smart batch

image-20241105-002957.png

image-20241105-003354.png

image-20241105-003512.png

Closing Batch

closing the batch and confirm batch item and transaction creation

image-20241105-003526.png

image-20241105-004208.pngimage-20241105-004227.png

image-20241105-004323.png

Payment

create a payment to pledge

image-20241105-004753.png

image-20241105-004829.png

image-20241105-005126.png

image-20241105-005231.png

Batch Correction

create batch correction for pledge/partially paid pledge

image-20241101-040605.png

image-20241101-040718.png

image-20241101-040831.png

image-20241101-042038.png

image-20241101-042233.png

image-20241101-042253.png

Voids and Corrections

Voids and Corrections

  • All Voids and Corrections can be done in Gift/Pledge batches.

  • Voids and corrections on Open Pledges can be done in Gift/Pledge Corrections batches with fewer batches than if done with Gift/Pledge batches.

 

Voiding and Redesignating Pledges from one Designation to Another Single Designation

  • Select the Account for the donor of the Pledge.

  • Choose Method of Void.

  • Click Void Transactions next to the appropriate Pledge.

  • Check the pledge installments that you want to redesignate. All available installments will be checked by default.

  • Click Void Transaction and Add Correction.

  • Enter void notation Description and Click Void Transaction.

  • Under New Schedule, Enter the Due Date based on your original pledge schedule, Choose your Pledge Type, Campaign Appeal, Designation, and Acknowledgement Type.

  • Click Save.

  • Click the Close Batch button at the top of the Batch Item entry screen or on the main Batch screen to close the batch.

  • Click Confirm Close.

  • Click Ok to confirm.

  • Navigate to the donor’s Account and click the Giving tab to verify the redesignation.

Voiding and Redesignating a Pledge Installment from One Designation to Two or More Designations

  • Select the Account for the donor of the pledge.

  • Choose Method of Void.

  • Click Void Transactions next to the appropriate Pledge.

  • Check the pledge installment that you want to redesignate. All available installments will be checked by default.

  • Click Void Checked Transactions.

  • Enter void notation Description and Click Void Transaction.

Now, in the same batch, you can create the two new pledge schedules for the two designations by using the Method of Add Transaction to Existing Batch:

  • Choose the Account and Method of Add Transaction to Existing Batch.

  • Choose Payment Method of Pledge.

The Pledge will popup.

  • Choose Add Transaction next to the appropriate pledge.

  • Choose Payment Schedule Type of Single Payment.

  • Complete the values for the first portion Amount and its Designation. Be mindful to align your Due Date to the old first pledge installment.

  • Click Calculate Payments.

  • Click Save.

Follow those steps for the second portion and its Designation.

Follow those steps for any additional amounts and Designations.

  • Click the Close Batch button at the top of the Batch Item entry screen or on the main Batch screen to close the batch.

  • Click Confirm Close.

  • Click Ok to confirm.

  • Navigate to the donor’s Account and click the Giving tab to verify the redesignation.

Voiding and Redesignating a Pledge Payment from One Designation to another Single Designations

  • Select the Account for the donor of the pledge and payment.

  • Choose Method of Void.

  • Click Void Transactions next to the appropriate Gift/Pledge.

  • Check the payment transaction that you want to redesignate. All available payments and installments will be checked by default.

  • Click Void Checked Transactions.

  • Enter void notation Description and Click Void Transaction.

  • Click Save.

Now, you will need to close this batch, so you can redesignate the pledge installment and then make a payment on the next installment:

  • Click the Close Batch button at the top of the Batch Item entry screen or on the main Batch screen to close the batch.

  • Click Confirm Close.

  • Click Ok to confirm.

Now, you will open another batch to redesignate the pledge installment:

  • Create a new Gift/Pledge batch.

  • Select the Account for the donor of the Pledge.

  • Choose Method of Void.

  • Click Void Transactions next to the appropriate Pledge.

  • Check the pledge installment that you want to redesignate. All available installments will be checked by default.

  • Click Void Transaction and Add Correction.

  • Enter void notation Description and Click Void Transaction.

  • Under New Schedule, Enter the Due Date based on your original pledge schedule, Choose your Pledge Type, Campaign Appeal, Designation, and Acknowledgement Type.

  • Click Save.

  • Click the Close Batch button at the top of the Batch Item entry screen or on the main Batch screen to close the batch.

  • Click Confirm Close.

  • Click Ok to confirm.

Now, you will create a new batch to make a payment on the pledge installment with the new designation:

  • Create a new Gift/Pledge batch.

  • Select the Account for the donor making the payment.

  • Choose Method (e.g., Check, Credit Card).

  • Enter Amount and see the Open Pledges pop-up.

  • Select appropriate Pledge and Click Post as Pledge Payment.

  • Enter Acknowledgement Type and appropriately apply the Amount to the correct installment, which can be determined by the Due Date and Designation.

  • Click Pay Pledges.

  • Click the Close Batch button at the top of the Batch Item entry screen or on the main Batch screen to close the batch.

  • Click Confirm Close.

  • Click Ok to confirm.

  • Navigate to the donor’s Account and click the Giving tab to verify the pledge and payments are properly applied.

Soft Credit

Create pledge and calculate with soft credit with foundation for a Houshold and confirm automatically created soft pledge records upon closing.

image-20241105-005822.png

image-20241105-010310.png

image-20241105-010826.png

image-20241105-011728.png

Batch Approval/Closing Report

 

image-20241105-030637.png

image-20241105-030807.png

image-20241105-030428.png

image-20241105-030746.png

Batch Reports

Ana’s comment: Batch Reports that don’t working in Smartbatch 2.0:
Batch Control Verification - Payment

Batch Control Verification - Pledges
Batch Items by Method Buckets
Batch Item Transaction by Method Buckets

Batch Validations

PeopleSoft Integration, Validation

  • set Batch Review Status to Ready for Validation


image-20240910-233241.png

Ana’s comment: Batch validation not working. When set the batch status to ‘ready for validation’ and it should either validate successfully or validate with error. It does not do either.

  • No labels