-
Notifications
You must be signed in to change notification settings - Fork 3
Home
Allison Letts edited this page Sep 24, 2020
·
33 revisions
- Start with a Jamboard to collaboratively design/review an ERD
- Consider spinning up a scratch org to make it happen
- 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.
- 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
- 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
Currently tracking in Issue #6