Ready to capture
Agent Scripting: Side-by-Side Comparison
Same Architecture. Different Syntax. 24-Month Gap.
October 2023 ← 24 months → October 2025
| FEATURE | Agentman PRODUCTIONOct 2023 | Salesforce AgentScript BETAOct 2025 |
|---|---|---|
| Topic/Task Definition | {
"taskName": "ProcessOrder",
"steps": [...]
} | topic forecast_service:
description: "Weather forecasts..."
reasoning_instructions: ... |
| Reasoning Instructions | "steps": [
"Call tool with user input",
"Process the result",
"Route to next task"
] | reasoning_instructions:
>>
Deliver comprehensive forecasts.
Call tool with parameters.
Present results to user.
|
| Variable References | "Call tool with $order_id"
"Store in $order_data" | "Call with {{@variable.user_city}}"
set @variable.forecast_data =
@result.daily_forecast |
| Tool Calls & Parameters | "Call ${tool:GetWeatherForecast}
with $user_city,
$user_country,
$forecast_days" | @action.Get_Weather_Forecast
with city=@variable.user_city
with country=@variable.user_country
with forecast_days |
| Conditional Logic | "If user mentions severe weather →
Go to ${task:SevereAlerts}
Else if needs current weather →
Go to ${task:CurrentWeather}" | "If severe weather detected →
{{@action.alert_monitoring}}
can transition to alerts.
If user wants current conditions →
{{@action.current_conditions}}" |
| Task Transitions | "Go to ${task:SevereWeatherAlerts}"
// With context
"Go to ${task:CurrentWeather}
for current conditions" | @utils.transition
to @topic.severe_weather_alerts
as alert_monitoring
description: "Monitor severe
weather..." |