Skip to content

Project Meeting Notes February 2022

Jump to bottom
samanthashain edited this page Feb 9, 2022 · 1 revision

Present:

Samantha Shain (notes), Cassie Supilowski, Eileen Knapp, Charles Thompson, Alissa Edwards, Cori O'Brien, Paul Prescod, Aaron Crosman, Junette Tan, Allison Letts, Jung Mun

Ice breaker: goal or aspiration (personal or professional)

Project leadership updates (Aaron):

  • our official structure: up until recently, we had 3 community leaders (Sam, Aaron, Cassie) and one SF staff liaison (Paul)
  • in Jan, we decided to enlarge the circle
  • Allison, Jung, said yes! Alisa TBD
  • we would like to have an annual leadership check-in in January
  • would like to have workstream leaders
  • interested in taking turns with mtg planning

Snowfakery updates (Paul):

  • evolving to do data generation AND data transformation
  • useful if you need CI, you are already using CCI flows,
  • "update" feature to allow you to pull down data and update records
  • Snowfakery 3.0 - eta Feb 24
  • Snowfakery now includes JSON schema
  • Backwards compatibility - in Snowfakery 3.0, dates will be internally stored as "date objects" and not "strings" - this will impact the outputs of formulas in ${{}} brackets. This may impact a few recipes but the vast majority of recipes won't change.
  • Paul has been working on this since "summer" in the NW hemisphere
  • back burner - ability to use VS code to return fields and metadata for a specific SF org

Mini sprint:

  • need to write blurb for Cori
  • need to plan onboarding session (Eileen, Sam, Allison). (resources: Barbara C, Melanie T from DLRS and Videography)
  • Social media - Cassie, Jung, Cori (Junette and Eileen to share on LinkedIn)
  • Tool Comparison matrix
  • Recipes based on use cases (this is different from making recipes just for the sake of making recipes)
  • Many recipes have parts but not all of what you need. Need to develop an index by S object or another way to combine recipes
  • Jung shared that she takes the API names of all of the fields for a custom object, comments out the formula fields, and then grabs the fields that are actually relevant to the template. Is there a way to do this with code? It's very difficult bc a vanilla scratch org has 800 s objects (not counting special industry clouds)

Useful projects to work on

  • Snowfakery demo videos (Jung working on this)

We contributed 44 pieces of community resources last year (2021!)

Clone this wiki locally