Free Salesforce Public Sector AP-222 Exam Flashcards

Business License Application, used when a business registers and seeks permits, and Individual Application, used when a person seeks a professional license. Both link to an Account, and inspection visits and their violations trace back to one of them, so choosing the wrong object breaks the downstream chain.

In the Preliminary Application Reference object. On submission a Data Mapper moves the values into Business License Application or Individual Application. Staging keeps in-progress portal input out of the live application objects.

A site visit made by an inspector to inspect and assess code compliance. It captures the date, time, purpose, place, related account, and inspector. Inspection Type is the setup record defining a kind of inspection; Visit is the transaction.

Assessment Indicator Definition is reusable setup describing a parameter that acts as a marker of compliance. Assessment Task is the transactional record of a check performed during a visit. Assessment Task Definition pairs a task with an indicator definition so both can be reused.

Regulatory Code Violation. It looks up to the inspection Visit, the Regulatory Code, and a Violation Type, and it relates back to the business license or individual application. Remedial steps go on Violation Enforcement Action, which is master-detail to the violation.

You publish it as an Action Plan Template Version. Applying that version creates an Action Plan whose Action Plan Items each map to one assessment task. An unpublished template cannot generate action plans.

Public Complaint stores complaints submitted by constituents against a business or establishment. Complaint Case links a public complaint to a Case. The complaint typically triggers an inspection Visit, which can then produce Regulatory Code Violations.

BusRegAuthTypeDependency captures dependency relationships between authorization types. BusRegAuthorizationType associates an authorization activity with a license or permit type. Model prerequisites in this data rather than hard-coding the sequence into a Flow or OmniScript.

Funding Opportunity advertises the pool of money. Individual Application captures the request. Application Decision records the approval or denial. Funding Award is the approved grant. Funding Disbursement tracks each payment out. Funding Award Requirement holds the deliverables the grantee owes.

Funding Award Amendment, which records modifications to an approved award's scope or finances. Creating a replacement Funding Award instead would orphan the existing requirements and disbursements and break reporting continuity on the original award.

Funding Award Participant for awards and Funding Opportunity Participant for opportunities. They record who has access to that specific record, so reviewers and collaborators are granted access per record instead of by widening org-wide defaults.

Benefit defines what the agency offers, such as food assistance. Benefit Assignment is one individual's or business's enrollment in it, captured from their application. Money or goods actually issued against that enrollment are Benefit Disbursement records.

Benefit Type classifies benefits applicable to individuals or groups. Benefit Product is the specific product or benefit authorized for delivery under a program. Benefit Schedule holds the delivery plan for issuing the benefit.

Program Enrollment holds the enrollment details, and Program governs enrollment and disbursement of benefits within that program. Case Program is a separate junction linking a Case to a Program when casework is tracked against it.

Recruitment Requisition is the formal request to fill a vacancy. Recruitment Posting is the advertised vacancy. Job Position is the instance of employment. Employment Offer records the offer. Position defines the functional role and Pay Grade groups positions with similar responsibilities.

A single Employee Workspace hub, HR Service for employee cases and requests, Talent Recruitment Management, digitized government forms, and an employee-facing bot. It is priced as a separate add-on to the public sector editions, so confirm entitlement before designing employee-facing requirements.

The Emergency Response Site template. Constituents request emergency assistance and businesses request critical supplies for employee and customer safety. Emergency Program Management surfaces program information, incident updates, and applications for assistance.

Care Plan Template defines a type of plan offered; Care Plan is the instance created for one individual to reach goals. Care Barrier records an obstacle preventing the constituent from getting required care. Goal Assignment ties goals into that care context.

It tracks one supporting document the constituent must submit, optionally constrained to a document type. Adding checklist items to an action plan template applies the same document requirements consistently to every application of that type.

Intelligent Form Reader, also documented as Intelligent Document Reader, which calls the Amazon Textract optical character recognition API and needs a Textract license. It runs inside Intelligent Document Automation: the upload becomes a Received Document, the reader extracts the values, and staff confirm them into the mapped record fields.

OmniStudio Document Generation, which merges Word or PowerPoint templates with data from a data source. Intelligent Document Automation runs the opposite direction, reading data out of submitted documents rather than producing new ones.

An Auth Provider for the secure connection, a Named Credential built from it that OmniScripts and Integration Procedures call, DocuSign's login page added as a Trusted URL because it loads in an iframe, and two Omni Interaction Configuration entries holding the DocuSign authorization.

Use standard reports and dashboards for operational lists and straightforward metrics on Salesforce data. Recommend CRM Analytics when the need involves large or blended datasets, exploration across multiple datasets, or embedded drillable dashboards beyond the report builder.

OmniScript for a guided multi-step process that collects input, such as a permit application. FlexCard for a compact, mostly read-only summary of a record with actions, such as a constituent overview tile. A FlexCard can launch an OmniScript.

Extract reads Salesforce data and returns JSON, XML, or a custom format. Turbo Extract reads and filters from a single object type. Load writes JSON or XML input back to Salesforce, updating and creating records. Transform reshapes data without touching Salesforce.

When you need data from more than one object type, or formulas, custom JSON, default values, or complex transformations. Turbo Extract reads a single Salesforce object type plus related-object fields, trading those features for simpler configuration and faster runtime.

Integration Procedures run server-side and chain multiple reads, writes, and external calls into one round trip. That cuts client-side traffic and keeps reusable logic in one place, callable from OmniScripts, FlexCards, and Flows alike.

Data Mappers take less time to create and are easier to maintain than equivalent Apex classes, and they are configuration rather than code. Reserve Apex for logic that Data Mappers and Integration Procedures genuinely cannot express.

A series of elements that run sequentially as one logical flow, built from variables, constants, conditions, calculations, lookups, and aggregations. It is the calculation and orchestration layer, and it can call decision matrices and decision tables as steps.

A decision matrix matches input values to one table row and returns that row's outputs, giving a single outcome per input set. A decision table reads rules from Salesforce objects or custom metadata, supports different operators per field, and can return multiple matching outcomes.

A decision table, because its rules live in Salesforce objects or custom metadata that business users can maintain. Burying the thresholds in expression set conditions would force a developer change and a deployment every month.

Decision Explainer for Expression Sets. It stores the application data behind a past decision so the outcome can be retrieved and reported on later. Agencies need it for appeals, audits, and fraud review of automated eligibility.

From Flows, OmniScripts, Integration Procedures, Apex, and the API. That reach is the reason to centralize policy logic in Business Rules Engine rather than duplicating the same rules inside every channel's automation.

It provides the data model for collecting and managing OmniScript form responses. Assessment questions are grouped into categories, and an Omni Assessment Task links an action plan item to the OmniScript that holds those questions and the conditional logic sequencing them.

Licenses And Permits. Constituents assess licensing needs, apply for and renew licenses, search license holders, file complaints, and view inspection history. Benefit Assistance, Grantmaking, Emergency Response, Employee Site, Career Site, and Service Provider Portal cover the other journeys.

Grantmaking. Managers post funding opportunities, applicants apply and report on outcomes, and external reviewers assess submissions. Benefit Assistance would give constituents benefit journeys but no funding opportunity or reviewer experience.

Service Provider Portal. Providers process referral requests, track service delivery, manage their own information, and collaborate with agency staff and constituents. It is provider-facing, unlike Benefit Assistance, which is built for constituents.

The constituent's identity, using Identity Verification. It runs as a flow launched from an engagement interaction, a voice call record page, or the utility bar, and by default checks details such as name, birth date, phone, and postal code.

An engagement interaction record, which forms the audit trail for the verification. Replacing Identity Verification with an ad hoc screen flow loses that trail, which agencies rely on as compliance evidence.

Actionable Relationship Center, which graphs constituents alongside related records such as cases, benefits, and care plans. Timeline is different: it displays a constituent's events and milestones in date sequence rather than mapping relationships.

Action Launcher gives agents a set of actions to start during an interaction, such as creating a case or requesting an appointment. Record Alerts is surfaced through a FlexCard and pushes critical information about the record at the agent unprompted.

It is the shared set of Industries tools that automate service delivery across intake, assessment, delivery, and monitoring. OmniStudio, Action Plans, Business Rules Engine, Document Checklist Items, Timeline, and Identity Verification all live there, so the same components recur across every public sector journey.

The Salesforce Platform as the single source of truth for agency data, Agentforce Service for case management and the constituent view, Experience Cloud for public portals, and the public sector data model of purpose-built objects on top.

Extend the standard object with custom fields rather than building a parallel custom object. Standard objects arrive with prebuilt relationships, components, and site templates. Replacing them forfeits all of that and creates permanent integration and upgrade work.

Only when configuration genuinely cannot meet the requirement. The expected order is OmniStudio, Business Rules Engine, Flow, and Action Plans first. Code adds testing, deployment, and maintenance burden that small agency teams struggle to carry.

Public sector journeys span constituents, caseworkers, inspectors, reviewers, and external providers, and each needs different access and interfaces. Persona and process mapping drives site template selection, sharing design, and which OmniStudio components you build.

Who may see a constituent's records, given that caseworkers, inspectors, reviewers, and external providers all touch them. Answer it with roles, sharing rules, and participant records rather than loosening org-wide defaults, because constituent data must stay least-privilege.

Government Cloud Plus - Defense. Government Cloud Plus holds a FedRAMP High provisional authority to operate and meets DoD Impact Level 2 through FedRAMP reciprocity. Confirm the agency's required level early, because it constrains which products and features are available.

Duplicate and inconsistent constituent records, which break the single view the public sector data model depends on. Plan matching and deduplication, name the source of truth per object, and validate before cutover instead of cleaning up afterward.

Because the evidence an agency must produce shapes the build. Decision Explainer, engagement interaction records, and assessment task records only capture what was configured at the moment of the decision. They cannot reconstruct history retroactively.