2023-12-11 AQ Consultation Session 12

chatter and notifications

• it's about leveraging chatter to create automatic notifications for specific groups. Every time like a gift comes in or pledged payment has been paid on on the pledge.

• Priscila Tello-Vela to provide some guides/recommendations on how to setup chatter and notifications effectively

Pledge Approval Utility

• use LWC

• kind of like Portfolio Reassignment Utility which we are not using

• if we can attach the doco in the gift record, then that could potentially be surfaced into the LWC for the approver to refer to

• we still need to migrate historical receipts into SF which is still sitting in shared drive presently

• Salesforce storage is notoriously expensive

• the intent is to put everything in Jarvis.

• large part of our storage is on campaign members (we haven’t been able to purge them yet)

• Priscila Tello-Vela to send the office word documentation on pledge approval utility

Giving Summary

• because we're doing most aggregation in power. Bi. So if we can leverage the summary definition then we don't need to recalculate it in power BI. Then it can be visible in salesforce reports as well

• we can also use engaging scoring utility

• The more complicated you're giving summary gets. the more it is easier to do it with salesforce reports, and then extract the ids and populate the summary object (only for extremely complicated cases)

• Yeng Sembrano to provide Priscila Tello-Vela some actual use cases for giving summary (fields and objects we are calculating on)
• Priscila Tello-Vela to test giving summary on custom fields and revert back

LL Salutation

• what is the relationship between LL Salutation and Salutation

• if you have it in Salutation it won’t create in LL Salutation

• problem is our integration is not creating on LL Salutation (does not sync)

• we don’t want to restrict salutation because we don’t know what our integration will throw

• Priscila Tello-Vela to share LL Salutation doco

Challenged fund

• Priscila Tello-Vela to send the write up on challenged fund

LL Currency

• need to use on one batch per currency but you can also change the default on batch each time you will enter a different currency because the default is on the batch

• enter amount in donor’s currency

• mainly in grants space and also some major gifts

• the issue would probably be more about when we're paying pledge down. What we receive is the Australian.

• it stamps the currency exchange rate and the the converted amount in AUD

• you can’t change the exchange rate on batch item, it will wipe it out

• the use case is we would enter the pledge in original currency so that when we send pledge reminder in the original currency

• limitation of LL Currency is that you need to update the latest exchange rate then create the batch (an enhancement request already made so that it will look at the date of the gift and apply the corresponding rate on that date)

• if payment has higher rate, it will overpay that installment and flow over to pay the next

• there is a field called Total Pledge in Original Currency

• write off the remainder of pledge due to currency loss

• Modify our pledge reminder to read the original currency amount
• rommel.ngo to test LL currency batch when modifying gift, does it get the current rate or it copies the original rate

multiple receipt for a gift with multiple payment on same day

• work around is to enter them in separate batches

• receipt number is not legally required

• potentially we can just build the receipts on gifts and transaction and skip the receipting object. A conversation needs to happen with the wider audience.

Third party payment modification

• we do it in 3 steps, void the payment, modify the pledge, then add the payment back