Salesforce AP-222 Dumps Questions Answers

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.

An Action Plan Template becomes immutable after it is published. Salesforce explicitly states that published Action Plan Templates cannot be edited or returned to Draft status.

This behavior protects the integrity of repeatable operational processes. Existing Action Plans may already have been generated from the template, and allowing administrators to alter the underlying published definition could create inconsistent inspection requirements between records created at different times. When inspection requirements change, the administrator should use the supported versioning approach: deactivate the published template if necessary, clone it to create a new template/version, modify the cloned Draft version, add or revise its tasks, checklist items, assessment content, or other configuration, and then publish the new version. Salesforce documents this same approach for application requirements and other Action Plan implementations. The absence of an Edit button is therefore expected behavior and is not resolved by adding the action to a page layout or granting additional permissions. Salesforce Support is also not required to modify the template. The same design principle applies broadly across Action Plans: all required content should be finalized before publication because the published template is treated as the controlled definition of the repeatable process.

Study Guide References: Action Plan Templates; Template Lifecycle; Draft and Published Status; Cloning Templates; Inspection Action Plans; Version Management.

Inspection configuration in Agentforce Public Sector separates the reusable checklist definition from the inspection classification used when a visit is created. An Action Plan Template contains the assessment tasks, assessment indicator definitions, signatures, and related inspection work that inspectors must complete. Salesforce requires inspection Action Plan Templates to target the Visit object and to use the assessment-oriented Action Plan type before they are published and used for inspection execution.

The Inspection Type determines the type of onsite inspection being created. During Visit creation, the user selects an inspection type, and the configured inspection framework determines which assessment process applies. Salesforce ' s documented inspection process establishes the relationship among Visit, Inspection Type, and the relevant published Action Plan Template. Therefore, when an administrator clones an existing template to produce a revised version, the configuration that references the prior template must also be updated. Otherwise, newly generated Business Re-Opening inspections continue to use the previously associated template even though a newer template exists. Merely giving the templates identical names does not change the underlying record association, and creating a separate Inspection Type version is unnecessary when the existing type should use the new template.

Study Guide References: Inspection Types; Action Plan Templates; Visits; Assessment Tasks; Inspection Configuration and Template Associations.