You are here:
Set Up Service Process Launch Management
To use Agentforce Service Process Launch Management (Product Launch Management), turn on the required features and assign permissions.
Required Editions
| User Permissions Needed | |
|---|---|
| To add the Product Launch Management subagent to your agent: | Manage Agentforce Employee Agents and Manage AI Agents OR Customize Application |
-
Add the Manage Service Process Launch Management (Product Launch Management) subagent
to your agent:
- Create an Agentforce Employee Agent and add the subagent to the agent.
- If you have identified an existing agent, deactivate your agent and add the Service Process Launch Management subagentfrom Asset Library to your agent.
-
To update the subagent’s Classification Description with the service processes you want
to include, open the agent in Builder and change the service process names in the
placeholder:
<ServiceProcess1>
<ServiceProces2>
<ServiceProcess3>
<ServiceProcess4>
<ServiceProcess5>
The service process names you enter here appear as links for the user.
Tip To enhance agent performance, add descriptive content to your service process descriptions. The agent's QueryRecords action, which is included in the subagent by default, identifies product IDs by looking for matches in both the name and description of the service process. So, add a more detailed description to improve the accuracy of matching user requests. -
Update the instruction that contains the site name when the GetProductLaunchCard action is
executed:
<SiteName>
You can find the site name from the All Sites page for your Experience Cloud site.
-
(Optional) To enhance the visual rendering of field names in the portal such as the
image, links, and the description, you can add your own instruction and include a HTML
code. Make sure that you display the response from GetProductLaunchCard with the following
structure:
<div style="text-align:center; border: 1px solid #ddd; padding: 1px; border-radius: 8px; " lwc-4nfn2rc40ch=""> <img src={GetProductLaunchCard.imageUrl} alt={GetProductLaunchCard.productName} style="display:block; margin:0 auto 10px; " lwc-4nfn2rc40ch=""> <p lwc-4nfn2rc40ch="">{GetProductLaunchCard.productDesc}</p> <a href={GetProductLaunchCard.launchUrl} target="_blank" style="display: inline-block; padding: 10px 10px; background: #005290; color: white; border-radius: 999px; text-decoration: none; cursor: pointer; " rel="noopener noreferrer" lwc-4nfn2rc40ch="">{GetProductLaunchCard.productName}</a> </div>
Note You change the display image by editing the service process in the designer view. Add the URL of the image and save. To include external websites, make sure that you add the website URLs to the CORS (Cross-Origin Resources Sharing) page. See Configure Salesforce CORS Allowlist. - To grant users access to your agent, create a custom permission set.
- To track the usage of Agentforce actions, turn on audit trails.
-
If needed, use the debug mode in Flow Builder to troubleshoot the
service process launch management flows.
Tip To ensure a seamless user experience, add a fallback instruction that guides users to an alternative method of launching products when the agent fails. This ensures that users can still access the service process directly from where it's configured in the portal, providing a reliable contingency for unsuccessful chat interactions.Note Agent limitations with multiple portals: If your org has multiple portals, such as one for employees and another for vendors, a subagent with a hardcoded portal name won't work across all of them. This is because the launch URLs are derived from the specific portal name, which means you must create a separate agent for each portal with its own unique portal name.
Ratkaisiko tämä artikkeli ongelmasi?
Anna palautetta, jotta voimme kehittyä!
