Study guide
14.2 Discovery & Design Approaches and Solution Documentation
Salesforce Accredited Agentforce 360 for Public Sector Professional Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Overview, Architecture & Constituent Data Modeling
1.1 AP-222 Exam Blueprint, Passing Standards & Credential Overview 1.2 Public Sector Solutions Layered Architecture & Industry Common Layer 1.3 Person Accounts & Constituent Data Modeling
2 Chapter 2: Licenses, Permits, and Inspections (LPI) — Intake & Issuance
2.1 Regulatory Authorization Types & Application Intake 2.2 Business License & Permit Issuance, Conditions & Status Tracking 2.3 Application Reviews, Multi-Department Approvals & Renewals
3 Chapter 3: Inspections, Code Enforcement, and Compliance
3.1 Inspection Types, Action Plan Templates & Onsite Visit Execution 3.2 Regulatory Codes, Assessment Indicators & In-Field Checklists 3.3 Regulatory Code Violations, Enforcement Actions & Remediation Workflows
4 Chapter 4: Grants Management & Grantmaking Lifecycle
4.1 Funding Programs, Funding Opportunities (NOFOs) & Public Discovery 4.2 Grant Application Intake, Review Workspaces & Multi-Stage Scoring 4.3 Funding Awards, Disbursement Schedules & Post-Award Reporting
5 Chapter 5: Benefits Management & Assistance Programs
5.1 Benefit Programs, Benefit Schedules & Beneficiary Data Architecture 5.2 Discovery Framework Assessments & Question Versioning 5.3 Rules-Based Eligibility Determination & Recertification Lifecycle
6 Chapter 6: Employee Experience & Emergency Response Management
6.1 Public Sector Employee Experience & Workforce Operations 6.2 Emergency Response Management (ERM) Intake, Triage & Incident Dispatch 6.3 Rapid Resource Allocation, Volunteer Coordination & Contact Tracing
7 Chapter 7: Document Processing, Intelligent Automation & Reporting
7.1 Document Checklist Items, Content Management & Upload Portals 7.2 Intelligent Document Automation (IDA), the Document Workspace & the IDA vs. IDA/IFR Decision 7.3 Intelligent Document Reader (OCR with Amazon Textract) & eSignature Integration 7.4 OmniStudio Document Generation & Dynamic PDF Production 7.5 Public Sector Operational Reporting, Compliance Dashboards & CRM Analytics
8 Chapter 8: OmniStudio for Public Sector — Guided Intake & 360 Views
8.1 OmniScript Architecture, Step Design & Conditional Branching 8.2 Data Prefill Patterns, Context Passing & Save-for-Later 8.3 FlexCard Architecture, Constituent 360 Layouts & Action Frameworks
9 Chapter 9: OmniStudio Integration & Server-Side Processing
9.1 Data Mappers (DataRaptors) — Turbo Extract, Extract, Transform & Load 9.2 Integration Procedures — Action Chaining, Batching & Error Handling 9.3 External API Integrations, HTTP Actions & Named Credentials
10 Chapter 10: Business Rules Engine (BRE) & Dynamic Fee Calculation
10.1 Expression Sets — Calculation Steps, Formulas & Versioning 10.2 Decision Tables & Decision Matrices for Policy Decisioning 10.3 Dynamic Fee Schedules, Calculation Procedures & Regulatory Pricing
11 Chapter 11: Experience Cloud Citizen Portals & Service Console
11.1 Public Sector Experience Cloud Site Templates & Citizen Self-Service 11.2 Guest vs. Authenticated User Journeys & Identity Verification 11.3 Multilingual Localization, Custom Labels & Translation Workbench 11.4 Public Sector Service Console, Workspace Tabs & Omni-Channel Routing
12 Chapter 12: Security, Compliance, Government Cloud & Best Practices
12.1 Data Security, Org-Wide Defaults (OWD) & Sharing Architecture 12.2 Government Cloud Tiers, FedRAMP & DoD Compliance 12.3 Salesforce Shield, Field Audit Trail & Platform Encryption 12.4 Declarative-First Strategy, Process Library & Deployment with IDX Workbench
13 Chapter 13: Agentforce & AI Innovation for Public Sector
13.1 Agentforce Architecture, Agent Builder & Public Sector Agents 13.2 Topic Definitions, Instructions, Actions & CRM/Data Cloud Grounding 13.3 Einstein Trust Layer, Guardrails & Responsible AI Governance
14 Chapter 14: Discovery, Requirements & Solution Design
14.1 Documenting Business Needs, Agency Value & Vision for Desired Outcomes 14.2 Discovery & Design Approaches and Solution Documentation 14.3 Mapping Business Processes, Personas & Requirements
15 Chapter 15: Org Setup, Data Management & Integration Governance
15.1 Setting Up an Org for Agentforce Public Sector 15.2 Data Management Strategy, Data Quality & Integration Governance
14.2 Discovery & Design Approaches and Solution Documentation
Key Takeaways Explain This Topic AI
Domain 3 opens with two paired objectives: recommend the best approach to discover and design the optimal solution, and then design and document that solution highlighting implementation best practices.
Public sector discovery is constrained by procurement: the statement of work, appropriation period, and change-order process are fixed before the first workshop, so the approach must fit the contract vehicle rather than the other way round.
Salesforce ships the Public Sector Process Library of pre-built process templates; a fit-gap discovery against those templates is faster and lower-risk than eliciting every requirement from a blank page.
Documented outputs that matter on this exam are the capability fit-gap, the object and data model map, the process and persona inventory, the integration register, and the decision log with rationale.
Never customize a Process Library template in place — clone it into the customer's own version so the reference asset survives upgrades.
Last updated: September 2026
14.2 Discovery & Design Approaches and Solution Documentation
Exam Focus: Two of the seven objectives in the 19%-weighted Implementation Strategies domain are about method rather than product: "recommend the best approach to discover and design the optimal solution" and "design and document the Agentforce Public Sector solution highlighting solution implementation best practices." These items read like generic consulting questions but they are not — the correct answers depend on facts specific to Public Sector Solutions, above all the existence of the Process Library and the standard PSS data models. Discovery that ignores what ships out of the box is the wrong approach, and the exam scores it that way.
What Makes Government Discovery Different
Three constraints reshape the method before a single workshop is booked.
1. Procurement fixes the shape of the engagement. The statement of work was written and competitively awarded before the team assembled. Scope changes require a formal change order, sometimes a contract modification, occasionally a re-bid. An approach that assumes freely renegotiated scope is unusable. The practical consequence: put more rigour into defining the phase boundary up front , and keep a disciplined register of items that fall outside it.
2. Appropriations fix the clock. Funding is often authorized for a fiscal year and can lapse. "We'll get to that next quarter" may mean "we'll get to that with money that no longer exists." Sequencing must front-load the outcome the funding was appropriated for.
3. The requirement is frequently the law. Eligibility rules, statutory deadlines, records-retention periods, and public-notice obligations are not stakeholder preferences to be traded off. Discovery must separate statutory constraints (non-negotiable, cite the source) from policy choices (agency discretion) from preferences (negotiable). Conflating them is the most common discovery error in the sector, and it produces designs that either over-engineer optional behaviour or under-serve a legal obligation.
Recommended Approach: Fit-Gap Against the Process Library
Because Public Sector Solutions ships pre-built data models and pre-built processes, blank-page requirements elicitation is both slower and riskier than a fit-gap. The Salesforce-aligned approach runs in this order:
Stage Activity Output
1. Orient Read the statute, strategic plan, audit findings, and prior system documentation before workshop one Constraint register with sources
2. Demonstrate Show the relevant standard capability — Licenses/Permits/Inspections, Grants, Benefits, Emergency Response — and the applicable Process Library template Shared vocabulary; stakeholders react to something concrete
3. Fit-gap Walk the agency's real process against the standard capability, marking each step fit / configure / extend / gap Capability fit-gap matrix
4. Model Map agency entities onto standard PSS objects; identify genuinely missing attributes Object and data model map
5. Decide Resolve each gap through the declarative hierarchy, recording why Decision log
6. Sequence Group into releases aligned to the appropriation and the mission outcome Release plan with explicit non-goals
Why demonstrate before eliciting
Asking a licensing supervisor "what are your requirements?" produces a description of the system they have. Showing them BusinessLicenseApplication , an Action Plan for required review steps, and a Process Library template for professional licensing produces a description of the difference between what they have and what they need — which is the only part the project has to build. It also prevents the most expensive failure mode in the sector: rebuilding a standard object as a custom one because nobody realised it existed.
The Process Library rule
Salesforce delivers the Public Sector Process Library : production-ready process templates (professional licensing, food-service permitting, building permits, grant application review, and others) bundling OmniScripts, Data Mappers, Integration Procedures, document checklists, and rules. The best-practice rule is absolute and testable: clone the template into a customer-specific version and modify the clone. Editing the delivered template in place destroys the reference asset and creates an upgrade conflict the agency will pay for later.
Choosing a Delivery Shape
Approach When it fits a public sector engagement Risk to manage
Iterative, program-by-program (recommended default) The agency runs several distinct programs; one can go live and prove value while others are designed Requires agreement that phase 1 is genuinely narrow
Single big-bang cutover Legacy contract expires on a fixed date; no parallel run is possible Highest risk; demands a full data-migration rehearsal and a real rollback plan
Pilot in one department or jurisdiction Multi-county or multi-agency rollout where local practice varies Guard against the pilot's local practice hardening into the enterprise design
Externals-first The mandate is constituent-facing (self-service, portal access) Staff-side change management gets neglected; schedule it explicitly
Iterative delivery is the default recommendation on the exam because Public Sector Solutions is modular by construction: LPI, Grants, Benefits, and Emergency Response are separable, and the platform's three annual releases reward getting a narrow capability into production early.
The Documented Design: What Actually Has to Exist
"Design and document the solution highlighting best practices" has a concrete answer. These are the artifacts:
Capability fit-gap matrix — every process step marked fit / configure / extend / gap, with the resolution for each gap.
Object and data model map — agency entity to standard PSS object, with the fields added and why. This artifact is what stops a second team from inventing Permit__c next to BusinessLicenseApplication .
Process and persona inventory — the processes in scope and who performs each step (developed in section 14.3).
Automation design — which OmniScripts, FlexCards, Data Mappers, Integration Procedures, expression sets, decision matrices, and Action Plan Templates exist, and what each is for.
Integration register — every external system, the direction of flow, the volume, the timing (real-time or batch), the authentication method, and the system of record for each field.
Security and sharing design — org-wide defaults, role hierarchy, sharing rules, permission sets and permission set licenses, guest-user access, and identity approach.
Decision log — every significant choice with the alternative considered and the reason. In government engagements staff turn over and administrations change; the decision log is what prevents a successor team from unpicking a design they no longer understand.
Non-goals — written down, agreed, and dated.
Highlighting best practices in the documentation
The documentation should not merely record what was built; it should record why it is the maintainable choice . The recurring best practices worth stating explicitly are: standard PSS objects before custom objects; declarative automation before Apex; Business Rules Engine for any rule a policy owner may need to change; cloned Process Library assets rather than edited originals; and configuration that a successor administrator can read without a developer.
- 💡 Real-World AP-222 Exam Scenarios & Case Analysis
- Scenario 1: A Discovery Approach Recommendation
A county with five regulatory departments — building, health, fire, business licensing, and environmental — has awarded a fixed-scope contract to modernize permitting. Each department describes its process as unique. The appropriation covers 14 months. The partner must recommend a discovery and design approach at kickoff.
What is the right recommendation?
Run a fit-gap against the standard LPI capability and the relevant Process Library templates , department by department, rather than five parallel blank-page requirements efforts. The departments will discover that most of what they call unique is the same lifecycle with different regulatory codes, fee schedules, and review steps — which is exactly what RegulatoryAuthorizationType , RegulatoryCode , expression-set fee rules, and Action Plans are designed to vary.
Sequence iteratively : take one department live inside the appropriation period, then apply the proven pattern to the rest. This protects the outcome against a lapsed appropriation.
Separate statutory constraints from local practice in the constraint register, because the genuine differences between departments are almost always statutory.
Record the phase boundary and non-goals in writing, since the fixed-scope contract makes later scope changes expensive.
Scenario 2: The Template Customization Question
An implementation team finds that the delivered Process Library template for food-service permitting matches the county's process except for two additional inspection steps and a different fee formula. A developer proposes editing the delivered template directly "so there is only one version to maintain."
What should the architect direct?
Clone the template into a customer-specific version and make the two changes there. Editing the delivered asset in place forfeits the reference copy and creates conflicts when Salesforce updates the library.
Implement the additional inspection steps as Action Plan items rather than as new custom objects, and the fee difference as a Business Rules Engine expression set so the county's finance owner can revise it when the fee ordinance changes.
Record both decisions, with their alternatives, in the decision log — this is precisely the kind of choice a successor team would otherwise reverse.
Scenario 3: Documentation Handover
Twelve months after go-live, the agency's original project sponsor and lead administrator have both left. A new administrator asks why constituent records use Person Accounts and why eligibility logic lives in expression sets rather than in Flow.
What artifact should answer that, and what does its absence cost?
The decision log , supported by the object and data model map . Person Accounts are a one-way, org-wide enablement, and expression sets were chosen so that a policy owner could version an eligibility rule without a release; both are decisions a newcomer would otherwise be tempted to reverse.
Without that record, the successor team re-litigates settled architecture, and in the Person Accounts case may attempt something that cannot be undone. This is why the exam treats documentation as an implementation best practice , not as project overhead.