Understanding the Limitations of Agent Script

Agent Script is still a relatively new feature, and as such, it has several limitations that can cause issues for teams trying to migrate from classic Agentforce. One of the main limitations is the lack of support for packaging, which is still in beta and not yet fully functional.

The root cause of the migration issues is the current state of Agent Script, which is still in development and has not yet reached full feature parity with classic Agentforce. This means that certain features, such as packaging and agent tests, are not yet fully supported or are still in beta.

Another limitation of Agent Script is the lack of documentation on how to use it with 2GP packaging. The old packageable constructs, such as Bot, BotTemplate, and GenAiPlannerBundle, do not seem to apply anymore, and there is no clear guidance on how to package Agent Script agents.

Overcoming the Blockers

To overcome the blockers and migrate successfully to Agent Script, teams need to develop workarounds and carefully review the current limitations of the feature. For example, they can use the classic Agentforce for certain features, such as packaging and agent tests, until Agent Script reaches full feature parity.

Additionally, teams can use resources such as the Claude Code skill for Agentscript, which provides a condensed version of the Salesforce documentation and tracks known issues.

Step-by-Step Solution

To migrate to Agent Script, teams should follow these steps:

Agent Script migration steps

1. Review the current limitations of Agent Script
2. Develop workarounds for packaging and agent tests
3. Use the classic Agentforce for certain features until Agent Script reaches full feature parity
4. Use resources such as the Claude Code skill for Agentscript
5. Carefully test and validate the migration

Heads up: The migration to Agent Script requires careful planning and testing to ensure a smooth transition.

Checklist for Migration

Pre-Migration Checklist

• Review the current limitations of Agent Script
• Develop workarounds for packaging and agent tests
• Use the classic Agentforce for certain features until Agent Script reaches full feature parity
• Use resources such as the Claude Code skill for Agentscript
• Carefully test and validate the migration
• Document the migration process and any workarounds used
• Plan for ongoing support and maintenance

Frequently Asked Questions

What are the main limitations of Agent Script?

The main limitations of Agent Script are the lack of support for packaging and the limited documentation on how to use it with 2GP packaging.

How can I overcome the blockers and migrate to Agent Script?

To overcome the blockers and migrate to Agent Script, teams need to develop workarounds and carefully review the current limitations of the feature.

What resources are available to help with the migration?

Resources such as the Claude Code skill for Agentscript can provide a condensed version of the Salesforce documentation and track known issues.

How can I ensure a smooth transition to Agent Script?

To ensure a smooth transition to Agent Script, teams should carefully test and validate the migration, document the migration process and any workarounds used, and plan for ongoing support and maintenance.

What is the current state of Agent Script?

Agent Script is still a relatively new feature and is still in development. It has not yet reached full feature parity with classic Agentforce, and certain features, such as packaging and agent tests, are not yet fully supported or are still in beta.

How can I stay up-to-date with the latest developments in Agent Script?

Teams can stay up-to-date with the latest developments in Agent Script by following the Salesforce documentation and release notes, as well as participating in the Agentforce community and forums.