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).