Cert++
  1. Home
  3. Public Sector Solutions Accredited Professional

Public Sector Solutions Accredited Professional

Checklist progressProgress

0/189Learned

Public Sector Solutions Accredited Professional Study Checklist
  • Platform Administrator
  • Platform App Builder
  • Platform Foundations
  • Platform Developer
  • Platform Administrator II
  • Agentforce Sales Consultant
  • Agentforce Service Consultant
  • Platform Data Architect
  • Platform Development Lifecycle and Deployment Architect
  • Platform Identity and Access Management Architect
  • Platform Integration Architect
  • Platform Sharing and Visibility Architect
  • Heroku Architect
  • B2C Solution Architect
  • Experience Cloud Consultant
  • Agentforce Field Service and Operations Consultant
  • Agentforce Nonprofit Consultant
  • Data 360 Consultant
  • Omnistudio Consultant
  • CRM Analytics and Einstein Discovery Consultant
  • Platform User Experience Designer
  • Platform Strategy Designer
  • B2C Commerce Developer
  • JavaScript Developer
  • Omnistudio Developer
  • Platform Developer II
  • Marketing Cloud Engagement Administrator
  • Marketing Cloud Engagement Specialist
  • Marketing Cloud Engagement Consultant
  • Marketing Cloud Account Engagement Specialist
  • Marketing Cloud Next Consultant
  • Agentforce Sales Foundations
  • Business Analyst
  • Marketing Cloud Engagement Developer
  • Marketing Cloud Engagement Foundations
  • Agentforce Specialist
  • Agentforce Life Sciences Consultant
  • B2B Commerce Administrator AP
  • B2B Commerce Developer AP
  • Agentforce Communications AP
  • Agentforce Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • Public Sector Solutions AP
  • Revenue Cloud Consultant
  • MuleSoft Integration Foundations
  • MuleSoft Developer
  • MuleSoft Developer II
  • MuleSoft Platform Integration Architect
  • MuleSoft Platform Architect
  • Tableau Desktop Foundations
  • Tableau Data Analyst
  • Tableau Consultant
  • Tableau Server Administrator
  • Tableau Next Consultant
  • Tableau Architect
  • Slack Administrator
  • Slack Consultant
  • Slack Developer

Checklist progressProgress

0/189Learned

  • Translating agency pain points into Agentforce Public Sector value
  • Agency vision statements and measurable success criteria
  • Matching agency missions to modular Agentforce Public Sector apps
  • Prebuilt data model and industry common layer versus custom build
  • Communicating the solution vision to business stakeholders and governance
  • License and permit lifecycle stages
  • Regulatory authorization framework objects for licensing
  • Business regulatory authorization type dependencies
  • License training requirements for occupational licenses
  • Helping constituents identify required licenses and permits
  • Application objects and record types for licenses and permits
  • Regulatory transaction fees in licensing and permitting
  • Approval processes for license and permit applications
  • Issuing and renewing licenses and permits
  • Access for internal licensing staff versus external portal applicants
  • Constituent self-service views on the license and permit site
  • Licensing guided flow components and process library packages on site pages
  • Inspections versus dynamic assessments for compliance reviews
  • Inspection checklist hierarchy from regulatory code to assessment task
  • Action plan templates and inspection types for inspection visits
  • Creating, assigning and conducting inspection visits
  • Visit record page and Hierarchical View configuration for inspectors
  • Mobile signature capture at the end of an inspection visit
  • Violation types, code violations and violation enforcement actions
  • Automatic regulatory code violation creation from failed assessment results
  • Fees generated from inspection visits and enforcement actions
  • Turning on Grantmaking in an Agentforce Public Sector org
  • Grantmaking permission set licenses and permission set assignment
  • Budgets and funding opportunities setup for grant programs
  • Track Applications versus Individual Application for grant intake
  • Grantmaking Experience Cloud site setup for grantseekers
  • Action plan templates and document checklists for grant programs
  • Grant application review assignment and reusable evaluation workflows
  • Compliant Data Sharing for grantmaking records and reviewer access
  • Funding awards, disbursements, and award requirements configuration
  • Automation tool selection for grantmaking processes
  • Grantmaking add-on capabilities for extended grant requirements
  • Employee Experience for Public Sector add-on scope and licensing
  • HR Service for employee onboarding, self-service and HR subagents
  • Employee Experience versus constituent-facing prebuilt apps for internal workforce needs
  • Combining Public Sector add-ons for employee-facing AI and security requirements
  • Recognizing repeatable decisions suited to Business Rules Engine
  • Business Rules Engine versus Flow, Apex, and agents for policy logic
  • Building a decision from expression sets and lookup tables
  • Decision matrices versus decision tables for rule lookups
  • Complaint prioritization and enforcement action rules
  • Calling BRE decisions from Omniscripts, Integration Procedures, and flows
  • Assessing the need for document processing in paper-based intake
  • Intelligent Document Automation alone versus with Intelligent Form Reader
  • Transforming received documents into application records
  • OCR Review component for verifying extracted application data
  • Selecting an eSignature technology for a public sector business process
  • GenericDocuSign sendEsignature Omniscript for sending record documents
  • DocuSign recipient types and signer access codes
  • Signer routing order for sequential versus simultaneous signing
  • Sending generated agreements and permits for eSignature
  • Customizing the sendEsignature Omniscript and its Data Mapper sources
  • Standard Reports and Dashboards versus CRM Analytics for agency reporting needs
  • Analytics for Licenses, Permits, and Inspections app dashboards
  • Caseworker Productivity app for caseload and SLA insights
  • Deploying CRM Analytics apps in Agentforce Public Sector
  • Emergency Program Management capabilities and components
  • Emergency Response site template versus other Public Sector site templates
  • Emergency permit requests and assistance program intake
  • Post-approval health and safety inspections with the Inspection app
  • Adapting intake and rules quickly when policies change during a disaster

Given a set of business requirements, identify the appropriate Omnistudio components that can accomplish those requirements most effectively

0/13

When Omnistudio fits a requirement better than standard Salesforce tools

Learn this concept
Unseen

Omniscripts for guided constituent applications and intake forms

Learn this concept
Unseen

Flexcards for at-a-glance information and contextual actions

Learn this concept
Unseen

Omnistudio Data Mapper types for reading, transforming and writing data

Learn this concept
Unseen

Integration Procedures versus Data Mappers for server-side data

Learn this concept
Unseen

Supporting file uploads and save-for-later in Omniscript forms

Learn this concept
Unseen

Cross-step validation in Omniscript application forms

Learn this concept
Unseen

Attaching completed application forms as PDFs to records

Learn this concept
Unseen

Omnistudio Document Generation for official correspondence

Learn this concept
Unseen

Prebuilt Public Sector Omniscript templates and process library packages

Learn this concept
Unseen

Dynamic assessments with Discovery Framework and Omniscripts

Learn this concept
Unseen

Publishing Omniscripts and Flexcards on Experience Cloud sites

Learn this concept
Unseen

Combining Omnistudio components into an end-to-end solution

Learn this concept
Unseen

Given a set of business requirements, identify the appropriate Agentforce Service components to provide based on business requirements

0/9

  • Case management for constituent service requests
  • Agentforce Service channels for constituent request intake
  • Omni-Channel routing for caseworker workload distribution
  • Entitlements and milestones for service response deadlines
  • Account page for service representatives in Agentforce Public Sector
  • Identity Verification before sharing constituent information
  • Lightning Knowledge for staff answers and constituent self-service
  • Constituent-facing prebuilt agents for self-service sites
  • Service Process Studio for automating constituent service requests

Given business requirements for a digital customer experience, select the correct Agentforce Public Sector digital experience offering to meet the requirement

0/8

  • License and Permit portal template for constituent licensing journeys
  • Benefit Assistance portal for program discovery and benefit applications
  • Service Provider Portal for referrals and service delivery
  • Grants Management portal for grant applicants and grantees
  • Employee Experience portal for internal agency staff
  • Public portal setup steps from an Agentforce Public Sector template
  • Guest user access versus authenticated self-registration on public portals
  • Customer Community versus Customer Community Plus for portal users

Given a repeatable set of business logic, define the correct expression set and logical relationships to select and implement the automation tool

0/14

  • Variables versus constants in expression set resources
  • Object fields and context data as expression set inputs
  • Calculation and Lookup Table steps in an expression set
  • Decision matrices versus decision tables in Business Rules Engine
  • Condition, Conditional Group and Branch logic in expression sets
  • Aggregate and Aggregate Group steps for repeated calculations
  • Sub Expressions for reusable child rule logic
  • Expression set build, simulation and activation lifecycle
  • Expression set version dates and rank resolution
  • Choosing the workflow tool that invokes an expression set
  • Expression set design for license application fee calculation
  • Expression set design for benefit eligibility and amounts
  • Decision Explainer for expression set outcomes
  • Business Rules Engine designer and runtime permissions

Given a business scenario, define the correct steps and tools required to set up an org for Agentforce Public Sector

0/13

  • Agentforce Public Sector org setup workflow and task order
  • Supported editions and license verification for Agentforce Public Sector
  • Choosing Agentforce Public Sector configurations and add-ons
  • Guided Setup versus Salesforce Go for configuring features
  • Person accounts for constituent records in Agentforce Public Sector
  • Contacts to Multiple Accounts for constituent and business relationships
  • Installing and upgrading Omnistudio in an Agentforce Public Sector org
  • Internal users, profiles and permission sets for agency personas
  • Organization-wide email addresses for agency profiles
  • Chatter feed tracking, Notes and Salesforce Calendar for agency staff
  • Application record types for usage tracking
  • Application approval processes and review queues during setup
  • Field history tracking versus Field Audit Trail for audit and retention

Given a set of business requirements, identify when and how to use action plans to meet those requirements

0/11

  • When to use action plans for repeatable agency processes
  • Action plan templates versus action plan instances
  • Action plan template target objects
  • Assigning action plan tasks to users, roles, queues or the plan creator
  • Task dependencies, due dates and nonwork days in action plans
  • Document checklist items within action plan templates
  • Action plan setup on Lightning apps and record pages
  • Granting internal users access to action plans
  • Exposing action plans to constituents on Experience Cloud sites
  • Action plans for inspection visits and dynamic assessments
  • Action plans for grant application reviews and award requirements
  • Implementation lifecycle stages and the activities each stage owns
  • Customer-centric discovery of agency goals, stakeholders and success criteria
  • Current-state assessment of legacy systems, existing orgs and third-party roles
  • Ideation and prototyping to validate solution options with stakeholders
  • Layered architecture of Agentforce Public Sector in solution design
  • Modular selection of prebuilt apps and common layer components
  • Common layer components for intake and application review
  • Common layer components for assessment, delivery and monitoring
  • Prebuilt templates and standard features before custom development
  • Edition, license and add-on choices in the solution design
  • Phased rollout versus big-bang implementation
  • Prioritizing first-phase scope by business impact and effort
  • Presenting and defending the solution design to a governance body
  • Testing scenarios and user acceptance testing for Public Sector solutions
  • Fit-gap mapping of agency requirements to the Public Sector data model
  • Household and constituent relationship modeling
  • License and permit application objects for individuals and businesses
  • Regulatory framework objects for licensing and compliance
  • Visit, violation and enforcement objects for inspections
  • Program and benefit management objects for benefit delivery
  • Discovery Framework assessments versus custom objects for data collection
  • Extending standard Public Sector objects versus building custom objects
  • Profiles, roles and permission sets in agency access design
  • Org-wide default settings for sensitive public sector records
  • Role hierarchy design for an agency reporting structure
  • Sharing rules for cross-department collaboration beyond org-wide defaults
  • Persona-based access with permission set groups and muting
  • Compliant Data Sharing versus role hierarchy and sharing rules
  • Compliant Data Sharing setup and participant roles
  • External sharing and security for constituent portal users
  • Data management strategy planning questions
  • Data governance versus data stewardship roles
  • Data quality dimensions and fit-for-purpose data
  • Data profiling and ongoing data quality monitoring
  • Declarative controls that enforce data quality at entry
  • Duplicate management for constituent and business account records
  • Legacy data migration preparation and load sequencing
  • Data Import Wizard versus Data Loader for agency data loads
  • Integration pattern categories, timing and systems of record
  • Federation, replication and middleware strategies for external agency data
  • Data retention, archiving and backup planning for government records
  • Scoping a business process map by input and outcome
  • Hierarchical process mapping levels for different stakeholder audiences
  • Universal Process Notation versus other process diagram types
  • Current-state versus future-state process analysis
  • Process map governance, ownership and version control
  • Developing constituent personas from research
  • Constituent journey mapping to back-end business processes
  • User stories and acceptance criteria for documented requirements
  • Least-privilege user access with profiles and permission sets
  • Government Cloud and data residency options for regulatory compliance
  • Choosing Salesforce Shield capabilities for sensitive constituent data
  • Identity Verification, Audit Trail and decision logs for sensitive interactions
  • Large data volume planning as the agency org grows
  • Omnistudio design choices for high-volume portal performance

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Public Sector Solutions Accredited Professional studiers.

Go to Discord
  1. Public Sector Solutions Accredited Professional Checklist
  3. Public Sector Solution Product Configuration

Integration Procedures versus Data Mappers for server-side data

Explainer

Learn More

Practice Question

Studying for this exam?

This is one of 189 concepts on the Salesforce Public Sector Solutions Accredited Professional exam.

Looking for practice exams? Click below to try one!

Keep going

Next conceptSupporting file uploads and save-for-later in Omniscript forms

Checklist progress

0/189 (0%)

0 of 189 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle

Study Community

Ask questions and get the latest info from other Public Sector Solutions Accredited Professional studiers.

Go to Discord
Close
  1. Public Sector Solutions Accredited Professional Checklist
  3. Public Sector Solution Product Configuration
Integration Procedures versus Data Mappers for server-side data

Explainer

Learn More

Practice Question

Studying for this exam?

This is one of 189 concepts on the Salesforce Public Sector Solutions Accredited Professional exam.

Looking for practice exams? Click below to try one!

Keep going

Next conceptSupporting file uploads and save-for-later in Omniscript forms

Explainer

Data Mappers and Integration Procedures are the two Omnistudio tools that work with data on the server without custom code. A Data Mapper does one data job: it reads Salesforce data, writes it, or reshapes it in a single step. An Integration Procedure runs many steps in one server call, can reach many kinds of data sources, and usually calls one or more Data Mappers to do the reading and writing.
Core information
  • The two tools are partners, not rivals. Integration Procedures usually call one or more Data Mappers and are more flexible and powerful, but for some use cases a single Data Mapper is enough.
More details and nuances
  • Read-then-write is the most common trigger for an Integration Procedure. A Data Mapper reads or writes, so a requirement to both read and write needs at least two Data Mappers, and an Integration Procedure is what runs them together.

Explainer

Data Mappers and Integration Procedures are the two Omnistudio tools that work with data on the server without custom code. A Data Mapper does one data job: it reads Salesforce data, writes it, or reshapes it in a single step. An Integration Procedure runs many steps in one server call, can reach many kinds of data sources, and usually calls one or more Data Mappers to do the reading and writing.
Core information
  • The two tools are partners, not rivals. Integration Procedures usually call one or more Data Mappers and are more flexible and powerful, but for some use cases a single Data Mapper is enough.
More details and nuances
  • Read-then-write is the most common trigger for an Integration Procedure. A Data Mapper reads or writes, so a requirement to both read and write needs at least two Data Mappers, and an Integration Procedure is what runs them together.