Universal Containers (UC) requires a solution with a custom UX for users to input a sales order number, followed by invoking a custom prompt template to generate and display a summary. Let's evaluate each option based on this requirement and Salesforce Agentforce capabilities.
Option A: Create an autolaunched flow and invoke the prompt template using the standard " Prompt Template
" flow action.An autolaunched flow is a background process that runs without user interaction, triggered by events like record updates or platform events. While it can invoke a prompt template using the " Prompt Template " flow action (available in Flow Builder to integrate Agentforce prompts), it lacks a user interface.
Since UC explicitly needs a custom UX for users to enter a sales order number, an autolaunched flow cannot meet this requirement, as it doesn't provide a way for users to input data directly.
Option B: Create a template-triggered prompt flow and invoke the prompt template using the standard " Prompt Template " flow action.There's no such thing as a " template-triggered prompt flow " in Salesforce terminology. This appears to be a misnomer or typo in the original question. Prompt templates in Agentforce are reusable configurations that define how an AI processes input data, but they are not a type of flow. Flows (like autolaunched or screen flows) can invoke prompt templates, but " template-triggered " is not a recognized flow type in Salesforce documentation. This option is invalid due to its inaccurate framing.
Option C: Create a screen flow to collect the sales order number and invoke the prompt template using the standard " Prompt Template " flow action.A screen flow provides a customizable user interface within Salesforce, allowing users to input data (e.g., a sales order number) via input fields. The " Prompt Template " flow action, available in Flow Builder, enables integration with Agentforce by passing user input (the sales order number) to a custom prompt template. The prompt template can then query related data (e.g., sales order header and details) and generate a summary, which can be displayed back to the user on a subsequent screen.
This solution meets UC's need for a custom UX and seamless integration with Agentforce prompts, making it the best fit.
Why Option C is Correct:
Screen flows are ideal for scenarios requiring user interaction and custom interfaces, as outlined in Salesforce Flow documentation. The " Prompt Template " flow action enables Agentforce's AI capabilities within the flow, allowing UC to collect the sales order number, process it via a prompt template, and display the result- all within a single, user-friendly solution. This aligns with Agentforce best practices for integrating AI-driven summaries into user workflows.
References:
Salesforce Help: Flow Builder > Prompt Template Action - Describes how to use the " Prompt Template " action in flows to invoke Agentforce prompts.
Trailhead: Build Flows with Prompt Templates - Highlights screen flows for user-driven AI interactions.
Agentforce Studio Documentation: Prompt Templates - Explains how prompt templates process input data for summaries.