mirror of
https://github.com/forcedotcom/afv-library.git
synced 2026-07-30 03:09:50 +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>
116 lines
4.6 KiB
Plaintext
116 lines
4.6 KiB
Plaintext
# Flow Action Lookup Template
|
|
# ============================
|
|
#
|
|
# This template demonstrates the pattern for calling Flow actions
|
|
# that return complex data types (SObjects, lists, custom types).
|
|
#
|
|
# Pattern: Data lookup and display using Flow actions
|
|
# Use when: Fetching records from Salesforce (Cases, Orders, Accounts)
|
|
#
|
|
# CRITICAL: When defining Flow action outputs in Agentforce Assets:
|
|
# - For SObject returns: complex_data_type_name = "lightning__recordInfoType"
|
|
# - For list[string]: complex_data_type_name = "lightning__textType"
|
|
# - For currency: complex_data_type_name = "lightning__currencyType"
|
|
|
|
system:
|
|
messages:
|
|
welcome: "Hello! I can help you look up order information."
|
|
error: "I apologize, something went wrong retrieving your data."
|
|
instructions: "You are a customer service agent helping users look up their orders."
|
|
|
|
config:
|
|
agent_name: "FlowActionLookupAgent"
|
|
agent_label: "Order Lookup Agent"
|
|
description: "Agent demonstrating Flow action patterns with complex data types"
|
|
default_agent_user: "agent@yourorg.com" # REQUIRED: Change to valid Einstein Agent User
|
|
|
|
variables:
|
|
# Customer context (from session)
|
|
customer_id: linked string
|
|
source: @session.customerId
|
|
description: "Customer ID from session context"
|
|
|
|
# Order data (populated by Flow action)
|
|
order_id: mutable string = ""
|
|
description: "Current order being viewed"
|
|
order_status: mutable string = ""
|
|
description: "Order status from lookup"
|
|
order_total: mutable string = ""
|
|
description: "Order total amount"
|
|
order_date: mutable string = ""
|
|
description: "Order date"
|
|
|
|
# Error handling
|
|
lookup_error: mutable boolean = False
|
|
description: "Whether lookup encountered an error"
|
|
|
|
start_agent entry:
|
|
description: "Entry point - welcome and route to order lookup"
|
|
reasoning:
|
|
instructions: |
|
|
Welcome the customer and offer to help with order lookups.
|
|
actions:
|
|
go_lookup: @utils.transition to @subagent.order_lookup
|
|
description: "Start order lookup"
|
|
|
|
# ============================================================
|
|
# ORDER LOOKUP SUBAGENT (Flow Action Pattern)
|
|
# ============================================================
|
|
|
|
subagent order_lookup:
|
|
description: "Look up order details using Flow action"
|
|
reasoning:
|
|
instructions: ->
|
|
# POST-ACTION CHECK: Display results if order was found
|
|
if @variables.order_status != "":
|
|
| **Order Details**
|
|
| - Order ID: {!@variables.order_id}
|
|
| - Status: {!@variables.order_status}
|
|
| - Total: {!@variables.order_total}
|
|
| - Date: {!@variables.order_date}
|
|
|
|
|
| Is there anything else you'd like to know about this order?
|
|
|
|
# ERROR CHECK: Handle lookup failures
|
|
if @variables.lookup_error == True:
|
|
| I couldn't find that order. Please check the order ID and try again.
|
|
set @variables.lookup_error = False
|
|
|
|
# INITIAL STATE: Ask for order ID
|
|
if @variables.order_id == "":
|
|
| What order would you like me to look up?
|
|
| Please provide your order ID.
|
|
|
|
actions:
|
|
# Flow action with SObject return type
|
|
# In Agentforce Assets, set outputs.order_record complex_data_type_name = "lightning__recordInfoType"
|
|
lookup_order: @actions.Get_Order_Details
|
|
description: "Look up order by ID"
|
|
with order_id = ... # LLM extracts from user message
|
|
include_in_progress_indicator: True
|
|
progress_indicator_message: "Looking up your order..."
|
|
set @variables.order_id = @outputs.order_id
|
|
set @variables.order_status = @outputs.status
|
|
set @variables.order_total = @outputs.total_amount
|
|
set @variables.order_date = @outputs.order_date
|
|
# Error handling: check if lookup failed
|
|
if @outputs.found == False:
|
|
set @variables.lookup_error = True
|
|
|
|
# Flow action returning a list of strings
|
|
# In Agentforce Assets, set outputs.product_names complex_data_type_name = "lightning__textType"
|
|
get_items: @actions.Get_Order_Line_Items
|
|
description: "Get list of items in the order"
|
|
available when @variables.order_id != ""
|
|
with order_id = @variables.order_id
|
|
|
|
clear_search: @utils.setVariables
|
|
description: "Search for a different order"
|
|
with order_id = ""
|
|
with order_status = ""
|
|
with order_total = ""
|
|
with order_date = ""
|
|
|
|
escalate_now: @utils.escalate
|
|
description: "Transfer to human agent"
|