2023 May Sprint

Attendees:

• Emily Miller ([email protected])
• Jordyn Jaffer ([email protected])
• Ben Mozenter ([email protected])
• Jung Mun ([email protected])
• Juan Victoriano ([email protected])
• Heeyeon Park ([email protected])
• Abasi Aniton ([email protected])
• Sean Forde ([email protected])
• Andrew Wilson ([email protected])

Notes:

1. Flow Ideas
   1. Case Load Migration Flow: Screen flow to migrate an old field workers relationships to a new field worker who has replaced them. a. Useful if you want to track which specific field worker is completing surveys and it’s important to maintain that record. Otherwise you can just give the new field worker the login information to the generic field worker record.
   2. Create Relationship From List View Flow: Flow to mass assign survey clients to a field worker from the contact list view. a. Initially caused an error when the contact type wasn’t set to Survey Client. For now, it’s skipping those use cases. But should consider either giving that feedback to user or auto setting those contact types to Survey Client (as long as they’re not a field worker).
   3. A flow related to creating a follow-up survey automatically? Maybe for initial surveys that require out of schedule repeat visits?
   4. Attendance Flow:
      1. Automatically create and sync a list of survey contacts (attendees) to a field worker (teacher) to be able to have class attendees to be determined by another existing object (ex: contacts registered for a class in an Event object).
      2. Field worker is just a contact email and password. So for events you could set it up to have field workers be event1, event2, and event3. That way you can pre-set up different attendance groups for different events and just have the field worker login to different events depending on the class
   5. Use Cases for “Disaster Relief” Field Survey record type:
      1. Record-Triggered Flow that creates Cases depending on the different values that are inputted in the Priority of Needs” field
         1. Using the “Priority of Needs” field - parse out how many different Cases would need to be created
            1. I.e. If client inputs “Housing, Food, Medical” in the field, we can create formulas within the Flow to segment the priorities out to ensure the order of the Cases to creat
         2. Use a Custom Metadata Type object to map the different priorities to either Case Type values or Case record Types
            1. This allows us to provide a few examples but will let the customer be able to easily customize their process without having to edit the Flow too much
      2. Record-Triggered Flow to create a task to reach out to the Organization that the client inputs in the “Name of Org You're Connected With” field
         1. Within the Flow include a Get Records element to check if the Organization is already an Account record within Salesforce or if we need to create a new record for it
      3. Record-Triggered Flow to create a task to reach out to the Contact that the client inputs in the “Need to contact anyone outside the HH?” field
   6. Use Case(s) for “Homecare” Field Survey record type: 8. Record-Triggered Flow that creates Cases for each of the following fields if they are populated: 4. “Overall Health” and/or “Mental Health” have a value of “Poor” 5. “Nutrition Advice Needed?” checked TRUE 6. “Food Delivery Assistance Needed?” checked TRUE 7. “Financial Support Needed?” checked TRUE
2. Sample survey use cases
   1. Equipment checks - solar check a. I as a “checker” will go and take notes on the status of multiple equipments (solar panels, drains, etc) b. Equipment = “client”
   2. Trail logs a. I need to and take measurements of
   3. Rentals a. List equipment available for rental b. Date selection: select rental dates c. Picklist: rental reason d. Approval for rental?
   4. Attendance for events / classes a. QR codes
   5. Census a. Case worker b. Clients to visit
   6. Game scorekeeping a. Volunteers at a school are helping evaluate student projects (or sports games) in the gymnasium. Each volunteer is assigned to evaluate pre-assigned teams on a number of criteria.
      1. Volunteers = Field Worker 2. Teams = Client b.
3. Field Worker “CONTACT” =
   1. Case worker
   2. Event
   3. Classes
4. Data ideas
   1. Enhance data caching for mobile device, making it configurable by admins by choosing which fields will sync from the survey custom object
   2. Survey statuses to enable incomplete answers and partially prefilled surveys to be available in mobile
   3. Unstructured data to create dynamic surveys
   4. Pushing changes made to the the survey record in Salesforce to the mobile app to keep sync (could be included in 4.a)
   5. Support for all Salesforce field types
5. Miscellaneous
   1. Branding, let organizations add a logo
   2. Pushing page layouts sync
   3. Setting for sync on wi-fi only or wi-fi on cell data as well and automatic sync when either is detected
   4. Look into Account Lookup - would this pull be too large? Need a way to designate which to sync?

Report Back

What we did

• Super charged our marketing!
  • Personas
  • New slide deck - more focused on nonprofit users and their needs, unique value prop
  • Relevant global stats for why the app is needed
• Bug Fixes
  • Permission set issue for sample survey package
  • Tracing React Native bug cause- found potential cause! Worked on troubleshooting it
• Flow
  • First version of mass assigning field workers from a Contact List View - launching flow from a button to set the records up
  • Screenflow to mass reassign records/clients to another field worker or copy them to assign to multiple field workers.
  • Record-Triggered Flow for specific Disaster Recovery use case to create a Task for Field Worker to reach out to other organization that client specifies in survey for extra information
  • Wrote up ideas for potential use cases for the “Disaster Recovery” and “Homecare” Field Survey record types
• UX
  • Worked on test installs
  • Brainstorm enhancements to mobile app
• Use Cases
  • Brianstormed additional uses
  • Brainstormed flow ideas