Salesforce AP-222 Dumps Questions Answers

Agentforce Public Sector provides the Public Complaint object specifically for constituent-reported concerns and the Case object for subsequent internal investigation and follow-up. This separation supports the requirement to maintain external complaint intake independently from the agency ' s internal investigative work.

A Public Complaint can represent information submitted through an Experience Cloud site by either authenticated or anonymous users. After intake, authorized staff can create or associate a separate Case to manage investigation activities, ownership, status, work assignments, findings, and follow-up actions. Salesforce ' s Public Sector common-layer architecture distinguishes constituent intake records from operational case-management records, allowing the agency to retain the original complaint while independently managing the investigation. Using Case record types for both purposes would collapse two distinct business concepts into one object. A custom complaint object would also duplicate functionality already supplied by the Public Sector data model and increase maintenance effort. The standard Public Complaint plus Case model therefore provides cleaner data separation, supports anonymous/public intake, and gives internal staff an appropriate record for managed investigation.

Study Guide References: Public Complaint; Case Management; Experience Cloud Complaint Intake; Investigative Case Management; Public Sector Common Data Model.

The standard architecture combines an OmniScript application form with Business Rules Engine. The OmniScript gathers the business information required to calculate the fee, such as authorization type, revenue, industry classification, or other regulatory attributes. The collected data can then be passed to Business Rules Engine for deterministic fee calculation.

Salesforce specifically documents using Business Rules Engine to calculate processing fees associated with Business License Applications. The documented configuration uses a Decision Matrix and Expression Set to determine an application fee based on information that a constituent enters in an OmniScript license application form. Decision Matrices are particularly appropriate when fee values depend on combinations of configurable business parameters. An Expression Set orchestrates calculations and matrix lookups and returns the resulting fee to the OmniScript. Salesforce confirms that Expression Sets and Decision Matrices accept JSON input from OmniScripts and return JSON output back to them. Implementing fee policy inside triggered Flows or Integration Procedures would place regulatory logic in a less appropriate layer. Integration Procedures are useful for orchestration and external integration, but Business Rules Engine is purpose-built for maintainable policy decisions and calculations.

Study Guide References: OmniScripts; Business Rules Engine; Decision Matrices; Expression Sets; Automated Application Fee Calculation; Licensing and Permitting.

The Licenses and Permits Experience Cloud site template is specifically designed for constituent-facing licensing, permitting, and inspection processes. Salesforce provides this template with preconfigured pages for assessing license or permit requirements, applying for licenses or permits, renewals, permits, complaints, applications, inspection history, and related constituent interactions.

Using this purpose-built template significantly reduces custom site development and ongoing maintenance. Public Sector also supplies dedicated components that can be added to the template ' s pages for licensing and permitting functions. These components support processes such as submitting applications, searching licenses and permits, renewing authorizations, and filing complaints. OmniStudio components such as OmniScripts can provide guided application experiences, while FlexCards can surface contextual information and actions. Maintaining these processes within a dedicated licensing-and-permitting site keeps the digital architecture aligned with the Public Sector product model rather than expanding a generic Help Center into a specialized regulatory application portal. OmniOut is principally used when OmniStudio experiences must run outside Salesforce-hosted experiences, so it is unnecessary for a standard Experience Cloud implementation.

Study Guide References: Licenses and Permits Experience Cloud Template; OmniStudio; OmniScripts; FlexCards; Constituent Digital Experiences.