Accredited Professional Certification AP-222 Full Course Free

The native Public Sector design combines an OmniScript application form with Business Rules Engine . Salesforce explicitly documents this architecture for automatically calculating processing fees associated with business license applications. Business Rules Engine uses Decision Matrices and Expression Sets to determine fee amounts from multiple input criteria, while the OmniScript captures those constituent inputs.

For example, a Decision Matrix can contain base-fee values indexed by authorization type, industry category, location, revenue band, or another applicable parameter. An Expression Set invokes one or more matrices, performs any additional arithmetic, and returns a calculated currency amount. Salesforce documents that Expression Sets and Decision Matrices accept JSON input from and return JSON output to OmniScripts.

The integration is direct: Salesforce explains that an Expression Set Action can be added to the OmniScript so that, when the applicant supplies the required information, the Business Rules Engine processes those values and returns the appropriate license fee.

Triggered Flow could calculate values, but it would duplicate a purpose-built policy calculation engine. Integration Procedures are appropriate for data orchestration and external integrations, not for replacing BRE as the authoritative fee-policy engine. A generic Flow application also bypasses the Public Sector OmniScript application architecture.

Study Guide Reference: Public Sector Solution Product Configuration – OmniScripts; Business Rules Engine; Expression Sets; Decision Matrices; automated application fee calculation.

================

The required combination is Web-to-Case, Person Accounts, and the Emergency Response Management for Public Sector managed package . This question reflects the ERM deployment architecture in which the agency provides an external digital destination for constituents and organizations to submit emergency-related requests while Public Sector components manage those requests internally.

Person Accounts provide the appropriate Salesforce representation for individual constituents who are not operating as business accounts. Web-to-Case supplies a standard intake mechanism through which web-submitted constituent requests can become Salesforce cases. The managed ERM package supplies the purpose-built emergency-response functionality; the unmanaged-package alternative is therefore incorrect.

Current Salesforce documentation describes Emergency Program Management as an Agentforce Public Sector capability for exposing emergency program information, incident updates, permits, assistance programs, and constituent requests through an Experience Cloud site. Salesforce also identifies Emergency Program Management as a specific Public Sector implementation area in the current Agentforce Public Sector portfolio.

Email-to-Case processes inbound email into cases but does not satisfy the specified web-based constituent experience prerequisite.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge; Emergency Program Management; Emergency Response Management; Person Accounts; constituent digital intake.

================

The product-native, low-code solution is to use Salesforce's DocuSign integration together with the supplied generic DocuSign OmniScript rather than designing Apex-based envelope handling.

Salesforce currently documents the sample OmniScript under the exact technical name GenericDocuSign/sendEsignature . It sends one or more documents associated with standard objects such as Opportunity, Order, or Quote—and supported custom objects—to DocuSign for electronic signature. The user selects the recipients and documents, reviews the routing order, and sends the envelope directly through the guided OmniScript.

Salesforce also provides a Send for eSignature (Generic) action that launches this OmniScript, minimizing custom development and allowing the signed-document status to be tracked using Generic DocuSign Envelope functionality.

Therefore, option C represents the intended answer. The option's GenericDocuSign/sendSignature wording reflects older/abbreviated exam terminology; Salesforce's current documented component is GenericDocuSign/sendEsignature. Option A refers to an "ObtainSignature" process rather than the send-for-signature flow needed when agreements must be transmitted to external grantseekers. Options B and D introduce the separate managed-package/Flow architecture when the supplied OmniScript capability already solves the requirement with less custom implementation.

Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – DocuSign integration; electronic signatures; GenericDocuSign/sendEsignature; OmniStudio document workflow.

================

Cloning an Action Plan Template creates a separate template configuration; it doesn't automatically redirect existing inspection configuration to the cloned version. Therefore, if the "Business Re-Opening" inspection continues to generate work based on the previous template, the configuration that identifies which Action Plan Template applies to that inspection must be updated. This makes C the intended configuration correction.

Salesforce's current Public Sector inspection architecture maintains the same fundamental principle: an inspection visit must be explicitly associated with the intended published Action Plan Template . Salesforce documents Action Plan Templates as reusable definitions containing assessment tasks, signature tasks, and other activities. When creating the inspection workflow, the appropriate template must be associated with the Visit so that the corresponding Action Plan and assessment indicators are generated.

Merely cloning the template doesn't alter existing references. Option A is unnecessary because creating a new template doesn't inherently require cloning the Inspection Type. Option D is also irrelevant; record identity, rather than display-name similarity, governs the relationship.

The terminology and association workflow have evolved in newer Public Sector releases, but the configuration principle tested by this item remains: the inspection must reference the new template rather than the previous template record .

Study Guide Reference: Public Sector Solution Product Configuration – Inspection Types; Action Plan Templates; Inspection Visits; template associations and version management.

================