AP-222 Leak Questions

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.

Document processing for a Business License Application requires Document Checklist functionality, an appropriate Document Type, and controlled user permissions. Salesforce ' s current Public Sector configuration guidance first directs administrators to turn on Checklist Items with Attachments under Document Checklist Settings. This activates the document-checklist framework used to associate required documents with applications.

The administrator then creates an appropriate Document Type, such as Business License Application, so submitted documents can be categorized and used consistently in document-management and extraction workflows. Salesforce ' s Intelligent Document Automation documentation likewise identifies Document Types and Document Checklist Items as core components for managing documents received from constituents. Access must then be restricted to the intended intake officer. Salesforce directs administrators to assign the Document Checklist license and corresponding permission set to users who work with application documents. Object, field, and application-form permissions should be limited according to the intake officer ' s responsibilities. Notes and Attachments is not the Document Type framework used by Intelligent Document Automation. The secure configuration therefore combines Document Checklist enablement, a purpose-defined Document Type, and the appropriate permission assignments.

Study Guide References: Intelligent Document Automation; Document Checklist Settings; Document Types; Application Forms; Document Permissions and Access Control.

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.