Hi everyone,
I’m reaching out to see if anyone has encountered a similar issue. We are an ISV Partner currently packaging our first Employee Agent and our goal is to package only the Subagent and its associated Actions
. Is that feasible?
Here’s what we have done so far:
- Created a namespace Scratch Org.
- Built an Agent.
- Built a Subagent in Agentforce Assets.
- Built each Action in Agentforce Assets and linked them to the Subagent.
- Added the Subagent to the Agent using Agentforce Builder → Add the Asset from Library.
Issue
After adding the Subagent (with its linked Actions) using Add the Asset from Library, saving the Agent, and attempting to commit the first Agent version, we receive the following error:
The strange part is that the Subagent and its Actions are already configured correctly.
The only workaround we have found is to manually choose the Reference Action, select the correct picklist value again, and save the Subagent. After doing this, we can successfully commit the Agent.
Question
Has anyone successfully built a custom Subagent with its associated Actions and then added it to an Agent using Add the Asset from Library
, without having to manually re-select the Reference Action picklist value every time?
We would appreciate any guidance on how to properly package/reference these Agentforce Assets so that the Subagent retains the correct Action configuration and can be committed without triggering the restricted picklist error.
Thanks in advance!
#Agentforce