Ideas Captured from Sprint (20th, 21st Oct) - SFDO-Community-Sprints/AnimalShelterStarter GitHub Wiki

360 View for Animal Shelter

  1. Adoption
  2. Fostering
  3. Donations (NPSP?)
  4. Animal
  1. Assessments
  2. Movements
  1. Inventory
  1. Locations
  2. Medicine
  3. Reporting
  1. Contacts (Personas)
  1. Volunteer
  2. Adopter
  3. Foster
  4. Advocates
  1. Employees’ (internal staff)
  1. Director
  2. Transporting
  3. Animal Care
  1. Programs (PMM?) or Cases
  1. Cruelty Investigations
  2. Domestic Abuse
  3. Vet services provided
  4. Trainings
  1. Marketing (MC for NPSP?)
  1. Social Media engagement

Suggested Priorities:

  1. Continue to gather needs/use-cases from organizations/shelters
  2. Multi-Site Support
  1. Risk not being accessible to larger organizations without this support
  2. Could the sites be entered as Accounts the animals look up to? Internal Organizations vs. External Organizations. Could have account hierarchy with out of box functionality.
  1. Foster Functionality Enhancements
  1. Create a separate object or identifier on Contact/Lead record?
  1. Would allow proactive automation/matching. Match fosters to available animals or even programs/trainings based on foster/contact’s information
  1. Foster Process - external user journey flow
  2. Allow foster to update information online
  1. Adoption Flow Enhancements
  1. Allow external users to start adoption, submit application, upload files, etc
  2. Setting criteria for a given animal based on external user info to flag (ex. Animal A needs no children in the house).
  1. Document how other existing products can be used with animal shelter pack to get a full 360 suite of functionality
  1. Programs, Services delivered - PMM (free)
  2. Donations, Grants, etc - NPSP (free)
  3. Call Centres, Chat Bots - Service Cloud (paid)
  4. External User Flows - Experience Cloud
  1. Digital Experience Framework
  1. LWC Components to support external user flows
  1. Customer can drag and drop to build own sites
  1. Adoption application progress/process
  2. Available animals (images and details)
  3. Fostering application progress/process
  4. Donate page
  5. Can provide interests, experience, availability, locations, etc

Technical Considerations

  1. Convert Process Builders to Record-Triggered Flows
  1. Consider using before apex trigger for same-record updates (ex. Location trigger - sublow of Animal - Block Capacity Calculations)
  1. Consider replacing custom aura components (lightning datatable) with single related lists in page builder for Animal record page when Intelligent Related Lists is delivered (currently scheduled for Spring 22).
  2. Make decisions on global picklist vs. separate objects with regards to Animal Types and Animal Breed (high volume of options).
  3. Remove references to “%%%NAMESPACED_ORG%%%” in apex. Code in a managed package does not need to use the namespace to refer to other packaged components (fields, objects).
  4. “Animal Actions” object - what’s the benefit of having its own object vs. just using tasks and/or events with custom fields added to them?