Nonproft Base App
Back to Nonprofit Development Community
Contents |
About this Solution
This solution will serve as the base install for all nonprofit organizations.
Solution Details
Development Project
Live Demo
Template/Implementation Ideas
- This templates needs to be very simple with as few design intricacies as possible.
- Any customizations or workarounds included in this template must be made with the understanding that this is a base template to which managed packages can be added. Therefore, anything that is not necessary to be on the template and therefore available to everyone, should be moved in to individual managed packages.
Contacts and Accounts
- As a central assumption, all organizations that choose to use this as their base template will be agreeing to the design assumption of a person centric business model.
- The basic work flow and functional intention of this template will be contact management.
- The workaround for B to I will most likely need to be implemented at this level and be a flexible as possible. Best case scenario would be a simple way to "turn it off" at the beginning stages of implementation.
- Contacts are assumed to be constituents of the organization.
Custom Objects
- What are the best practices for deciding to create a custom object in an AppEx as opposed to trying to add a new Contact or Case type to the Base Template?
- There are significant problems to be worked out relative to managing the introduction of new categories of constituents via an AppExchange. For example, if a nonprofit that was doing fundraising and event management would need to constituent categories (Record Types) for both donors and event attendees. How would these new constituent types be introduced?
- Similar conflicts can happen with cases as when an appexchange introduces a new constituent type in to contacts. For Example, an organization that want to do case management, grant making and trouble tickets of some sort.
- Do any custom objects belong in the base template?