The pattern: identify the assessment use case, find the closest sample template, clone it, customize for org-specific needs, test, activate, iterate via versions. The samples save significant time; starting from scratch is rarely worth the extra effort.
- Identify the assessment use case
Sales qualification, customer onboarding, compliance intake, needs assessment, industry-specific. The use case drives which sample template to clone.
- Open Discovery Framework Sample Templates
Setup, Discovery Framework Setup, Sample Templates. Browse the available templates per industry and use case.
- Preview the closest-match template
Read through the questions, branching, and default mappings. Identify what fits your use case and what needs customization.
- Clone the template into the org
Click Clone. The customizable copy appears in the org's Discovery Framework template list.
- Customize questions, branching, and output mapping
Edit per org-specific needs. Map answers to org fields and custom objects; the mapping is what makes the assessment valuable.
- Test in a sandbox before activating in production
Walk through the assessment as a representative user. Verify branching, validate mappings produce the right field updates.
- Activate the customized template
The active version runs when users invoke the assessment. Subsequent improvements create new versions through the same edit-test-activate cycle.
Pre-built starting point per industry or use case.
Editable copy of a sample, customizable for org-specific needs.
Per-question mapping of answers to org record fields.
Iterative refinement through new template versions, like Flows.
Financial Services, Health Cloud, Public Sector industry templates with regulatory-aware content.
- Samples ship with default mappings that assume standard objects. Customization replaces defaults with org-specific mappings; skipping the customization produces assessments that collect data without downstream use.
- Industry samples need industry cloud licensing. Confirm the org has the relevant industry edition before assuming the sample is available.
- Cloning produces an editable copy; the original sample stays untouched. Customizing the sample directly is not supported.
- Active template versions run in production. New versions in draft do not affect users until activated; the version model supports iterative refinement without disruption.
- Test in sandbox before production activation. Mapping mistakes produce wrong field writes; sandbox testing catches them.