Understanding the Limitations

Teams running Agentforce have hit this issue, where the Agent Script, once committed, includes the GenAIPlannerBundle with odd, hash-like or possibly Base64 encoded script and graph references. These elements are not standard and make the planner bundle unpackagable, preventing it from being turned into a template.

The root cause of this issue lies in the way Agent Script is handled within Agentforce, specifically how the planner bundle is constructed and the lack of documentation on these encoded parts.

This limitation means that even though you can retrieve the normal metadata like GenAIPlannerBundle, GenAIFunction, etc., for the agent from the org, the planner’s additional encoded parts, which contain crucial instructions for the LLM and deterministic processes, are not accessible in a standard, understandable format.

Workarounds and Potential Solutions

While there isn’t a straightforward way to package Agent Script, a possible workaround involves creating a template from the Agent Script agent files retrieved from the org once the agent is committed or published. However, this approach lacks the instructions due to the templating system’s inability to understand the encoded files.

This workaround, although not ideal, could be used for distribution to small, trusted customer bases by providing them with the script directly.

Conclusion and Recommendations

Given the current state of Agent Script packaging in Agentforce, it’s clear that there are significant limitations that hinder the process. The lack of official support or documentation from Salesforce on this matter further complicates the situation.

Heads up: As of the latest updates, there are no concrete plans or timelines from Salesforce regarding the improvement of Agent Script packaging for Agentforce customers.

Checklist for Agentforce Customers Considering Agent Script

• Understand the current limitations of packaging Agent Script in Agentforce.
• Explore workarounds such as creating templates from retrieved agent files.
• Consider the implications of distributing scripts directly to trusted customers.
• Stay updated with any official announcements or updates from Salesforce regarding Agentforce and Agent Script.
• Evaluate the feasibility of using Agent Script based on your specific business needs and the current state of the technology.
• Engage with the community and Salesforce support to push for more documentation and support on this topic.

What is the current status of packaging Agent Script in Agentforce?

As of the latest information, packaging Agent Script is not feasible due to the encoded references in the GenAIPlannerBundle.

Are there any workarounds for distributing Agent Script?

Yes, creating a template from the agent files and distributing the script directly to trusted customers are possible workarounds.

Has Salesforce announced any plans for improving Agent Script packaging?

There are no concrete plans or timelines announced by Salesforce for improving the packaging of Agent Script for Agentforce customers.

What should Agentforce customers do regarding Agent Script?

Customers should evaluate their needs, consider the limitations, and stay updated with any official announcements from Salesforce.

How can the community help with the issue of Agent Script packaging?

The community can help by sharing experiences, workarounds, and by pushing for more documentation and support from Salesforce on this topic.