Free Practice Questions for the Salesforce Accredited Professional Certification AP-222 Exam (2026 Updated)

Access to Action Plans requires the appropriate Action Plans permission set. Salesforce ' s Public Sector configuration documentation explicitly lists the Action Plans permission set as required for users who set up or use Action Plans.

The same requirement applies to Dynamic Assessments. Salesforce identifies Action Plans among the permission sets that must be assigned to users who conduct dynamic assessments, alongside Dynamic Assessment Access, Industries Assessment, OmniStudio User, and use-case-specific permissions such as Public Sector Access and Industries Visit. The scenario strongly indicates a user-specific access issue: existing inspectors can use Action Plans, while the newly onboarded inspector cannot. That makes an org-wide configuration problem such as Person Accounts highly unlikely. The appropriate troubleshooting step is therefore to compare the new inspector ' s permission-set assignments with those of a functioning inspector. The Enable Notes setting is unrelated to Action Plan feature entitlement. A disabled Salesforce user would prevent the user from accessing Salesforce altogether rather than selectively blocking only the Action Plans feature. Assigning the Action Plans permission set grants the required feature access, after which object-level and field-level permissions should also be validated for the objects used in the inspector ' s process.

Study Guide References: Action Plans; Action Plans Permission Set; Dynamic Assessment Access; Inspector Permissions; Public Sector User Access Configuration.

Person Accounts must be enabled when Public Sector processes need to represent individual constituents, such as scholars applying personally for research or grant programs.

A Person Account represents an individual using Salesforce ' s Account architecture while combining person-oriented Account and Contact characteristics. This model allows Public Sector applications to associate government processes with an individual constituent without forcing the person into a traditional business-account structure. Employee Experience and broader Public Sector functionality use person-centric records extensively for applications, benefits, grants, licenses, cases, and related services. The Individual Application object is designed to represent an application submitted by an individual. Person Accounts supply the constituent identity model that supports that relationship. Salesforce Flow may automate parts of the process, but it does not replace the required person data model. A custom application object is unnecessary because Individual Application already exists, and Product Schedule is unrelated to constituent grant applications. Because Person Accounts materially change the Salesforce account model, their enablement should be planned deliberately during Public Sector implementation.

Study Guide References: Person Accounts; Individual Application; Grants Management; Constituent Data Model; Individual Applicants.

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.

Salesforce Shield is the appropriate add-on when an organization requires enhanced security, auditability, monitoring, and data-protection controls. Shield is a suite of security products designed to add additional layers of security, compliance, and governance to Salesforce applications. Its core capabilities include Event Monitoring, Field Audit Trail, and Shield Platform Encryption, with Data Detect also available for sensitive-data discovery.

For a public sector implementation, Shield Platform Encryption strengthens protection for sensitive information stored at rest. Field Audit Trail provides long-term field-level historical information that supports regulatory audits, governance, and forensic review. Event Monitoring provides detailed visibility into user activity and data access, helping security teams detect suspicious behavior and demonstrate operational monitoring controls. Salesforce specifically describes these capabilities as relevant to regulatory compliance and security governance. Setup Audit Trail and standard Field History Tracking provide narrower auditing functions, while Classic Encryption does not deliver the comprehensive monitoring, encryption, and audit framework represented by Shield. Shield does not itself confer ISO 27001 certification, but it provides significant technical controls that can support an organization ' s compliance program.

Study Guide References: Salesforce Shield; Platform Encryption; Event Monitoring; Field Audit Trail; Public Sector Security and Compliance.

Configuring regulatory authorizations in Agentforce Public Sector depends on defining the regulatory framework that describes who issues the authorization, what authorization is required, and what type of business requires it. Those requirements are represented by Regulatory Authority, Regulatory Authorization Type, and Business Type.

Salesforce defines Regulatory Authority as the agency or department responsible for defining and enforcing requirements for licenses, permits, and inspections. Regulatory Authorization Type represents a particular license or permit required for a specified activity or business. Business Type categorizes a business and its activities, enabling the authorization model to associate applicable licenses and permits with the correct class of business. Salesforce also provides Business Regulatory Authorization Type to map regulatory authorization types to business types. Inspection Type belongs to the subsequent inspection configuration process and determines the type of compliance inspection performed. Business Profile stores business-related information but is not one of the three foundational regulatory configuration entities identified here. Together, Business Type, Regulatory Authorization Type, and Regulatory Authority establish the declarative licensing framework required before license authorization processes can operate consistently.

Study Guide References: Regulatory Compliance Data Model; Regulatory Authority; Regulatory Authorization Type; Business Type; Licensing and Permitting Configuration.

A secure constituent grant-application architecture should combine record-level privacy, authenticated access, and automated bot protection. Setting the external organization-wide defaults for application records to Private establishes a restrictive baseline. External users receive access only through explicit sharing mechanisms rather than being able to discover other applicants ' records. Salesforce consistently recommends restrictive external sharing for sensitive constituent data.

Grant application OmniScripts should also be hosted on Experience Cloud pages configured to Require Login. Authentication ensures that sensitive application information, supporting documentation, and application-status data are associated with a verified external user instead of being exposed through anonymous access. CAPTCHA provides a separate security control focused on automated form abuse. It helps distinguish human submissions from automated bots and reduces the risk of bulk fraudulent or spam applications. These controls address different threat surfaces and should therefore be implemented together rather than treated as alternatives. A public search page for application reference numbers does not prevent spam and can introduce unnecessary disclosure risk. Similarly, application protection should not rely solely on generic spam checking when authentication, restrictive record sharing, and CAPTCHA can be applied directly to the grant application experience.

Study Guide References: Grants Management Security; Experience Cloud Authentication; External OWD; CAPTCHA; OmniScript Security; Constituent Data Privacy.

Two Decision Matrices provide the appropriate separation of rule domains. One matrix represents the Federal Income Limit reference data, where inputs such as household size are evaluated to return the corresponding income threshold. The Expression Set can then calculate the household ' s AMI percentage by comparing household income with the returned threshold.

A second Decision Matrix maps that calculated percentage to the appropriate prioritization pool. This separation keeps externally defined income thresholds independent from the agency ' s prioritization policy, enabling either rule set to be maintained without restructuring the other. Salesforce defines Decision Matrices as lookup tables that match input values to rows and return the corresponding output values. Expression Sets perform calculations and can invoke Decision Matrices as part of a larger rule sequence. Salesforce ' s eligibility examples similarly demonstrate using household income and household size as matrix inputs for determining income thresholds before subsequent eligibility or benefit calculations. A third matrix for household data is unnecessary because household income and size are runtime inputs, not a separate policy lookup table.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Lookup Tables; Prioritization; Income and Household Eligibility Rules.

Action Plans provide the standard Public Sector mechanism for organizing, assigning, tracking, and completing repeatable groups of activities. Salesforce describes Action Plans as collections of tasks or checklist items that support repeatable business processes, with individual tasks capable of carrying an owner, priority, and deadline. This structure allows multiple reviewers, inspectors, caseworkers, and other employees to collaborate while retaining visibility into work status and accountability.

For inspections specifically, Public Sector uses Action Plan Templates to define the tasks required for a particular type of inspection visit. Templates can include assessment task definitions, required activities, task sequencing, and signature tasks. Published templates can then generate standardized action plans for individual visits, producing consistent inspection execution across teams. OmniStudio is suited to guided user interactions and integration orchestration, Business Rules Engine evaluates declarative decision logic, and Data Mappers/DataRaptors handle data transformation and persistence. None serves primarily as the collaborative task-management framework for inspection execution. Action Plans directly satisfy both requirements: automated creation of repeatable inspection work and coordinated execution by internal teams.

Study Guide References: Action Plans; Action Plan Templates; Inspection Visits; Assessment Tasks; Public Sector Inspections.

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.

Salesforce provides the ContractEnvelopeStatusScheduler Apex class specifically for polling DocuSign envelope statuses in the supported eSignature integration. Salesforce documentation explicitly states that this class can be scheduled to poll DocuSign for envelopes submitted through the eSignature process.

The scheduled job queries envelope status and updates Salesforce so contract and document records reflect states such as sent, completed, or voided. Salesforce notes that when scheduled through the Salesforce UI, the job can run hourly. It can also be scheduled through Apex at shorter intervals, subject to DocuSign ' s minimum polling interval requirements. DocuSign requires at least 15 minutes between successive polling calls. Salesforce ' s recent support guidance also confirms that ContractEnvelopeStatusScheduler remains the scheduled job responsible for retrieving envelope-state updates and discusses asynchronous handling when many envelopes require updates simultaneously. Using Salesforce ' s provided scheduler is preferable to building a separate REST polling implementation because it follows the supported Industries/DocuSign integration architecture. The other scheduler class names do not correspond to the documented component.

Study Guide References: DocuSign Integration; ContractEnvelopeStatusScheduler; eSignature Envelope Status; Scheduled Apex; Contract Lifecycle Management.

Salesforce ' s DocuSign integration supplies a defined electronic-signature lifecycle without requiring a custom signing framework. Salesforce documentation identifies three capabilities that directly correspond to this scenario: sending a contract document for review and signature, tracking the signed document and updating the associated contract status, and automatically invalidating a contract document awaiting signature when a newer document supersedes it.

Automatic invalidation is part of the contract/eSignature lifecycle itself. It does not require the organization to construct a separate approval process merely to void the superseded signing document. This is important for version integrity because the signer should not complete an outdated document after a replacement has become authoritative. The integration also tracks the progression of the signed document so Salesforce can maintain synchronization between the eSignature transaction and the relevant contract record. Sending the document for review and signature is therefore paired with post-signature status management. Allowing a reviewer to modify the actual contract-document contents during the signing operation is not one of these standard signing functions. Changes should be handled through the controlled contract-document generation and revision process.

Study Guide References: DocuSign Integration; Electronic Signatures; Contract Documents; Signature Status Tracking; Superseded Contract Documents.

A predictable application surge requires deliberate performance engineering, traffic management, and scale testing.

First, expensive synchronous processing should be reduced or moved to asynchronous execution where practical. Salesforce Experience Cloud supports high-volume record creation patterns that collect requests and process them asynchronously in batches, helping the site continue handling traffic during spikes. Second, a Content Delivery Network (CDN) reduces load on the Salesforce origin by distributing and caching eligible content closer to users. Salesforce recommends CDN-based delivery for high-traffic Experience Cloud sites because it improves page-load performance and reduces processing pressure during periods of heavy concurrent access. Traffic-control or waiting-room patterns can additionally regulate extreme arrival bursts before they reach the application tier. Third, the application must undergo realistic performance and scale testing based on expected concurrency, traffic, transactions, and customizations. UAT validates functional correctness but does not establish production-scale capacity. IP restrictions would arbitrarily reduce access rather than engineer the system to withstand legitimate constituent demand.

Study Guide References: Experience Cloud Performance and Scale; CDN; Asynchronous Processing; High-Volume Record Creation; Scale Testing; Traffic Surge Architecture.

Public Sector provides a dedicated Public Complaint object for recording concerns submitted by constituents and a separate Case object for managing the organization ' s investigation and response. This separation aligns directly with the requirement to distinguish external complaint intake from internal casework.

Salesforce ' s complaint-management architecture uses the Public Complaint record to capture the reported incident, reporter information, and associated supporting details. Public Sector can then create a separate Case related to that complaint so case managers can prioritize the matter, assign caseworkers, investigate the concern, and track follow-up activity. Salesforce ' s investigative case-management documentation also identifies the Public Complaint as the intake record created when a constituent submits a concern and supports subsequent case creation and proceedings based on that complaint. Using Case record types for both external intake and internal investigation would collapse two distinct business concepts into one object. A custom complaint object is unnecessary because Public Sector already provides the appropriate standard industry object and its relationships.

Study Guide References: Complaints Management; Public Complaint; Investigative Case Management; Case; Experience Cloud Complaint Intake; Constituent Reporting.

Public Sector includes native configuration for automatically creating Regulatory Code Violation records from inspection assessment results. Salesforce ' s current terminology identifies the relevant field as Assessment Question Status on the Inspection Assessment Indicator record.

The administrator configures the applicable failure status—such as Fail—to indicate that the result represents a violation. When an inspector selects that configured result during inspection execution, Public Sector automatically creates the corresponding Regulatory Code Violation record. Salesforce explicitly includes Configure an Assessment Question Status to Automatically Create a Violation as part of standard Inspections Setup. This declarative configuration keeps regulatory behavior within the standard inspection model. Assessment Indicator Definitions define what inspectors evaluate, Assessment Task Definitions group indicators into inspection activities, and Inspection Assessment Indicators capture the actual results. The status configuration determines when those results generate violations. A custom Flow is unnecessary because the platform already provides the required automation. Similarly, Action Plan Templates determine the inspection workload but do not independently control the conversion of a failed result into a violation.

Study Guide References: Inspections Setup; Inspection Assessment Indicator; Assessment Question Status; Regulatory Code Violation; Assessment Indicator Definitions.

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.

Business Rules Engine separates reusable lookup logic from procedural rule execution. Decision Matrices contain business-rule lookup tables with defined input and output columns. When supplied with input values, the matrix searches for the applicable row and returns its configured output. Salesforce describes Decision Matrices as useful for implementing complex rules in a systematic and readable manner.

Expression Sets orchestrate more sophisticated decision logic. They can execute calculations, conditional branches, aggregations, constants, variables, and matrix lookups. An Expression Set can therefore call a Decision Matrix at the appropriate point in a licensing or eligibility process and use the returned value in subsequent calculations or decisions. Salesforce specifically documents Expression Sets calling Decision Matrices and consuming the output corresponding to the matching matrix row. This architecture allows policy data and procedural calculations to be maintained independently. For example, a licensing fee table can be maintained in a Decision Matrix while an Expression Set calculates intermediate values, invokes the matrix, and produces the final fee. The other options reverse these functions or mischaracterize the data interface. Decision Matrices do not perform the broader sequence of calculations attributed to Expression Sets.

Study Guide References: Business Rules Engine; Expression Sets; Decision Matrices; Licensing Business Rules; Declarative Decision Automation.

Public Sector provides three purpose-built Lightning components for the Visit record page: Inspection Details, Inspection Actions, and Inspection Tab Container. Salesforce documents these components as part of the standard inspection experience used by inspectors, compliance officers, and caseworkers.

Inspection Details displays key Visit information such as location, scheduled time, person to visit, address, and inspection type. Inspection Actions provides operational controls such as Start Visit and End Visit and displays elapsed inspection time. Inspection Tab Container organizes inspection work into tabs for Tasks, Notes, and Details and can display a progress ring showing completion status. These components are specifically designed to reduce navigation and give inspectors the information and actions needed directly on the Visit page. Salesforce ' s standard Visit Lightning record-page configuration explicitly instructs administrators to place these inspection components on the page. Inspection Calendar and Inspection Dynamic Dashboards may support broader scheduling or analytical use cases, but they are not the three built-in Visit execution components identified for conducting an inspection.

Study Guide References: Inspection Management; Visit Lightning Record Page; Inspection Details; Inspection Actions; Inspection Tab Container.

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.

Decision Explainer provides the explainability layer for decisions generated through Public Sector business processes, including eligibility, prioritization, and other Business Rules Engine outcomes. Adding the Decision Explainer Log History component to the Lightning record page makes the interface available, but component placement alone does not grant the user access to Decision Explainer functionality or its underlying records.

Salesforce specifies Decision Explainer access permissions for users who create, use, or review explainability information. Current Public Sector documentation identifies Decision Explainer Service Access for internal users working with Decision Explainer entities and decision logs. Salesforce also provides a Decision Explainer permission set license for access to Decision Explainer functionality. Therefore, after confirming that the component is correctly placed on the application Lightning page, the administrator should validate the caseworker ' s Decision Explainer permissions. OmniStudio Admin and OmniStudio User concern OmniStudio configuration and execution, while Rule Engine Runtime enables execution of Business Rules Engine logic. Those permissions do not independently provide access to the Decision Explainer user interface and decision history.

Study Guide References: Decision Explainer; Decision Explainer Log History; Business Rules Engine Integration; Public Sector Permission Sets and Permission Set Licenses.

Scope, schedule, and cost represent the primary project constraints that must be controlled during a Public Sector implementation. Scope establishes the capabilities and business processes that the agency expects the implementation to deliver. Schedule establishes when those capabilities must be designed, configured, tested, approved, and released. Cost defines the financial boundary within which the implementation must operate.

These constraints are closely interdependent. Increasing scope normally increases the implementation effort and can extend the delivery schedule or require additional budget. Compressing the schedule can require additional implementation resources and may increase cost. Reducing available funding can require the organization to defer lower-priority functionality or adopt a phased delivery model. Salesforce implementation guidance similarly emphasizes defining the implementation scope, rollout milestones, timeline, customization effort, integration requirements, stakeholder availability, and project budget during planning. This discipline is especially important for government programs because regulatory requirements, procurement rules, approval processes, legacy-system dependencies, and fixed funding cycles can constrain delivery. Workshops, tools, and individual resource categories are important implementation considerations, but they are subordinate planning elements rather than the fundamental project constraint model represented in this question.

Study Guide References: Public Sector Implementation Planning; Project Scope; Implementation Schedule; Project Cost; Phased Delivery; Governance and Risk Management.

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.

For administrator-controlled registration, the Contact page layout should include the Enable Customer User action. This allows an authorized internal user to manually provision an Experience Cloud login from the constituent ' s Contact record rather than permitting visitors to create their own accounts.

Salesforce ' s documented manual-registration process instructs administrators to open Contact page-layout configuration and add Enable Customer User and, where appropriate, View Customer User. An administrator then opens the participant ' s Contact record, selects Enable Customer User, and specifies the username, profile, and other required user information. Current Salesforce guidance also confirms that Manage External Users functionality includes the Enable Customer User action and that these actions appear individually on Contact layouts in Lightning Experience. Self-registration would directly contradict the requirement because it allows external visitors to initiate account creation. There is no separate standard Contact action named Register User that replaces the established external-user provisioning mechanism described here. This configuration gives the PSO controlled onboarding of grantseekers while still allowing the resulting users to authenticate to the Grants Management Experience Cloud site after their accounts are provisioned.

Study Guide References: Grants Management; Experience Cloud User Administration; Manual Registration; Contact Page Layout; Enable Customer User.

The Decision Matrix is the first configuration point to inspect when applications are being placed into incorrect prioritization categories. A prioritization matrix typically contains the combinations of input criteria—such as income, household characteristics, program criteria, application attributes, or calculated scores—and maps them to corresponding priority outputs.

Salesforce defines a Decision Matrix as a lookup table in which input values are matched against configured rows and the corresponding output values are returned. If a threshold, range, row, input mapping, rank, or output value in that table is configured incorrectly, otherwise valid application data can produce the wrong prioritization result. The administrator should therefore inspect the matrix version used by the active rule, confirm that the expected input columns contain the correct values, validate boundary conditions and ranges, and verify that each matching row returns the intended prioritization output. Expression Sets can invoke the matrix, but when the process is executing and the observed problem concerns an incorrect mapped priority, the underlying matrix is the most plausible source of incorrect policy data. Decision Explainer can provide additional runtime transparency where configured, but the configuration element directly representing prioritization lookup rules is the Decision Matrix.

Study Guide References: Business Rules Engine; Decision Matrices; Application Prioritization; Matrix Versions; Input/Output Rule Validation.

Business Rules Engine supports calculations across collections of values by using Aggregate Groups and Aggregate steps within an Expression Set. This is the appropriate pattern when a single application contains multiple selected permits and each permit contributes a fee to the final amount.

Salesforce documents that an Aggregate Group executes the preceding steps once for each set of input values and then aggregates the resulting values according to the configured aggregation logic. Within the Aggregate Group, the Aggregate step can perform SUM, AVG, MAX, or MIN operations. For this licensing scenario, each selected permit can be evaluated to determine its applicable fee. The Expression Set then places the repeated evaluation inside an Aggregate Group, and an Aggregate step using SUM produces the application ' s total permit fee. A custom Lightning component is unnecessary because Business Rules Engine already provides declarative list aggregation. Permission sets are required for appropriate design or runtime access, but assigning permissions does not implement the actual multi-permit fee calculation. This configuration keeps fee policy inside Business Rules Engine, making the logic easier to maintain and reducing the need for custom code.

Study Guide References: Business Rules Engine; Expression Sets; Aggregate Group; Aggregate Step; SUM Function; Licensing and Permit Fee Calculation.

Standard Salesforce Reports and Dashboards provide the appropriate solution because the requirement is straightforward operational visibility rather than advanced analytical modeling. A custom dashboard can summarize each approver ' s pending applications, status, age, and other approval metrics and can be placed directly on the Lightning Home page.

Salesforce supports embedding dashboards on the Home tab so that users see relevant operational information immediately after login. The Dashboard standard component can be added in Lightning App Builder and configured to display the required dashboard. The Home page can then be activated for an app-and-profile combination, which aligns precisely with assigning the custom page to the Approver profile. CRM Analytics would add licensing and administration overhead without being necessary for this operational requirement. A single report also provides less effective at-a-glance monitoring than a dashboard containing multiple approval metrics and visualizations.

Study Guide References: Salesforce Reports and Dashboards; Lightning App Builder; Custom Home Pages; Profile-Based Page Assignment; Approval Operational Reporting.

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.

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.