Salesforce AP-222 - Salesforce Accredited Agentforce 360 for Public Sector Professional

Person Accounts allow Salesforce to represent an individual person using the Account data model rather than requiring the individual to be modeled as a conventional business Account with a separate Contact. Salesforce implements Person Accounts by combining Account and Contact behavior into a single record experience while retaining the underlying Account foundation.

This model is particularly appropriate in Public Sector because agencies commonly serve individual constituents as well as businesses. A private resident applying for a permit, license, benefit, or government service can be represented as a Person Account, while businesses continue to use Business Accounts. Salesforce confirms that enabling Person Accounts creates distinct Account record types for business accounts and person accounts. Therefore, the statement that Person Accounts do not support record types is incorrect. Person Accounts also cannot simply be disabled after activation. Salesforce states that enabling Person Accounts fundamentally changes the organization ' s data model and that the feature cannot be disabled once enabled. The model does not combine Opportunity and Contact fields. Its design combines Account and Contact characteristics to create a person-centric Account representation suitable for organizations that interact directly with individuals.

Study Guide References: Person Accounts; Public Sector Constituent Data Model; Account and Contact Model; Licensing and Permitting Constituents; Person Account Enablement Considerations.

Decision Matrices are the appropriate Business Rules Engine component when a licensing process must map a combination of defined inputs to a corresponding result such as an application fee. Salesforce defines a Decision Matrix as a lookup table containing user-defined input and output columns. At runtime, the matrix evaluates supplied input values, finds the matching row, and returns the configured output.

For a sporting-event licensing process, the inputs can represent attributes such as license type, event classification, location, capacity, duration, or other fee-determining criteria. The output column can contain the applicable fee. An Expression Set or OmniStudio process can invoke the matrix during application processing and use the returned amount to populate or calculate the application ' s fee. This design keeps regulatory fee schedules outside procedural automation. When the government agency changes a fee or threshold, administrators can update the Decision Matrix rather than modifying Flow, Process Builder, or custom code. Workflow Field Updates and Process Builder are general automation mechanisms and do not provide the structured multi-input lookup model that Business Rules Engine provides.

Study Guide References: Business Rules Engine; Decision Matrices; Licensing Fee Configuration; Expression Sets; Declarative Regulatory Calculations.

CRM Analytics for Public Sector provides a purpose-built analytics capability for government agencies that manage licenses, permits, inspections, cases, and related regulatory operations. Salesforce specifically provides an Analytics for Licenses, Permits, and Inspections template that can be used to create a preconfigured analytics application rather than building the analytical model from scratch.

The LPI analytics application includes prebuilt dashboards such as Compliance Insights, Executive Summary, Department Summary, and Account Insights. These dashboards enable agency users to examine regulatory activity, operational productivity, constituent outcomes, applications, inspections, licenses, and compliance trends. Because the scenario emphasizes quickly obtaining intelligent insights through pre-built templates, CRM Analytics for Public Sector directly addresses the requirement. Standard Salesforce Reports and Dashboards can provide operational reporting, but they would require more manual report and dashboard construction. Salesforce Einstein provides broader AI capabilities but is not the designated prebuilt LPI analytics solution described in the Public Sector configuration model. Current Salesforce releases also provide newer Tableau Next dashboard capabilities in applicable Agentforce for Public Sector editions, but the specific prebuilt analytics solution represented by the question is CRM Analytics for Public Sector.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Compliance Insights; Executive Summary; Public Sector Analytics Templates.

Administrator users responsible for creating and managing Public Sector analytics require both the CRM Analytics platform-level administrator capability and the Public Sector-specific analytics administrator capability.

CRM Analytics Plus Admin supplies the permissions required to administer CRM Analytics, including creation and management of templated analytics applications. Salesforce describes this prebuilt permission set as providing the administrative permissions for CRM Analytics Plus and associated application-management functionality. The administrator must also receive the Public Sector analytics administrator permission set represented in the options by CRMA for Public Sector Admin. Current Salesforce documentation identifies this Public Sector-specific administrative permission as TCRM for Public Sector Admin. Salesforce ' s setup procedure explicitly instructs administrators to assign CRM Analytics Plus Admin AND TCRM for Public Sector Admin to users who create and manage Public Sector analytics applications. The combination separates platform administration from industry-template access. CRM Analytics Plus Admin alone does not provide the full Public Sector-specific entitlement required by the LPI application, while the industry permission alone does not supply the necessary CRM Analytics platform administration rights.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Admin Permissions; CRM Analytics Plus Admin; Public Sector Analytics Admin.

Employee Experience and HR-service processes commonly use the Case object to represent sensitive employee requests, including HR, workplace, and employee-support matters. Because these cases can contain confidential personal or employment information, the appropriate baseline sharing model is to restrict access and then selectively grant it to authorized personnel.

Salesforce ' s Employee Concierge configuration explicitly sets the organization-wide default for the Case object to Private. This establishes the most restrictive standard access level and ensures that unrelated users don ' t automatically gain visibility into HR cases. Organization-wide defaults form the foundation of Salesforce record-level security. When Case is Private, the record owner and users who receive access through appropriate sharing mechanisms, queues, role hierarchy behavior, teams, or administrative privileges can access the case as configured. This supports least-privilege handling of employee information. Mirroring the organization chart into the role hierarchy could unintentionally widen access to confidential cases and does not itself secure HR data. Disabling approval processes has no direct relationship to record confidentiality. Likewise, the key security control required here is establishing Private OWD rather than relying on a hierarchy configuration as the primary protection.

Study Guide References: Employee Experience for Public Sector; HR Service; Case Security; Organization-Wide Defaults; Least-Privilege Record Access.

Inspection Action Plan Templates are associated with individual Visit records because the tasks, assessments, regulatory checks, and signatures are performed during a specific onsite inspection. Salesforce ' s current configuration guidance instructs administrators to create the inspection template with Target Object = Visit and an inspection execution Action Plan type. In current Salesforce terminology, this is represented as Assessment Execution; the question uses the corresponding Visit Execution terminology.

The template can contain Assessment Task Definitions, which group the assessment indicators that inspectors evaluate. Those indicators can be associated with regulatory codes, enabling the inspector to understand which legal or regulatory requirement corresponds to each checklist item. This preserves traceability between what is inspected and the regulation being enforced. Salesforce also allows a Signature Task to be added directly to the inspection Action Plan Template. The signature task can be marked required and used to capture acknowledgement at the completion of the inspection. Targeting Business License Application would be inappropriate because the Action Plan represents the work conducted during the physical Visit, even though that Visit originates from or relates to a Business License Application.

Study Guide References: Inspection Visits; Action Plan Templates; Visit/Assessment Execution; Assessment Task Definitions; Regulatory Codes; Signature Tasks.

Expression Sets use resources to hold inputs, outputs, constants, intermediate values, and other data required during Business Rules Engine execution. Within Expression Set Builder, the administrator opens Resource Manager and selects Add Resource to define the resource and specify its data type.

Salesforce ' s fee-calculation configuration guidance explicitly demonstrates this process. When creating variables for fee calculations, the administrator selects Add Resource, chooses Variable as the Resource Type, and selects Currency as the Data Type. Salesforce also documents Currency as a supported Expression Set resource data type, with standard numerical comparison operators available for use in rule calculations. This distinction is important because the data type belongs to the resource definition used by the Expression Set. A Decision Table can participate in the calculation and can contain supported column types, but it is not the location specified for defining an Expression Set resource. OmniScript controls the guided interaction, and Process Builder entry criteria are unrelated to Expression Set resource typing.

Study Guide References: Business Rules Engine; Expression Set Builder; Resource Manager; Add Resource; Currency Resources; Automated Fee Calculation.

Salesforce Knowledge combined with a public, unauthenticated Experience Cloud site provides the most direct self-service architecture for this requirement. Salesforce Knowledge centralizes permit and licensing guidance in managed articles, while Experience Cloud can expose approved Knowledge content directly to guest users. Salesforce explicitly supports making Knowledge articles available to unauthenticated users when the appropriate article visibility, guest-user access, and sharing configuration are established.

This architecture minimizes integration overhead because the agency does not need to maintain outbound API synchronization with a separate CMS or develop a Lightning Out implementation. It also avoids imposing an unnecessary authentication step on constituents who merely need general process information before starting an application. Articles can be updated centrally in Salesforce and surfaced immediately through the digital experience according to publication and visibility settings. An authenticated site is appropriate when information is constituent-specific or access must be restricted, but general licensing instructions, FAQs, prerequisites, and application guidance can be exposed publicly. This lowers call-center demand while preserving Salesforce as the authoritative content-management location.

Study Guide References: Experience Cloud for Public Sector; Salesforce Knowledge; Guest User Access; Public Self-Service; License and Permit Digital Experiences.

User Stories and a Functional Requirements Specification (FRS) are key implementation artifacts because they translate business objectives into requirements that can be designed, configured, tested, and accepted.

User Stories describe required behavior from the perspective of a particular persona or stakeholder. They help implementation teams break large public-sector processes into manageable requirements with clear outcomes and acceptance criteria. For example, a permitting implementation can contain separate stories for applicants, intake officers, inspectors, supervisors, and licensing administrators. The Functional Requirements Specification provides a more consolidated description of what the solution must accomplish. It documents functional processes, business rules, data requirements, integrations, security considerations, roles, and expected system behavior so that the implementation team has a controlled reference for solution design and validation. This aligns directly with Salesforce ' s official Agentforce Public Sector exam objectives. The exam guide expects consultants to document business needs and customer outcomes and, given a customer scenario, map and document the business process, personas, and requirements. A Marketing Plan concerns external promotion rather than solution requirements. A Budget Plan is part of project and financial governance but is not one of the two functional implementation documents identified in this context.

Study Guide References: Requirements Gathering; User Stories; Functional Requirements Specification; Personas; Business Process Mapping; Solution Design Documentation.

Decision Explainer provides the explainability framework required to expose how Business Rules Engine calculations and determinations were reached. After a prioritization Expression Set and its supporting Decision Matrix have been configured, the rule must be integrated with Decision Explainer so that execution metadata and decision details are captured. Salesforce specifically states that integrating Business Rules Engine with Decision Explainer makes business rules available so Public Sector reviewers can access decision logs.

The Decision Explainer Log History component must then be added to the appropriate application Lightning record pages. This component displays each decision ' s timestamp, Expression Set name, and version, and allows reviewers to inspect variables, values, and formulas that contributed to the determination. Finally, reviewers require the appropriate Decision Explainer access. Salesforce identifies Decision Explainer Service Access as the permission needed to use Decision Explainer entities. A custom Screen Flow or Apex trigger is unnecessary because the platform already provides native logging, explainability entities, and the Lightning component.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Decision Explainer; Decision Explainer Log History; Public Sector User Access.