mirror of
https://github.com/forcedotcom/afv-library.git
synced 2026-07-31 04:01:24 +08:00
* @W-21955450@ Rename topic to subagent for Agent Script v2
Aligns with Agent Script v2 naming standards where `topic` is renamed
to `subagent` across all skill documentation and templates.
Changes:
- Agent Script templates: topic keyword → subagent keyword
- References: @topic.* → @subagent.*
- Documentation: Updated all skill references and guides
- Natural language references preserved in comments/descriptions
* Rename start_agent topic_selector to agent_router
Completes the topic → subagent terminology alignment by:
1. Renaming start_agent from topic_selector to agent_router (15 agent files)
2. Updating template topic declarations: topic {{placeholder}} → subagent {{placeholder}} (5 files)
3. Updating all @subagent.topic_selector references to @subagent.agent_router (35 occurrences)
4. Updating documentation: prose, examples, and diagrams (10 markdown files)
5. Updating comments to use agent_router terminology
Files affected:
- 22 agent template files
- 10 documentation/reference markdown files
- Template component files
The agent_router name is more descriptive of its actual function
(routing to different subagents) and completes the Agent Script v2
terminology standardization.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Rename files with "topic" to use "subagent" terminology
Completes the topic → subagent terminology alignment by renaming
files and updating all references:
**Files renamed (5):**
- multi-topic.agent → multi-subagent.agent
- template-single-topic.agent → template-single-subagent.agent
- template-multi-topic.agent → template-multi-subagent.agent
- topic-with-actions.agent → subagent-with-actions.agent
- agent-topic-map-diagrams.md → agent-subagent-map-diagrams.md
**References updated (6 docs):**
- Updated all filename references to point to new filenames
- Updated "Topic Map" → "Subagent Map" throughout documentation
- Updated "multi-topic"/"single-topic" → "multi-subagent"/"single-subagent"
Files modified:
- README.md, SKILL.md, agent-spec-template.md
- assets/agents/README.md, assets/README-legacy.md
- references/agent-design-and-spec-creation.md
This ensures consistent "subagent" terminology across filenames,
file content, and all documentation references.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Complete topic-to-subagent terminology update across skills
Comprehensive update replacing "topic" with "subagent" terminology throughout
the developing-agentforce and testing-agentforce skills to align with Agent
Script's `subagent` block naming.
Key changes:
- "Topic Selector" → "Subagent Router" in all agent templates and docs
- "Topic/action" → "Subagent/action" in documentation
- "Topic map" → "Subagent map" in diagram references
- Updated all architecture documentation to use "subagent" terminology
- Updated 19 .agent template files with new labels and comments
- Updated 8 reference documentation files with consistent terminology
API contract preservation:
- Test spec YAML files preserve "topic" terminology to match Testing Center API
- Added clarifying comments explaining topic/subagent equivalence in YAML files
- Field names like `expectedTopic` unchanged (Salesforce API requirement)
Preserved terms:
- "off-topic" (standard phrase for out-of-scope)
- "expectedTopic" field (Testing Center API)
- "platform topics" (Salesforce guardrail features)
32 files changed, 379 insertions(+), 366 deletions(-)
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* Complete comprehensive topic-to-subagent terminology update
Thorough update replacing all remaining "topic" references with "subagent"
terminology across developing-agentforce, testing-agentforce, and
observing-agentforce skills to fully align with Agent Script's `subagent`
block naming.
Key changes:
- Agent Script syntax: @topic.<name> → @subagent.<name>
- Agent Script syntax: topic.actions → subagent.actions
- Shell script patterns: ^topic → ^subagent
- Documentation: "topic instructions" → "subagent instructions"
- observing-agentforce skill: Updated all agent architecture references
- Template files: Updated all inline comments and descriptions
- Variable names in scripts: TOPIC → SUBAGENT
Specific updates:
- 45 files changed, 294 insertions, 294 deletions
- Updated all Agent Script code examples to use @subagent syntax
- Updated observing-agentforce issue classification guide
- Updated shell script patterns in diagnostic tools
- Updated Apex comments to clarify topic field maps to subagents
Preserved (as required):
- "off-topic" and "off_topic" (standard out-of-scope phrase)
- Testing Center API fields: expectedTopic, topic: in YAML
- API response fields: .topic, generatedData.topic, topic_assertion
- STDM field names: ssot__TopicApiName__c (with clarifying docs)
- Template placeholders in test specs (API values)
- "Topic hash drift" (API field behavior)
- "Email topic/purpose" (means email subject)
- Explanatory comments about API field mapping
All Agent Script syntax and documentation now consistently uses "subagent"
while preserving backward compatibility with platform API field names.
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
* a few more topic -> subagent replacements
---------
Co-authored-by: Steve Hetzel <shetzel@salesforce.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
93 lines
3.6 KiB
XML
93 lines
3.6 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!--
|
|
GenAiFunction Template: Apex Invocation (Agent Builder UI / GenAiPlannerBundle ONLY)
|
|
|
|
⚠️ NOT NEEDED for AiAuthoringBundle (Agent Script).
|
|
If using Agent Script (.agent files), use `target: "apex://ClassName"` directly
|
|
in your subagent's actions block. See SKILL.md for details.
|
|
|
|
Use Case: Register Apex @InvocableMethod as an agent action in Agent Builder UI
|
|
- Required ONLY for GenAiPlannerBundle / Agent Builder UI path
|
|
- Works with GenAiPlugin (Subagent) for organization
|
|
|
|
Prerequisites:
|
|
1. Apex class with @InvocableMethod annotation must be deployed first
|
|
2. GenAiPlugin (Subagent) to organize functions (optional but recommended)
|
|
|
|
Setup Steps:
|
|
1. Replace all {{placeholder}} values
|
|
2. Deploy Apex class first
|
|
3. Create input/schema.json and output/schema.json (see below)
|
|
4. Deploy this GenAiFunction bundle
|
|
5. Optionally deploy GenAiPlugin to group functions
|
|
|
|
Bundle Structure:
|
|
force-app/main/default/genAiFunctions/
|
|
└── {{FunctionName}}/
|
|
├── {{FunctionName}}.genAiFunction-meta.xml (this file)
|
|
├── input/
|
|
│ └── schema.json (input parameters)
|
|
└── output/
|
|
└── schema.json (output parameters)
|
|
|
|
IMPORTANT (API v66.0):
|
|
- Only these XML elements are valid: description, invocationTarget,
|
|
invocationTargetType, isConfirmationRequired, masterLabel
|
|
- Do NOT use: <capability>, <genAiFunctionParameters>,
|
|
<genAiFunctionInputs>, <genAiFunctionOutputs>, <developerName>
|
|
- Input/output schemas go in schema.json files, NOT inline XML
|
|
-->
|
|
<GenAiFunction xmlns="http://soap.sforce.com/2006/04/metadata">
|
|
<description>{{FunctionDescription}}</description>
|
|
<invocationTarget>{{ApexClassName}}</invocationTarget>
|
|
<invocationTargetType>apex</invocationTargetType>
|
|
<isConfirmationRequired>{{true|false}}</isConfirmationRequired>
|
|
<masterLabel>{{FunctionLabel}}</masterLabel>
|
|
</GenAiFunction>
|
|
|
|
<!--
|
|
input/schema.json example:
|
|
{
|
|
"required": ["{{inputParam1}}"],
|
|
"properties": {
|
|
"{{inputParam1}}": {
|
|
"title": "{{Input Param 1 Label}}",
|
|
"description": "{{Input Param 1 Description}}",
|
|
"lightning:type": "lightning__textType",
|
|
"lightning:isPII": false,
|
|
"copilotAction:isUserInput": true
|
|
}
|
|
},
|
|
"lightning:type": "lightning__objectType"
|
|
}
|
|
|
|
output/schema.json example:
|
|
{
|
|
"properties": {
|
|
"{{outputParam1}}": {
|
|
"title": "{{Output Param 1 Label}}",
|
|
"description": "{{Output Param 1 Description}}",
|
|
"lightning:type": "lightning__textType",
|
|
"lightning:isPII": false,
|
|
"copilotAction:isDisplayable": true,
|
|
"copilotAction:isUsedByPlanner": true
|
|
}
|
|
},
|
|
"lightning:type": "lightning__objectType"
|
|
}
|
|
|
|
Lightning types:
|
|
- lightning__textType (String)
|
|
- lightning__numberType (Number/Decimal)
|
|
- lightning__booleanType (Boolean)
|
|
- lightning__dateType (Date)
|
|
- lightning__dateTimeStringType (DateTime — TDD validated v2.1.0)
|
|
- lightning__currencyType (Currency)
|
|
|
|
APEX CLASS REQUIREMENTS:
|
|
- Must be global or public with sharing
|
|
- Method must have @InvocableMethod annotation
|
|
- Input/output use @InvocableVariable wrapper classes
|
|
- Parameter names in schema.json must match @InvocableVariable field names
|
|
-->
|