Public Sector Solutions provides a specific data model to handle this scenario. The PublicComplaint object is designed as the intake mechanism for constituents to report issues, service requests, or concerns via a public-facing portal, such as an Experience Cloud site. It supports submissions from both authenticated and anonymous (guest) users. Upon submission of a PublicComplaint record, a separate Case record can be automatically or manually created for internal staff to manage the investigation, follow-up, and resolution. This two-object approach perfectly aligns with the requirement to track the constituent's report and the internal investigation as separate records.

A. Use the Complaint Case and Case objects.

"Complaint Case" is not the correct name for the standard object provided by Public Sector Solutions for this purpose. The correct object is PublicComplaint.

B. Use record types on Case, one for the constituents and one for internal staff.

This approach uses a single object (Case) and does not meet the requirement to "separately track their investigations and any follow-up in a separate Case."

D. Use a custom object for the Complaint with a lookup relationship to Case.

While technically feasible, this approach ignores the standard, out-of-the-box functionality provided by the PublicComplaint object, which is specifically designed for this use case.

1. Salesforce Help, Public Sector Solutions, Manage Complaints and Service Requests: "Use the Public Complaint object to capture complaints and service requests from the public. When a complaint is submitted, a case is created for an agent to investigate and resolve." This documentation explicitly describes the intended use of the PublicComplaint object for intake and its relationship with the Case object for investigation.

2. Salesforce Developer Guide, Public Sector Solutions, Object Details, PublicComplaint: The developer documentation outlines the fields and purpose of the PublicComplaint object (API Name: PublicComplaint). It is described as an object to "Store information about a complaint or service request submitted by a person from the public." This confirms it is the correct standard object for the initial report.

3. Salesforce Help, Public Sector Solutions, Set Up Case Management for Public Sector Solutions: This guide details the configuration process, stating, "Public Sector Solutions uses the Case object to help you manage and track customer issues... You can also create cases from public complaints." This reinforces the intended workflow of creating a Case from a PublicComplaint.

An Integration Procedure is the most appropriate feature for this requirement. It is a declarative, server-side process designed to execute multiple actions in a single server call. It can orchestrate calls to different data sources, such as making an HTTP callout to an external system to fetch permit fees and simultaneously using a DataRaptor to retrieve discount information from a Salesforce custom object. It can then perform calculations on the aggregated data before returning the final fee amount. This aligns perfectly with the scenario's need for multi-source data retrieval and processing.

A. DataRaptor: A DataRaptor is used to retrieve, transform, or write Salesforce data. It cannot, by itself, make a callout to an external system to fetch data.

C. FlexCard: A FlexCard is a user interface component used to display contextual information and provide access to actions. It is not the tool used for the backend data orchestration and calculation logic.

D. OmniScript: An OmniScript provides a guided user path. While it can call an Integration Procedure or an HTTP action, its primary purpose is user interaction, not complex, server-side data aggregation from multiple systems. The Integration Procedure is the specialized tool for that backend logic.

1. Salesforce Help, OmniStudio Documentation, "Integration Procedures": "An Integration Procedure is a declarative, server-side process that executes multiple actions in a single server call. Integration Procedures can read and write data from Salesforce and from external systems (using REST API calls)... Use an Integration Procedure to access and transform data from third-party sources." This directly supports the use of an Integration Procedure to call an external system and process data.

2. Salesforce Help, OmniStudio Documentation, "DataRaptors": "DataRaptors are a configurable service for retrieving, transforming, and updating data." This documentation specifies their role is confined to data operations, primarily within Salesforce, and does not include orchestrating external API calls.

3. Salesforce Help, OmniStudio Documentation, "OmniStudio FlexCards": "FlexCards are cards that display contextual information and provide access to relevant tasks for a customer... They are the building blocks of the UI." This confirms FlexCards are a presentation-layer component.

4. Salesforce Trailhead, OmniStudio Architecture, "Choose the Right OmniStudio Tool": This module distinguishes the tools' purposes. It positions Integration Procedures for "bundling actions together to create a single, server-side service" and handling "data from multiple sources," while OmniScripts are for "creating a guided path for completing a business process." This architectural guidance confirms the Integration Procedure is the correct choice for the described data logic.

To deploy a digital experience for emergency response using Public Sector Solutions (PSS), several core configurations are required. First, the Emergency Response Management (ERM) for PSS Managed Package must be installed, as it contains the specific components, objects, and business logic for the emergency response use case. Second, Person Accounts must be enabled. PSS is built on a constituent-centric data model where Person Accounts are used to represent individual citizens, which is essential for managing requests and services. Third, Web-to-Case must be enabled to allow the public-facing digital experience forms to capture service and program requests from constituents and businesses and create Case records in Salesforce, which is a fundamental part of the solution's intake process.

C. Enable Email-to-Case: While a valid channel for case creation, it is not a direct prerequisite for configuring the PSS digital experience components, which primarily use web forms.

E. Install the ERM for PSS Unmanaged Package: Salesforce distributes the official ERM solution as a managed package to ensure support and upgradeability. An unmanaged package is incorrect.

1. Salesforce Help, Public Sector Solutions, "Install Emergency Response Management": This document outlines the installation process, stating, "Install the Emergency Response Management for Public Sector Solutions managed package from the Public Sector Solutions Installer." This directly supports option A.

2. Salesforce Help, Public Sector Solutions, "Prerequisites for Installing Public Sector Solutions": This guide explicitly lists enabling Person Accounts as a critical prerequisite. It states, "Before you install Public Sector Solutions, enable Person Accounts in your org." This supports option B.

3. Salesforce Help, Public Sector Solutions, "Set Up Emergency Response Management": In the post-installation steps, this guide details configuring the "Request for Assistance" functionality, which relies on web-based case submission. It instructs the administrator to, "Set up Web-to-Case to allow constituents to submit cases from your Experience Cloud site." This supports option D.

The most secure and scalable approach for this scenario involves two key steps. First, establish the most restrictive baseline security model by setting the External Organization-Wide Defaults (OWD) to 'Private' for all relevant objects (Case, Account, Grant Application). This ensures that, by default, external users cannot see any records they do not own. Second, use Sharing Sets to grant users access to specific records they need. Sharing Sets are designed for high-volume Experience Cloud sites to grant users access to records that are associated with their account or contact, which directly addresses the need for users to see their own cases and applications.

A. Set up Sharing Rules to grant authenticated users access to their Cases. Applications, and Accounts: Sharing Rules are not the optimal tool for this use case. They are designed to open up access based on record ownership or criteria, not a user's direct relationship to an account, and are less performant than Sharing Sets for large-scale external user access.

B. Set Org-Wide Defaults for External Users to Hidden for everything: "Hidden" is not a valid Organization-Wide Default setting in Salesforce. The most restrictive and appropriate setting is "Private."

1. Salesforce Help, "External Organization-Wide Defaults": "To secure your org, we recommend setting the default internal and external access to the most restrictive level—Private. You can then use other record-level security and sharing tools to grant access to users who need it." This supports setting the OWD to Private (Option D) as the foundational step.

2. Salesforce Help, "Control Access to Records Using Sharing Sets": "Sharing sets grant site users access to records that are associated with their accounts or contacts based on their user profiles... A sharing set grants access to any record associated with an account or contact that matches the user's account or contact." This directly supports using Sharing Sets (Option C) to provide the required record access.

3. Salesforce Architects, "Record-Level Security for External Users": This guide outlines the external sharing model, stating, "The external sharing model determines the baseline record access for external users... After you’ve set the org-wide defaults, you can use other record-level security features to grant access to external users. For partner and customer users, you can use sharing sets..." This confirms the two-step process of setting OWD to Private and then using Sharing Sets.

4. Public Sector Solutions Developer Guide, "Set Up Security and Sharing": While discussing the overall security model, the guide emphasizes leveraging the core platform's security features. It states, "Configure organization-wide sharing defaults to restrict access to records... For external users, such as constituents who log in to an Experience Cloud site, set the default external access to Private for all objects." This reinforces the use of Private External OWDs as a best practice within Public Sector Solutions.

The grantmaking lifecycle follows a logical and sequential process to ensure effective and transparent distribution of funds. The process begins with the Plan phase, where the grantmaker defines the funding program's goals, budget, and requirements. The subsequent Engage phase involves outreach to potential applicants and the intake of applications. After applications are submitted, the Award phase includes the review, scoring, and selection of grantees, culminating in the disbursement of funds. Finally, the Review phase covers post-award management, including monitoring grantee progress, collecting reports, and evaluating the overall impact of the grant.

A. Engage, Award, Plan, Review.

This is incorrect because planning must precede engaging with applicants; a program's framework must be established before it is opened to the public.

C. Review, Award, Engage, Plan

This order is reversed. Reviewing performance is a post-award activity, and planning is the foundational first step of the entire lifecycle.

1. Salesforce Help Documentation: "The Grantmaking Lifecycle". This document explicitly outlines the four key stages in the correct order: "Plan your funding programs and opportunities. Engage with your applicants. Award your grants. Review your grantee's performance."

2. Trailhead by Salesforce: "Grants Management for Grantmakers" module, "Explore the Grantmaking Process" unit. This unit details the grantmaking journey, starting with planning funding programs, then moving to engaging applicants, awarding grants, and finally managing the post-award process (review). This aligns directly with the Plan, Engage, Award, Review sequence.

Salesforce Public Sector Solutions (PSS) licensing often includes usage-based entitlements, particularly for transactions like license and permit applications submitted by external users. Configuring and deploying numerous OmniScript forms on an Experience Cloud site facilitates the submission of these applications by the public. Each submitted application can consume an entitlement. Therefore, enabling a high volume of application submissions through these forms directly drives the consumption of these entitlements, which in turn impacts the overall licensing cost for the organization. The cost is tied to the volume of transactions (applications processed), not the configuration of the forms themselves, but making them available is the direct enabler of that consumption.

B. The Application Object Usage Record is a mechanism for tracking consumption against purchased entitlements. Configuring this record is for monitoring purposes and does not, in itself, generate the cost.

C. Business Regulatory Authorization Type Dependencies are a standard configuration feature within the PSS data model to define prerequisites. This is core functionality and does not have a direct, separate licensing cost.

D. Record types are a standard Salesforce Platform feature used to manage different business processes. Creating record types on objects does not incur additional licensing costs.

1. Salesforce Help, Public Sector Solutions Documentation, "Track Your Public Sector Solutions Usage": This document explains the concept of usage-based entitlements in Public Sector Solutions. It states, "Public Sector Solutions uses usage-based entitlements on a number of objects... When your org exceeds a usage-based entitlement's allocated limit, you can't create records for that object." This confirms that creating application records (facilitated by OmniScript forms) is the activity that consumes entitlements and drives cost. The document specifically lists "Licenses and Permits Applications" as a tracked entitlement.

2. Salesforce Help, Public Sector Solutions Documentation, "Set Up an Experience Cloud Site for Constituents": This guide details how to use Experience Cloud sites to provide services to the public, including application submission. It outlines deploying OmniScripts and other components for external users, which is the primary channel for consuming application entitlements. The act of making these forms available for submission is the direct precursor to incurring usage-based costs.

3. Salesforce Help, Public Sector Solutions Developer Guide, "IndividualApplication": The documentation for the IndividualApplication object and related objects (like BusinessLicenseApplication) underpins the licensing and permitting data model. While the documentation itself doesn't specify pricing, it defines the objects whose record creation is tracked against the usage-based entitlements mentioned in the primary PSS documentation.

OmniScript is the recommended Salesforce Public Sector Solutions tool for creating guided, interactive experiences for constituents. It allows for the creation of a dynamic flow where a user can select their Business Type. Based on this selection, conditional logic within the OmniScript can display the specific set of associated permits and licenses required. This approach provides a user-friendly, step-by-step discovery process that can be seamlessly embedded into an Experience Cloud site, directly addressing the city's requirement to show constituents exactly what they need to apply for.

B: The Business Regulatory Authorization Type Dependency object is used to define prerequisites between two specific permits (e.g., Permit A is required before applying for Permit B), not to associate a collection of permits with a Business Type.

C: While technically feasible, creating a custom object and a FlexCard is a custom development approach. The recommended best practice is to leverage standard, out-of-the-box tools like OmniScript, which are purpose-built for guided interactions and require less custom effort.

D: This custom solution proposes using a standard list view, which provides a less intuitive and less guided user experience compared to the dynamic, interactive nature of an OmniScript.

1. Salesforce Help, Public Sector Solutions Developer Guide, OmniScript for Public Sector Solutions: "OmniScripts provide a guided path for completing a business process and are a perfect fit for public sector use cases... For example, you can create an OmniScript that guides a constituent through a permit application." This establishes OmniScript as the primary tool for guided user processes.

2. Salesforce Help, Public Sector Solutions Developer Guide, Public Sector Solutions Data Model: The documentation for the BusinessRegulatoryAuthTypeDependency object states its purpose is to "Define the dependency between two business regulatory authorization types." This confirms it is for permit-to-permit dependency, not for linking a set of permits to a business category.

3. Salesforce Help, Public Sector Solutions Administrator Guide, Set Up Guided Intake Flows with OmniScript: "Create guided intake flows with OmniScript to provide a simple, user-friendly experience for your constituents on your portal... Use the drag-and-drop editor to build the flow, and add elements for conditional questions, to show different pages based on a user's answers." This directly supports the use of OmniScript with conditional logic for this exact use case.

The Emergency Response Management (ERM) package for Public Sector Solutions provides a dedicated framework for managing volunteers. A key component is the volunteer portal, built on Experience Cloud, which allows volunteers to self-register for projects and shifts, and subsequently log the hours they have worked. The system is also designed to dynamically manage resource allocation. When a volunteer shift is canceled or a volunteer unregisters, the data model automatically updates the counts for 'registered volunteers' and 'volunteers needed' on the relevant shift records. This ensures that program managers have an accurate, real-time view of staffing levels and requirements.

A. Chatbot for volunteers: While a chatbot can be configured using Salesforce Einstein Bots, it is not an out-of-the-box feature included specifically within the ERM volunteer management package.

D. Volunteers can automatically claim reimbursements for the expenses: The standard ERM package focuses on volunteer registration, scheduling, and time tracking. It does not include a native, automated expense reimbursement feature, which would require custom development or integration.

1. Salesforce Help, Public Sector Solutions Documentation, "Manage Volunteers and Their Shifts in Emergency Response Management": This document explicitly states, "Volunteers can sign up for projects and shifts, and report the time they spend on volunteer activities." It also details the data model where Volunteer Shift records track Number of Volunteers Needed and Number of Registered Volunteers, which are updated as volunteers register or unregister, supporting the automatic update logic.

2. Salesforce Help, Public Sector Solutions Documentation, "Set Up a Volunteer Portal": This guide outlines the steps to create an Experience Cloud site for volunteers. It describes the functionality that allows users to "view and sign up for volunteer projects and shifts" and "submit the hours they've worked," directly confirming option C.

3. Salesforce Help, Public Sector Solutions Documentation, "Emergency Program Management Data Model": The data model for ERM includes objects like VolunteerProject, VolunteerShift, and VolunteerHours. The fields within the VolunteerShift object, such as DesiredNumberofVolunteersc and a rollup summary for registered volunteers, confirm the system's capability to track and update volunteer counts for shifts, as described in option B.

The core requirement is to implement a standardized, repeatable set of due diligence activities that can be tracked separately and run in parallel for each new organization (Account). The most appropriate feature for this is an Action Plan Template. A consultant would configure an Action Plan Template to define the specific tasks required for due diligence, such as "Verify Organization Details" and "Collect Statutory Documents." This template acts as a reusable blueprint. When a new organization registers, an Action Plan instance is created from this template, automatically generating the predefined tasks for that specific Account, ensuring a consistent and compliant process.

A. A Path targeted at Account: A Path is a visual tool for guiding users through the stages of a linear process. It does not create or manage a set of distinct, parallel tasks.

B. A Support Process targeted at Account: Support Processes are a feature of the Case object used to define different lifecycles for support tickets. They are not applicable to the Account object for due diligence.

C. An Action Plan targeted at Account: An Action Plan is the instance of the process created from a template for a specific record. The consultant's task is to configure the reusable blueprint, which is the Action Plan Template, not the individual instance.

1. Official Salesforce Documentation - Public Sector Solutions: Action Plans:

"Create action plan templates for tasks that your users must complete on a regular basis. For example, create a template for the tasks involved in an application review process for a business license or a grant program. When you create an action plan from a template, the tasks from the template are automatically added to the action plan."

Source: Salesforce Help, Public Sector Solutions Documentation, "Create Action Plan Templates". This explicitly states that the template is the configurable, reusable component for regular processes.

2. Official Salesforce Documentation - Public Sector Solutions: Set Up Action Plans:

"To get your users started with Action Plans, create action plan templates that are tailored to your business processes."

Source: Salesforce Help, Public Sector Solutions Documentation, "Set Up Action Plans". This confirms that the setup and configuration work performed by a consultant involves creating the templates.

3. Official Salesforce Documentation - Public Sector Solutions: How Action Plans Work:

"Action plan templates are the reusable framework from which users create action plans. In a template, you define the tasks and their deadlines."

Source: Salesforce Help, Public Sector Solutions Documentation, "How Action Plans Work". This reference clearly distinguishes the template (the configured framework) from the action plan (the instance). The consultant's configuration work is on the template.

OmniOut is the specific OmniStudio feature designed to deploy and host OmniStudio components, such as OmniScripts and FlexCards, on an external, non-Salesforce website. In this scenario, the agency can build the grant application form using an OmniScript, which provides a guided, step-by-step user experience. OmniOut then generates the necessary code to embed this OmniScript directly into the agency's existing public-facing portal. This allows constituents to complete and submit the application from the external site, with the data being seamlessly passed to Salesforce Public Sector Solutions objects using underlying DataRaptors or Integration Procedures. This approach directly meets the requirement without needing to build a custom API integration from scratch.

B. FlexCards: FlexCards are primarily used to display contextual information and launch actions, not to build complex, multi-step data entry forms like a grant application.

C. DataRaptor: DataRaptors are backend services for retrieving, transforming, and writing Salesforce data. While an OmniScript would use a DataRaptor to save the application data, DataRaptor itself does not provide the user interface or the mechanism to embed it on an external site.

D. Integration Procedure: An Integration Procedure can be exposed as a REST API endpoint. While the external portal could call this endpoint to submit data, it would require the agency to custom-build the entire application form and client-side logic on their portal. OmniOut provides a more complete, low-code solution by enabling the entire user interface to be embedded.

1. Salesforce Official Documentation, OmniStudio: "OmniOut for OmniScripts and FlexCards." The documentation states, "With OmniOut, you can run OmniScripts and FlexCards on any external web page... For example, run an OmniScript on a non-Salesforce domain to enable users to change their address without logging into your application." This directly aligns with embedding a grant application on an external government portal. (Accessed via Salesforce Help Portal, OmniStudio > OmniOut).

2. Salesforce Official Documentation, OmniStudio: "DataRaptors." The documentation defines DataRaptors as "a configurable service for retrieving, transforming, and updating data." This positions them as a data service layer, not a UI or external hosting solution. (Accessed via Salesforce Help Portal, OmniStudio > OmniStudio DataRaptors).

3. Salesforce Official Documentation, OmniStudio: "Integration Procedures." The documentation notes, "Expose Integration Procedures as REST APIs that can be called by third-party services." This confirms their role as a server-side integration point, distinct from OmniOut's function of embedding UI components externally. (Accessed via Salesforce Help Portal, OmniStudio > OmniStudio Integration Procedures).