2022 May Community Sprint

Sprint Team:

• Dar Veverka
• Shun Kosaka
• Richardson Handjaja
• Deanne Walters
• Trish Perkins
• John Castelloe
• Bhim Raj Mainali
• Melissa Hill Dees
• Jeremiah Olafisoye
• Rich Nevin
• Badr Laabad

Informational Links:

• Metecho Project
• GRMS Github
• Cori’s May Sprint Artifact Doc
• GRMS Trailblazer Group
• Screensteps doc

This is an open source and community data collection application solution originally created for a group of health workers in the Himalayan hills around Darjeeling India which is focused on providing affordable field survey capacity to nonprofits worldwide. This team is dedicated to bringing the current iteration of the app to the larger global nonprofit community and is in the process of joining our Open Source Commons program.

Installation Links:

We are testing the following new builds. Please use these links for install rather than the ones in the Wiki. Note you still need to use the Wiki for the Heroku install.

For Salesforce packages, Replace [MyDomainName] with your SF dev org’s domain name

• Salesforce app v11.03 - https://[MyDomainName].lightning.force.com/packagingSetupUI/ipLanding.app?apvId=04t5G000003RTLtQAO
• Sample Survey pack v1.0.3 - https://[MyDomainName].lightning.force.com/packaging/installPackage.apexp?p0=04t8c000001334cAAA
• Android v5 mobile app client - https://expo.io/artifacts/935abc37-5a59-44f6-9e09-35bd380a11dc
• iOS v5 mobile client - install via TestFlight. Please let Shun know your email address of the Apple account.

Day 1 - Wednesday, May 4th

GRMS Intro

• Project Intro & History
• Team Member Intros
  • Name, where from/at, new/returning, skills, random thing about you
• Tasks for Sprint
  • Testing the new builds
  • Testing the new mobile clients
  • Reviewing & updating documentation
  • App Exchange page work
• Scribe assignment
  • Trish for Documentation Room
  • Dar for Testing Room

Breakouts

• Main Room/Breakout 1 - Guided Installs & Testing New Builds
  • Dar Veverka
  • Melissa Hill Dees
  • Deanne Walters
  • Badr Laadbad
  • Andy Utkan
  • Shun Kosaka
• Breakout 2 - Documentation & Write ups
  • John Castelloe
  • Trish Perkins
  • Richardson Handjaja
  • Bhim Mainali
• Breakout 3 - Dev Room (Optional If Needed)

Install Feedback - Room 1

• GRMS missing on Metecho- no version when pulling an org - Shun & Jung
• Adding Survey Contact to layouts- auto dumped into System Info section. Note it needs to be moved. DONE (by Shun)
• Mobile client doesn’t like + signs in gmail addresses - Shun Question & Troubleshooting Documentation
• Create Integration User instructions need some work - DONE in SCREENSTEPS
• Need editable section on default survey layout - should go in the package
  • This is for use cases other than Home Care or Disaster Relief. The org using the app can decide what goes here, create fields, and sections.
• Mobile client - didn’t accept % in Auth0 password - Troubleshooting Documentation
• User field on User & Client Relationship - should have a Contact Type = Survey User filter here
• Client field on User & Client Relationship - should have a Contact Type = Survey Client filter here
  • I put both of these filters on these two contact lookups. I think we just need to add that to the post-install instructions.
  • Shun has added to base package but it’s not in a beta release yet - DV
• User Contact and Survey Contact fields on Field Survey object should have Contact Type lookup filters, like the User and Client Relationship object above.
• Related to the User/Client fields on the User & Client Relationship object. I understand the team previously changed from using Contact Record Types to a Contact Type picklist field. But by doing this, the Contact record’s related lists display both “Related Survey Users” and “Related Survey Clients” regardless of whether the contact is a survey user or a survey client. (Also two separate Field Survey related lists.) Alternatively, the Lightning record page for Contacts should be using Related List - Single components so visibility filters can be used based on the Contact Type picklist.
  • This is interesting, and I don’t know how to do that. Do you? Please help.
  • Richardson: Yes, I know how to do that. Can discuss on day 2.
• iPhone - any picklist field is crashing the client - IN QA
• Typo on mobile app Log In Settings instructions (at least in iOS) - “For exmaple" - RESOLVED

Survey Sample Pack Feedback

• “Name of HH Member” is unclear - is this the same as the “Respondent” name? Or the names of other members of the household that are not the Respondent?
  • If the latter, “HH Member Birthdate” is limited to just one birthdate when there can be more than one other household members.
• Contact Text Field on Sample Survey package- this is field type email and doesn’t make sense with that label. Folks will assume this is for texting since that was a choice for contact and put in a phone number.
  • This field should be removed altogether. They can text either to the person’s phone number or to his/her email.
• Contact Text Field on Sample Survey package- this is field type email and doesn’t make sense with that label. Folks will assume this is for texting since that was a choice for contact and put in a phone number.
  • Same as above
• Contact Method fields have an option for “Messenger” (I assume this is Facebook Messenger?), but there are no fields to enter Messenger details.
  • Good idea
• In a disaster relief survey, “Insurer Health” may need to be renamed “Health Insurer” to keep consistent with “Homeowner Insurer”.
  • Good idea.
• Who is the “you” in the field label “Name of Org You’re connected with”? The respondant
  • These are fields for Disaster Relief victims. There is a question which attempts to find out if the victim is already in touch with another org that is providing assistance. The You is the person being interrogated on the disaster situation.
• Survey record type is displayed on the list of unsynced/synced/all surveys. Would make sense to include it on the survey layout as well?
  *It was on Disaster Relief, and I put it on Home Care, but this needs to be part of the sample package.
• It seems not possible to edit a synced survey on a mobile app, is that OK ?
  • Will ask Shun if this can be changed
  • I think this is not in the cards. Once a survey is synced, it is sent to Salesforce, and distributed with flows out to the Contact Object. We don’t have the capacity to fix a mistake in a form all the way to the depths of Salesforce. That’s why we teach the Field workers not to sync until they are sure.

Mobile App

• Survey Date field is auto populated when creating a survey from a mobile app but it’s not the case when we create a survey from the backend(salesforce app). Is that OK ?
• Adding surveys NOT with the app would most probably be surveys that didn’t happen today, so the Survey Date field should be editable, but not prefilled.
• In the iOS application, when “HH Member Birthdate” information is populated, the date format is Mmm dd, yyyy (e.g. Aug 04, 1967). Is this dynamic based on region and device, or is there some configuration that would need to be done for users that don’t follow the same date format?Question for SHUN
• In the iOS application, I intentionally put too many characters in the first name field. When syncing it told me what data was over and the max character limit. However it did not tell me which survey the error was in.Question for SHUN

Report Back Day 1 - Richardson H.

• What project are you working on?
  • Grassroots Mobile Survey
• What have you accomplished today?
  • Most of the new participants were able to successfully install the survey managed package and the mobile app, both on Android and on iOS devices. Some testing is happening on both Android and iOS devices. We immediately identified a bug on the new iOS app. Also successfully tested new flows for the app.
  • The documentation team got through Install, Post-Install and Create Your First Survey chapters of the documentation. We also began responding to questions and comments from the testers. We made some changes based on their excellent and thoughtful feedback.
• What are your next steps?
  • Install and testing team will continue testing the newer iOS app for bugs. Deploy flows as part of package update.
• Next up: Heroku and Mobile App install documentation.

—-------------------------------------------------------

Day 2 - Thursday, May 5th

Main Room - Documentation & Discussion

• Richardson

• Trish

• Deanne

• John

• Dar (when not helping on installs)

• Bhim

• Badr

  • Need a Cori security weigh in!
    • What to do with Flows!
      • Risks to packaging flow - SF team have stopped packing these as much
      • Could go with a template only approach ← may be what other teams have done. Allows cloning, editing, adding updates in the package
      • Need to ask Jason Lantz - may be here for Sprint today; David Reed would also have info
      • May be a good approach to go with Documentation first and then a template or in sample pack
  • Review Heroku Install & Mobile Install Documentation
  • What Goes Where - Package vs. Documentation
    • Updates/Corrections to the base package
    • Updates/Corrections to the Sample Surveys package
  • Flows!
    • Documentation or package?
    • Discuss Andy’s Survey Client record creation flow features
      • Deanne - documenting & reviewing
  • Outstanding Issues that need some support!
    • Issue 62- review & finalize field names, descriptions.
    • Dar will work on this
  • AppExchange page
    • What’s needed and what do we have
      • Cori sending us a template/checklist
      • Long description, short description, title, technical documentation on functionality/process/coding, security checklist doc (prelim run through Checkmarx)
  • Technical Documentation & Items - Shun & Jung
    • Metecho status
    • Technical documentation status
      • Need this for AppExchange as well

Breakout Room - Testing & Guided Installs

• Dar (at times)
  • Beta v0.6.1 iOS Client ready for beta testing
    • Verify picklists now working
    • Retest surveys on iOS for any new bugs
  • Any new folks or folks still in progress on install - guided installs

To Do’s for AppExchange

• Talk to release team - MetaDeploy functionality
  • https://install.salesforce.org/products
  • Pre-install checklists
  • Post install task choices
  • Could we do a choice page like the GMM one?

Changes To the Base Package

• Survey Contact on User & Client Relationship object
  • Relabel related list (“Client Relationships” for example)
• Filters on the Survey Contact & User on the User & Client Relationships object
• Possible - Lightning Page for Contact w/single related lists & filtered visibility

Changes to the Sample Survey Package

• None

Items for Troubleshooting Documentation

• Trish’s Heroku Troubleshooting

• No + in emails for field workers

• No % sign in password for Auth0

• Rich Documentation Notes: (posted 5/8/22)

  • Overview: I read through and followed the instructions through a lens of our audience - especially those that could be new / green admins and even users without admin experience expected to follow these notes. In general, I’ve tried to group like concepts together, streamline language to match everywhere, and reduce the number of words. It’s not perfect by any means but hopefully helpful.
  • SECTION: Github - skipped!
  • SECTION: Install the Salesforce App

    • General Notes:

      • "App" vs "Package" - need to be consistent so as not to confuse a jr. admin
      • “Sign up for Dev Org” needs context - and include those instructions up top
      • Group like things together: like the best practice not in production first! language

    • First Subsection:

      • Remove: “Sign up for a Dev Org…” language, replace with something like the following to give more context to jr admins:

    • Before using the Grassroots Mobile Survey App, it's best practice to try this app out in a safe space, like a dev org, scratch org, trailhead playground, or a sandbox. Here are instructions on how to create a dev org. Skip ahead to Install the Grassroots Survey Package if you already have your test environment set up or are ready to install in production.

• Second Subsection:

  • [Headline]: Install the Grassroots Survey Package
  • Installing this package will install the Grassroots Survey app into your Salesforce instance, including custom fields, custom objects, page layouts, and language customization.
  • [Remove: The Grassroots Survey package… line - it’s redundant]

• Third Subsection: keep the sub-headline “Create an Integration User” * [sketched out copy rearranged for clarity:]

• The integration user is not actually a "real person" but a handshake with the technology outside of Salesforce, including the mobile app. You may already have an "Integration User" but we need our own, so let's create a new one called GSIntegration User.

• NOTE: I made the prepend “GS” to match the app name, as opposed to “My” which is too general. But: is “GS” clear enough?

  • [The language “ Your system admin can specify which of these restrictions should apply to your organization.“ is confusing to me. Won’t the person taking these steps be the admin? I’m not sure there is someone to escalate this too - therefore maybe the language needs to be either cleaned up to more specificity or… hmmm]
  • Next subsection: “Get the Security Token…”
    • Replace “Integration User” with the label used above (in my example it would be “GSIntegration User”)

• [The phrase “POST-INSTALL” is confusing… Maybe “INSTALL THE SAMPLE SURVEY” IS ITS OWN SECTION?]

HEROKU:

• Heroku App Setup [remove “Initial” - unless there is more Heroku setup later]
  • General comment: it feels like this section can get pretty confusing through the eyes of a new admin…
  • In the initial paragraph:
    • [Start with]
    • We have built an app in Heroku that helps your Salesforce instance connect with all your users’ mobile phones but only use one Salesforce license (which is the “GSIntegration User” we created in the last step.)
      • [then keep the rest except use the label “Grassroots Survey App” to keep things consistent]
      • [note: this concept of “one license” feels like should be some pre-information before starting the installation - meaning we tell users that they will need a license to use this app.]
  • “Manage Verification Methods” - this language was a little confusing to me through the lens of a new admin. No suggestions yet! Just calling it out…
• [end Rich feedback - note that it’s not fully comprehensive!!]

—--------

Report Back Day 2 - [Richardson]

• What project are you working on?
  • Grassroots Mobile Survey
• What have you accomplished today?
  • Tested a new release on the iOS client.
  • Discussed steps for security review by Salesforce.
  • Reviewed documentation for Heroku & Mobile App installs.
  • Addressed questions from the testing team.
• What are your next steps?
  • Identify items to include in the base package instead of telling admins to create them after installing.
  • Create a troubleshooting guide for common error messages.
  • Clean up usage of certain terminologies to improve clarity for beginner users.
• Any other details to share?(optional)
• Need to have continuing conversation about impact of Flows on security review and what information to put on the AppExchange page.