Complete AP-222 Salesforce Materials

Action Plans provide the standard Salesforce mechanism for converting a repeatable review or due-diligence procedure into a structured sequence of tasks and document requirements. Salesforce Grants Management specifically supports completing grantseeker due diligence by using Action Plans, Verification Checks, and Tax Status Search.

For a repeatable process, the administrator creates and publishes an Action Plan Template that defines the required activities. Reviewers then generate an Action Plan for the relevant grantseeker Account and follow the same standardized set of tasks. Salesforce ' s documented Grants Management process provides an example in which a published due-diligence Action Plan Template is instantiated directly from an Account record to track the organization ' s requirements. Action Plans also work with Document Checklist Items, making them particularly suitable where reviewers must collect prescribed documents in addition to completing tasks. Salesforce provides dedicated Action Plans and Document Checklist permissions for Grants Management users. A Screen Flow or OmniScript could implement a custom guided process, but doing so would duplicate functionality that Action Plans already provide declaratively. Written guidance alone would not enforce consistent operational execution.

Study Guide References: Grants Management; Action Plans; Action Plan Templates; Due Diligence; Document Checklist Items; Verification Checks.

Employee Experience and HR-service processes commonly use the Case object to represent sensitive employee requests, including HR, workplace, and employee-support matters. Because these cases can contain confidential personal or employment information, the appropriate baseline sharing model is to restrict access and then selectively grant it to authorized personnel.

Salesforce ' s Employee Concierge configuration explicitly sets the organization-wide default for the Case object to Private. This establishes the most restrictive standard access level and ensures that unrelated users don ' t automatically gain visibility into HR cases. Organization-wide defaults form the foundation of Salesforce record-level security. When Case is Private, the record owner and users who receive access through appropriate sharing mechanisms, queues, role hierarchy behavior, teams, or administrative privileges can access the case as configured. This supports least-privilege handling of employee information. Mirroring the organization chart into the role hierarchy could unintentionally widen access to confidential cases and does not itself secure HR data. Disabling approval processes has no direct relationship to record confidentiality. Likewise, the key security control required here is establishing Private OWD rather than relying on a hierarchy configuration as the primary protection.

Study Guide References: Employee Experience for Public Sector; HR Service; Case Security; Organization-Wide Defaults; Least-Privilege Record Access.

Decision Explainer is specifically designed to expose why an automated Business Rules Engine decision produced a particular outcome. Salesforce describes Decision Explainer as providing insight into business-rule calculations and helping public sector organizations maintain transparency, compliance, fraud controls, and equitable distribution of government benefits.

When grant eligibility is determined by an Expression Set and Decision Matrix, Decision Explainer captures the execution information required to understand the decision. Authorized reviewers can inspect the rule execution and determine which inputs, intermediate values, matrix outputs, and expressions contributed to the result. This provides an auditable explanation of why the application failed or satisfied eligibility requirements. Salesforce ' s Business Rules Engine is designed for precisely these types of public-sector policy decisions. It can determine whether applicants qualify for programs such as unemployment insurance, small-business loans, business licenses, and other public services. Decision Explainer can then be layered onto the rule to expose the reasoning behind the automated calculation. Developer debug logs are intended for technical troubleshooting rather than constituent-facing decision transparency, while repeated testing does not explain the actual historical determination made for the specific application.

Study Guide References: Decision Explainer; Business Rules Engine; Expression Sets; Decision Matrices; Eligibility Determination; Grants Program Transparency.

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.