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 Fall '23 - Version 26
- rommel.ngo
- seonah.choe
Affinaquest Advancement RM 25.x was released on November 2, 2023
Configuration from version 25
In Rolling out version 25, it was recommended to the business and the business agreed that any SmartBatch 2.0 feature is going to be deferred for use until Version 26 (which is this one). The reason being is that the available functions available in v25 are quite basic and do not cater for most of the scenarios we process (i.e. pledges and pledge payments). Thus we have also deferred any configurations relating to SmartBatch 2.0. The time to roll them out is with this version. Please see the configuration from AQ release notes
https://support.affinaquest.com/hc/en-us/articles/18137162212877-Configuring-the-Smart-Batch-Data-Entry-Screen
Add permissions for users who enter data in Smart Batch and/or close batches to the Apex Classes:
BatchItemDataDisplayController
ProcessSmartBatch
ServiceProcessSmartBatch
SmartBatchController
New Field - Smart Batch 2.0
AQB__SmartBatch2__c
Checkbox
Used to toggle between Smart Batch 1.0 and 2.0.
Add the field Smart Batch 2.0 to the page layout for Open Batches to allow toggle between Smart Batch 1.0 and 2.0.
Smart Batch 2.0 (AQB__SmartBatch2__c) has also been added to the Batch Item object and will be copied from the Batch. This field is for internal use only in processing and should not be manually updated or changed. Permissions to this field will be added with the Update Permission Set for gift batches.
Custom Fields on Batch Item Transactions
Custom fields can be added to Batch Items Transactions and will pass through to the processed Transactions if the field has the same name.
- Allow users to configure Smart Batch 2.0 data entry screens?
What’s New?
Description | Testing / Training Scope | Impact | Comments |
|---|---|---|---|
Smart Batch 2.0 | Yes |
|
So we use them to record the gift date of EFT's, pledges, bequests and grants. Where the money has been received on a different day than what we enter it into Jarvis or the pledge deed was signed on a different day than we are entering it. We want to record the actual date of the gift not just the processed date. We usually put the same date in both fields e.g. if cashiers say an EFT was received on the 25th and we enter it on the 28th then we populate the two dates with the 25th. This gift and it's receipt will have the 25th on it after closing the batch (important at EOFY if we need to receipt for June but we processed in July). The only time we put different dates in them is in the new year, if we have received a grant in January 2024 for instance but the grant was awarded in December 2023 then we want to record that the gift was made in 2023 but we want to count it as funds raised in 2024, gift date would be Dec 2023 and credited override date would be 2024. in v28, Gift date will be available for input, up until then user need to update the gift date on batch item (I have tested this and seems to be working) Since soft credits are now created as transaction, the total amount on batch item would include the soft credit. As per testing, when created in SmartBatch 1.0, soft credits are as per usual, they are not created as transactions. - we need update, Apsona (Batch Approval, etc.)
|
Communication Channels | No | The standard Salesforce format for non-US or Canadian phone numbers is now used in Communication Channels. |
|
Contact Utilities | Yes | The Decease Utility will no longer overwrite the End Date or change the Status of an Employment row if the End Date is populated. If the End Date is not populated, the utility will populate the End Date with the date of death if known or the current date if the date of death is not known and will change the Status to "No Longer at this Position." v26
 decease the contact  Employment record after decease
V24 before Decease
after decease (status and end dates are overwritten)
|
|
Gift/Pledges | Yes | A new field has been added, Initial Amount Pledged. This field totals the Amount of all Batch Item Transactions with a Type of Pledge during batch processing. It is not a formula field and is never updated by the software after initial calculation. It can be updated manually. |
|
Name Definitions - Accounts | No | Medical and Professional Suffixes can now be used in Name Formatting. For Accounts, the logic can be added to Name Definitions using the Use Professional Suffix Logic to your Account Names. This option will produce the following formatting: 
| confirmed with business not to roll out medical suffixes for now |
Name Definitions - Contacts | No | Medical and Professional Suffixes can now be used in Name Formatting. For Contacts, the logic can be added to Name Definitions using the Use Professional Suffix Logic to your Contact Names. This option will produce the following formatting:
| confirmed with business not to roll out medical suffixes for now |
Recognition Option Offers | No | •Master Fundraising Campaign Added to Recognition Options •Historical Data check box added to Recognition Option Offers - Allows for adding into Offers Accepted without an Accepted Date A flag has been added to Recognition Option Offers to indicate that it is a historical record and the Accepted Date is not known. If checked, even if the Accepted Date is not filled in, the Offer will be counted in the rollup calculation for Offers Accepted. | we are not using Recognition Option Offer |
Summary Definitions | No | Summary Definitions can now be cloned. | Does not affect anything, it’s just cloning the record
|
Transactions | No | A flag has been added to Transactions to indicate that the Payment was made through a DAF. This is a system flag and should not be changed manually. |
|
Tribute Notification | No | The prompt "This Contact does not have a valid mailing address" will be displayed if a Contact is added to a Tribute Notification that does not have a valid address. The prompt can be dismissed and will not prevent the Contact from being added |
|
Defect Fixes | |||
Account | No | Account Name not updated with Decease utility To Reproduce Verify that the Institutional Suffix is using either Decease or d. Create a Name Definition for Accounts that uses the Institutional Suffix Create a Name Definition for Contacts that uses the Institutional Suffix Create or use an existing Account with one Contact Decease the Contact with the Decease utility The Contact name will update with the correct Institutional Suffix. The Account name will not update. If an edit is made to the Contact to uncheck the Decease flag, save, then open and recheck, the Account name will update. Expected behavior - Account name will update. | We are not using Institutional Suffix |
Activities |
| Back to Activity button not available to users with Read only access on Activity Reports, Activities, Events and Tasks. To reproduce: Create a permission set with only Read permissions to Activity and Activity Reports Add this permission set to a Read Only user with no other rights from the Profile for SF Events/Tasks Go to an Activity Report on an Account The Back to Activity button will be grayed out Expected behavior - Users with Read Only Access should have access to the button. In Fall '23, to access the button, users need: Read access to all fields on: Activity Report Activities Event Task Read access Account ID and Name on the Account object Read access to Account ID and Name on the Contact object |
|
Alternate Channels | No | Address does not update in Alternate Channels when City is changed on Account or Contact To reproduce: Ensure Add To Alt Channel and Archive Addresses are enabled On an Account with an Address in Alternate Channels, update the City on the Address from the Account The Address on the Account will update, but the copy in Alternate Channels will not Expected behavior - The Address on Alternate Channels will update v25 when changed the City, it’s supposed to be not updating? (although it would be a rare case of needing to change just the city unless it’s correcting a typo/data entry error)
| We do not have any account with linked address, though surprisingly, there are about 20k contacts who are linked address field but the thing is that that field has been hidden on contact page and therefore it’s misleading to use it.  |
Apex Classes | No | AreaUpdateAccountBatch Apex Job expecting value in both BillingPostalCode and AccountDefaultZipCode To reproduce: Ensure that there is an Account with a blank value in Permanent Add Zip/Postal Code (AQB__AccountDefaultZipCode__c). Run the AreaUpdateAccountBatch from the Apex Launcher The error "attempt to de-reference a null object salesforce" is thrown Expected behavior - the Apex Class will run without error | we don’t use this |
Change Verification Queue | No | Changes to check boxes on Accounts are not reflected correctly in Change Verification Queue To reproduce: Logged in as a User who is set to use the Change Verification Queue for Accounts and Contacts Change a checkbox on a Contact and Account (for example Do Not Contact) Logged in as a User who reviews the Change Verification Queue Changes in the record made in step 2 are not reflectred in the NEW DATA column Expected behavior - the changes are reflected in the NEW DATA column | we don’t use this feature |
Contact Utilities | No | Error "An Error occurred when creating the new Account" is thrown To reproduce Create a new user that has full access permissions sets to the Contact UtilitiesSharing settings for Account set to Private Create 2 new Accounts with a the new User that is different than the user that owns the other Accounts in the Org Joining 2 Accounts that have blank External Id on both Accounts You should receive an error "An error occurred when creating the new Account." | our accounts are not private |
Dues Batches | No | Default Entry Type is not used in Dues Batches To reproduce: Create a dues batch and set the Default Entry Type to something other than Check Go to batch items - the entry type will display Check Expected behavior - the Default Entry Type will be used v25 v26
Dues Payments throw an error if processed when the Default Designation for the Dues Batch is not set to the Designation of the Dues Pledge it is paying off To reproduce: Create a new Dues Batch Go to Batch Items Process a simple Pledge: save and close the Batch Create a new Dues Batch Go to Batch Items Attempt to enter a Payment for the Dues Pledge processed in Step 3: upon clicking 'Save', Error thrown "Error updating BatchItem Pledge Payment: You can only change the designation on the Batch Item Transaction" Expected behavior - Batch Item for Payment is saved v25
| We don’t really encounter such scenario. |
Engagement Scoring | No | Engagement Scoring reset throws 50000 Error Message on large data sets To reproduce, run the apex class Engagement Scoring Reset Batch from the Apex Launcher on a large data set Expected behavior - Job runs to completion without error | we don’t use engagement scoring yet |
Gift Batches (Smart Batch 1.0) | Yes | Add Transaction to Existing Gift - Gift Recognition Credits process incorrectly with this Entry Type To reproduce: Create a new Gift/Pledge Batch Go to Batch Items Select an Account that already has a Gift Set Entry Type to 'Add Transaction to Existing Gift' Process, save, and close the Batch Observe the GRCs created and updated for the updated Gift/Pledge record: a new row (per Contact) is processed, and the original row is updated with the new amounts from the Additional Transaction and the new rows sum up with the amounts from the original row, resulting in the Legal Credit % being greater than 100% Expected behavior - Gift Recognition rows are created correctly Updating the Account on a Batch Item does not Update the Contacts on the Gift Recognition Credit rows To reproduce: Enter a gift in Smart Batch and save Verify Batch Item Recognition Credits have been created for the Batch Item Edit the Batch Item and change the Account on the Batch Item and save View the Batch Item Recognition Credits - the Contacts are the Contacts from the original Account Close the Batch View the processed Gift - the gift will be on the correct Account, the Gift Recognition Credit rows will be for the Contacts on the original Account Expected behavior - Contact on the Gift Recognition Credits are updated v25 v26
| @Ana Simic not sure if we’ve raised this before but this one is a welcome fix. I’d recommend to check this on split legal credit as well, also with soft credit. |
Transactions | Yes | Third Party Payoff and Third Party Payment are both checked on a Soft Credit used to pay down a pledge when hard credit is voided and corrected To reproduce: Create a pledge with a single payment on an Individual Account Reduce the pledge on the Individual Account by making a hard credit gift from a Foundation and using Save and Add Soft Credit In a Gift/Pledge batch, use Void and Correct to change the Designation on the hard credit gift. The resulting Soft Credit transaction that is now being used to reduce the pledge on the individual will have both Third Party Payment and Third Party Payoff will be checked Expected behavior - Only the Third Party Payoff box should be checked v25 Pledge on individual after correction
v26 after correction
| It doesn’t look like Third Party Payment fields is on Transaction page. Not sure if we are using it, this fix is working as tested. @Yeng Sembrano maybe we can check if there are any data to fix retrospectively? |