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

The Analytics for Licenses, Permits, and Inspections template performs a data compatibility check before creating the analytics application. Salesforce requires the Public Sector org to contain source records from the LPI operational data model so that the template can build its datasets and dashboards.

Salesforce ' s current data-requirements documentation identifies Visit as one of the supported source objects used by LPI analytics, along with Business License Application, Individual Application, Public Complaint, and Regulatory Transaction Fee. If the org lacks qualifying source data, the template returns an error during application creation and instructs the administrator to add the required data before trying again. Among the choices, missing Visit data is the relevant operational-data problem associated with the inspection portion of the analytics application. Visits represent actual inspection activity and are therefore central to metrics such as inspections performed, inspection volume, and related operational trends. Violation records, active Action Plan Templates, and Person Account enablement are not listed as the prerequisite represented by this compatibility-check scenario.

Study Guide References: CRM Analytics for Public Sector; Analytics for Licenses, Permits, and Inspections; Data Requirements; Visit Object; Analytics Compatibility Check.

A secure external-user sharing model starts with Private external organization-wide defaults. Salesforce explicitly recommends configuring external OWD as Private whenever possible so authenticated Experience Cloud users cannot see records that they do not own or that have not otherwise been shared with them.

After establishing this restrictive baseline, Sharing Sets provide the controlled mechanism for granting external users access to the particular Accounts, Cases, Contacts, applications, and other records associated with their own Account or Contact relationships. Salesforce specifically documents this pattern for external and high-volume community users. This design follows least privilege: nothing is exposed by default, and the site user receives only the application and service records required for their own interaction with the agency. Traditional sharing rules can be useful for external users with roles, but they are not the universal mechanism for high-volume Experience Cloud users. Sharing Sets are purpose-built for these relationship-based external access scenarios. Hidden is not an available organization-wide default record-access level. Salesforce documents external access values such as Private, Public Read Only, Public Read/Write, and Controlled by Parent where applicable.

Study Guide References: Experience Cloud Security; External Organization-Wide Defaults; Sharing Sets; Customer Community; Grants Application Security.

The standard Hierarchical View component is specifically designed to display multi-level related Public Sector records in a single structured view. Salesforce describes Hierarchical View as a Lightning web component that presents cascading relationships and allows users to avoid repeatedly navigating through individual related lists and record tabs. It can display up to four levels of related records.

For an Account, Salesforce provides a directly relevant configuration pattern. The first level can display Business License Applications, the second level associated Visits, the third level Regulatory Code Violations, and the fourth level Violation Enforcement Actions. This precisely matches a scenario in which reviewers want to start from an Account and understand its inspection and compliance history. The component supports standard Public Sector objects including Account, Visit, Inspection Assessment Indicator, Regulatory Code Violation, Violation Enforcement Action, and several other regulatory objects. It can therefore provide the requested multi-level visibility without requiring a custom UI component. Although Hierarchical View is technically implemented as a Lightning web component, the appropriate configuration choice is the named Hierarchical View component, because Salesforce supplies and supports it specifically for this use case. Building a generic custom LWC, Aura component, or installing an AppExchange component would add unnecessary development and maintenance.

Study Guide References: Hierarchical View; Account Unified View; Visits; Regulatory Code Violations; Enforcement Actions; Public Sector Record Relationships.

Business Rules Engine (BRE) is designed for high-volume, policy-driven decisions in which applications must be evaluated against defined conditions and consistently classified, qualified, prioritized, or assigned calculated outcomes.

BRE separates business policy from procedural automation through Decision Matrices and Expression Sets. Decision Matrices store structured rule tables, thresholds, and output mappings, while Expression Sets orchestrate calculations, conditions, matrix lookups, and final decisions. Salesforce specifically documents Business Rules Engine for determining applicant eligibility and benefit amounts based on defined criteria such as income and household size. This architecture is appropriate for grant qualification because administrators can change eligibility thresholds or decision criteria declaratively without rewriting Apex. The rules can also be tested before activation, versioned, and integrated with Decision Explainer when reviewers need transparency into why a particular application received a result. Flow is well suited to process orchestration, but it is not the specialized decision-rule framework represented here. Apex Trigger would require custom development, and Process Builder is not the preferred architecture for complex policy evaluation.

Study Guide References: Business Rules Engine; Decision Matrices; Expression Sets; Grant Eligibility; Application Qualification; Declarative Decision Automation.

Public Sector Case Analytics is designed to provide prebuilt analytics for case-management performance, including case-resolution duration, workload, historical trends, case-owner activity, and service effectiveness. The decisive requirement is that Bobahaven has not historically tracked case duration and wants ongoing trend analysis without introducing unnecessary customization.

Salesforce explicitly documents that when an organization doesn ' t have a field that tracks case duration, Public Sector Case Analytics uses its own CRM Analytics formula. For closed cases, the calculation uses the case opening and closing dates; for open cases, the current date is used. Business-hours duration calculations can also be incorporated when configured. The application ' s prebuilt dashboards provide metrics such as average time to close and historical case-status duration, making it suitable for comparing current and prior operational performance. Creating a new custom field would only begin collecting duration prospectively and would add configuration overhead. A standard report with a custom formula also lacks the breadth of the prebuilt analytical model. Leveraging Public Sector Case Analytics therefore minimizes customization while supplying the required historical and ongoing trend analysis.

Study Guide References: Public Sector Case Analytics; CRM Analytics; Case Duration Metrics; Case Overview; Historical Case Analytics.

The appropriate design combines authentication, bot protection, and restrictive external record access. Experience Cloud allows individual pages to be configured as Requires Login, which prevents unauthenticated visitors from accessing those pages even when other portions of the site are publicly available. Grant application OmniScripts should therefore be placed behind authenticated access when they collect or expose constituent-specific information.

CAPTCHA or reCAPTCHA adds automated abuse protection by distinguishing legitimate human submissions from bots. Salesforce documents reCAPTCHA implementations for Experience Cloud scenarios specifically to prevent automated or fraudulent form submissions. The external organization-wide default for sensitive application records should also be Private. Salesforce recommends keeping external OWD settings Private whenever possible and then opening access only through controlled sharing mechanisms. With Private external access, authenticated external users cannot automatically see other constituents ' records. A public application-reference search page would risk unnecessary information exposure and does not prevent form abuse. The combination of authentication, CAPTCHA, and restrictive sharing implements defense in depth for constituent application data.

Study Guide References: Experience Cloud Security; Requires Login; CAPTCHA/reCAPTCHA; External Organization-Wide Defaults; Grant Application Privacy; OmniScripts.

Partner Central is the Experience Cloud template designed for partner and channel-management scenarios. Salesforce specifically identifies Partner Central as supporting lead distribution, lead monitoring, deal registration, partner onboarding, channel programs, and collaborative marketing capabilities. Salesforce documentation states that organizations can use Partner Central to implement lead distribution and deal registration and manage channel-sales relationships without constructing those functions from the ground up.

Deal registration is particularly relevant because Partner Central includes predesigned components and processes for partner-submitted deals, including Quick Create capabilities, lead and deal list views, approval workflows, and channel-conflict management. The template also supports partner recruitment and onboarding as well as marketing initiatives such as campaigns and market-development activities. Help Center is primarily intended for customer self-service and knowledge delivery, while Customer Account Portal focuses on customer account interaction. Neither is optimized for partner relationship management and channel-selling workflows. Partner Central therefore aligns directly with the agency ' s requirement to manage external associates as channel partners.

Study Guide References: Experience Cloud; Partner Central; Partner Relationship Management; Lead Distribution; Deal Registration; Channel Marketing.

Customer Community is designed for high-volume business-to-consumer Experience Cloud implementations in which very large populations of external users require access to selected Salesforce functionality. Salesforce specifically documents that Customer Community licenses can support 100 million users, whereas Customer Community Plus supports substantially fewer users because it includes capabilities such as roles and more extensive sharing functionality.

Salesforce also classifies Customer Community users as high-volume community users. These users do not receive Salesforce roles, which avoids the role-hierarchy calculation overhead that would become impractical at very large scale. This architectural characteristic is particularly important for public-sector portals serving millions of residents, customers, borrowers, or other external constituents. Partner Community is oriented toward business-to-business partner relationship management and access to sales-oriented capabilities. Channel Account licensing is also targeted toward partner/channel scenarios rather than massive constituent-facing portals. Customer Community Plus adds reporting, dashboards, roles, and standard sharing features, but those features increase the complexity and supported-user considerations and are unnecessary when the dominant requirement is extreme external-user scale.

Study Guide References: Experience Cloud Licensing; Customer Community; High-Volume External Users; Customer Community Plus; Public Sector Constituent Portals.

Salesforce ' s Grants Management installation requirements include the appropriate Grants Management entitlement together with Customer Community Plus Login licensing, Lightning Experience, Digital Experiences, My Domain, and Chatter. Salesforce explicitly lists Customer Community Plus Login, Lightning Experience, and Chatter among the package prerequisites.

Customer Community Plus is important because a grantmaking portal generally requires richer authenticated external-user capabilities than a basic high-volume customer portal. Grant applicants need controlled access to funding requests, requirements, application records, and related processes. The Grants Management implementation can also establish a grantseeker profile and sharing configuration for those users. Lightning Experience is required because Grants Management and its modern application components operate within the Lightning platform. An organization whose staff still work in Salesforce Classic must therefore transition the relevant users to Lightning Experience before adopting the solution. Chatter is also a prerequisite because Grants Management includes collaboration-dependent functionality. Web-to-Lead does not provide the grant-application architecture, and basic Customer Community licensing does not satisfy the package ' s specified portal licensing requirement.

Study Guide References: Grants Management Installation; Grants Management Prerequisites; Customer Community Plus; Lightning Experience; Chatter; Grantseeker Portal.

A standardized eligibility and prioritization solution requires three complementary layers: structured applicant intake, declarative rule data, and executable decision logic. An OmniScript provides the guided application experience through which the grant seeker supplies the information required for eligibility assessment and prioritization. OmniScripts support multi-step questions, validations, conditional presentation, and integration with downstream rule processing.

A Decision Matrix stores decision data such as thresholds, categories, eligibility conditions, or scoring mappings. An Expression Set orchestrates the logic: it consumes application data, invokes the appropriate decision matrices, evaluates expressions, and returns eligibility or prioritization results. Salesforce ' s Business Rules Engine architecture uses Decision Matrices and Expression Sets together for declarative decision processing. A closely related Public Sector eligibility workflow is explicitly configured by customizing an OmniScript, creating a Decision Matrix, building an Expression Set, and then activating the experience. This architecture separates frequently changing policy data from the constituent-facing form and from executable rule orchestration, which improves maintainability and auditability. Web-to-Lead is designed to capture leads, while Web-to-Case creates service cases. Neither provides the purpose-built guided application and Business Rules Engine integration required for eligibility-based grant prioritization.

Study Guide References: OmniScript Designer; Business Rules Engine; Decision Matrices; Expression Sets; Grant Eligibility and Prioritization.