Home

GAU Replacement Object

Work for 9/24

• Design/review an ERD: https://user-images.githubusercontent.com/45673708/94176033-1f5fb100-fe5d-11ea-9ca4-4fc87331f861.jpg
• Report charts for total expenditure and total allocation. Added another issue for the need for these rollups here: https://github.com/SFDO-Community-Sprints/OutboundFunds/issues/9

MVP Assumptions

• Sales Cloud with Opportunities as primary inbound money object
• want to create a scalable solution for orgs that use a different inbound money object (FUTURE)
• we will avoid creating master-details
• No replacement GAU object already in place
• You need to know how much money you have to give out before you start disbursements
• It's not a one-to-one (Bob gave a scholarship to Sally). We need to be tracking the path from Donor --> Funding Pool(s)/Program --> Funding Recipient
• This object would (for now) only be about connecting an opportunity to a funding program for MVP -- we're not worrying about campaigns, payments, etc.
• We're not providing plumbing to assign a fund to a funding program.

Design Planning

• we'll plan to create an opp lookup lookup partially so that it's not a problem later
• Whatever we do, installing the package would let you rewire so it's a template - unmanaged custom object that they created as a gau replacement
• scalable option eventually might be a set of default/assumed GAU allocations based on funding programs

Other questions

• could the Funding Program be the GAU if you're not in NPSP? For simpler implementations, yes, but it wouldn't work for more complex orgs.
• if a funding program is the parent, then being able to show what's in the hierarchy for the funding program would be nice.
• how can we design/document this so that we don't get asked "why isn't the funding program just the GAU"???
  • funding program right now is for applications, dollars to spend, etc.
• we don't link from GAU Expenditure back to Funding Program

Afternoon Discussions

• Connection between the fund and the funding program; in the past we have had this discussion and then decided that we don't need it.
• We need to revisit the historical notes to see why the team had decided not to create this connection.
• this would address the budget side of things
• it would have to be a many-to-many junction object
• most likely we will add it to both the NPSP extension and then Fund extension packages

Reporting Workbook

Currently tracking in Issue #6