Solution Engineering

Document Technical Concept Explanations

A teammate asks how a Salesforce feature or approach works and gets back a written explanation they can read, share or build from. The usual result is a note or markdown file. Nothing changes in an org.

42 tasks
Method

How MeshMesh does it

  1. Looks up Salesforce developer documentation pages. Some pages it tried turned out not to exist as standalone pages.
  2. Reads any reference the user attaches in full, then summarizes it as an overview of modes, triggers, outputs and safeguards.
  3. For a template in an org, extracts the full Agent Script by intercepting network responses. It then analyzes each action's input and output schemas, maps how grounding works and gives customization examples.
  4. Writes a stage-by-stage conceptual breakdown of the feature. In one case it explained how Identity Resolution works in Data 360 so a developer could build a visualization.
  5. Saves the explanation as a downloadable markdown file in the workspace.
Products

Products and features it works with

Bars show how many of this capability's tasks touched each product.