@salesforce/afv-skills 1.7.3 → 1.7.4

package/skills/developing-agentforce/assets/{template-multi-topic.agent → template-multi-subagent.agent}

@@ -1,7 +1,7 @@
-# Multi-Topic Agent Template
+# Multi-Subagent Template
 # Copy this file to your AiAuthoringBundle directory and rename it to match
 # your agent's developer_name. Replace all placeholder values with real ones.
-# Add, remove, or rename topics as needed.
+# Add, remove, or rename subagents as needed.
 
 system:
     instructions: "You are a helpful assistant. Describe the agent's persona and purpose here."
@@ -27,23 +27,23 @@ language:
     additional_locales: ""
     all_additional_locales: False
 
-start_agent topic_selector:
-    description: "Welcome the user and determine the appropriate topic based on user input"
+start_agent agent_router:
+    description: "Welcome the user and determine the appropriate subagent based on user input"
     reasoning:
         actions:
-            go_to_topic_a: @utils.transition to @topic.topic_a
-            go_to_topic_b: @utils.transition to @topic.topic_b
-            go_to_topic_c: @utils.transition to @topic.topic_c
-            go_to_escalation: @utils.transition to @topic.escalation
-            go_to_off_topic: @utils.transition to @topic.off_topic
+            go_to_subagent_a: @utils.transition to @subagent.subagent_a
+            go_to_subagent_b: @utils.transition to @subagent.subagent_b
+            go_to_subagent_c: @utils.transition to @subagent.subagent_c
+            go_to_escalation: @utils.transition to @subagent.escalation
+            go_to_off_topic: @utils.transition to @subagent.off_topic
 
-topic topic_a:
-    label: "Topic A"
-    description: "Describe what this topic handles"
+subagent subagent_a:
+    label: "Subagent A"
+    description: "Describe what this subagent handles"
 
     reasoning:
         instructions: ->
-            | Replace this with instructions for topic A.
+            | Replace this with instructions for subagent A.
 
         actions:
             action_a: @actions.action_a
@@ -66,13 +66,13 @@ topic topic_a:
                     is_displayable: True
                     filter_from_agent: False
 
-topic topic_b:
-    label: "Topic B"
-    description: "Describe what this topic handles"
+subagent subagent_b:
+    label: "Subagent B"
+    description: "Describe what this subagent handles"
 
     reasoning:
         instructions: ->
-            | Replace this with instructions for topic B. This topic demonstrates the gating pattern.
+            | Replace this with instructions for subagent B. This subagent demonstrates the gating pattern.
 
         actions:
             # Collect data into a variable first
@@ -102,13 +102,13 @@ topic topic_b:
                     label: "Result"
                     is_displayable: False
 
-topic topic_c:
-    label: "Topic C"
-    description: "Describe what this topic handles"
+subagent subagent_c:
+    label: "Subagent C"
+    description: "Describe what this subagent handles"
 
     reasoning:
         instructions: ->
-            | Replace this with base instructions for topic C.
+            | Replace this with base instructions for subagent C.
 
             # Conditional instructions based on variable state
             if @variables.collected_input != "":
@@ -139,7 +139,7 @@ topic topic_c:
                     is_displayable: True
                     filter_from_agent: False
 
-topic escalation:
+subagent escalation:
     label: "Escalation"
     description: "Handles requests from users who want to transfer or escalate their conversation to a live human agent."
 
@@ -150,11 +150,11 @@ topic escalation:
             escalate_to_human: @utils.escalate
                 description: "Escalate to a human agent."
 
-topic off_topic:
+subagent off_topic:
     label: "Off Topic"
-    description: "Redirect conversation to relevant topics when user request goes off-topic"
+    description: "Redirect conversation to relevant subagents when user request goes off-topic"
 
     reasoning:
         instructions: ->
             | The user request is off-topic. Do not answer general knowledge questions.
-              Redirect the conversation by asking how you can help with topics this agent supports.
+              Redirect the conversation by asking how you can help with the subagents this agent supports.

package/skills/developing-agentforce/assets/{template-single-topic.agent → template-single-subagent.agent}

@@ -1,4 +1,4 @@
-# Single-Topic Agent Template
+# Single-Subagent Template
 # Copy this file to your AiAuthoringBundle directory and rename it to match
 # your agent's developer_name. Replace all placeholder values with real ones.
 
@@ -22,21 +22,21 @@ language:
     additional_locales: ""
     all_additional_locales: False
 
-start_agent topic_selector:
-    description: "Welcome the user and determine the appropriate topic based on user input"
+start_agent agent_router:
+    description: "Welcome the user and determine the appropriate subagent based on user input"
     reasoning:
         actions:
-            go_to_main: @utils.transition to @topic.main
-            go_to_escalation: @utils.transition to @topic.escalation
-            go_to_off_topic: @utils.transition to @topic.off_topic
+            go_to_main: @utils.transition to @subagent.main
+            go_to_escalation: @utils.transition to @subagent.escalation
+            go_to_off_topic: @utils.transition to @subagent.off_topic
 
-topic main:
-    label: "Main Topic"
-    description: "Describe what this topic handles. The Atlas Reasoning Engine matches user utterances against this description."
+subagent main:
+    label: "Main Subagent"
+    description: "Describe what this subagent handles. The Atlas Reasoning Engine matches user utterances against this description."
 
     reasoning:
         instructions: ->
-            | Replace this with instructions for how the agent should handle requests in this topic.
+            | Replace this with instructions for how the agent should handle requests in this subagent.
               Reference actions with the syntax shown below.
 
         actions:
@@ -60,7 +60,7 @@ topic main:
                     is_displayable: True
                     filter_from_agent: False
 
-topic escalation:
+subagent escalation:
     label: "Escalation"
     description: "Handles requests from users who want to transfer or escalate their conversation to a live human agent."
 
@@ -71,11 +71,11 @@ topic escalation:
             escalate_to_human: @utils.escalate
                 description: "Escalate to a human agent."
 
-topic off_topic:
+subagent off_topic:
     label: "Off Topic"
-    description: "Redirect conversation to relevant topics when user request goes off-topic"
+    description: "Redirect conversation to relevant subagents when user request goes off-topic"
 
     reasoning:
         instructions: ->
             | The user request is off-topic. Do not answer general knowledge questions.
-              Redirect the conversation by asking how you can help with topics this agent supports.
+              Redirect the conversation by asking how you can help with the subagents this agent supports.

package/skills/developing-agentforce/assets/verification-gate.agent

@@ -2,7 +2,7 @@
 # ========================================
 #
 # This template demonstrates the Verification Gate pattern where users
-# must pass through identity verification before accessing sensitive topics.
+# must pass through identity verification before accessing sensitive subagents.
 #
 # Pattern: Security gate before protected functionality
 # Use when: Handling sensitive data, payments, PII access
@@ -56,23 +56,23 @@ start_agent entry:
       instructions: |
          Welcome the customer and route to identity verification.
       actions:
-         start_verification: @utils.transition to @topic.identity_verification
+         start_verification: @utils.transition to @subagent.identity_verification
             description: "Begin identity verification process"
 
 # ============================================================
 # VERIFICATION GATE (Security Check)
 # ============================================================
 
-topic identity_verification:
+subagent identity_verification:
    description: "Verify customer identity before proceeding"
    reasoning:
       instructions: ->
          # SECURITY: Check for lockout FIRST (deterministic)
          if @variables.failed_attempts >= 3:
             | Too many failed attempts. Transferring to a human agent.
-            transition to @topic.escalation
+            transition to @subagent.escalation
 
-         # Already verified? Proceed to protected topics
+         # Already verified? Proceed to protected subagents
          if @variables.customer_verified == True:
             | Identity verified! How can I help you today?
 
@@ -88,11 +88,11 @@ topic identity_verification:
             set @variables.customer_verified = @outputs.verified
 
          # GUARDED: Only visible when verified
-         go_to_account: @utils.transition to @topic.account_management
+         go_to_account: @utils.transition to @subagent.account_management
             description: "Access account settings"
             available when @variables.customer_verified == True
 
-         go_to_refund: @utils.transition to @topic.refund_processor
+         go_to_refund: @utils.transition to @subagent.refund_processor
             description: "Process a refund request"
             available when @variables.customer_verified == True
 
@@ -104,13 +104,13 @@ topic identity_verification:
 # PROTECTED: Account Management
 # ============================================================
 
-topic account_management:
+subagent account_management:
    description: "Manage customer account (requires verification)"
    reasoning:
       instructions: ->
          # SECURITY GATE: Re-check verification
          if @variables.customer_verified == False:
-            transition to @topic.identity_verification
+            transition to @subagent.identity_verification
 
          | Welcome to account management.
          | What would you like to do with your account?
@@ -122,20 +122,20 @@ topic account_management:
          update_preferences: @actions.update_preferences
             description: "Update communication preferences"
             available when @variables.customer_verified == True
-         back: @utils.transition to @topic.identity_verification
+         back: @utils.transition to @subagent.identity_verification
             description: "Return to main menu"
 
 # ============================================================
 # PROTECTED: Refund Processor (with Post-Action Pattern)
 # ============================================================
 
-topic refund_processor:
+subagent refund_processor:
    description: "Process refund requests (requires verification)"
    reasoning:
       instructions: ->
          # SECURITY GATE: Re-check verification
          if @variables.customer_verified == False:
-            transition to @topic.identity_verification
+            transition to @subagent.identity_verification
 
          # ====================================================
          # POST-ACTION CHECK (at TOP - triggers on loop)
@@ -145,7 +145,7 @@ topic refund_processor:
             run @actions.create_crm_case
                with customer_id = @variables.customer_id
                with refund_amount = @variables.refund_amount
-            transition to @topic.success_confirmation
+            transition to @subagent.success_confirmation
 
          # ====================================================
          # PRE-LLM: Load churn risk data
@@ -181,14 +181,14 @@ topic refund_processor:
 # SUCCESS CONFIRMATION
 # ============================================================
 
-topic success_confirmation:
+subagent success_confirmation:
    description: "Confirm successful operation"
    reasoning:
       instructions: |
          Great news! Your request has been processed successfully.
          Is there anything else I can help you with?
       actions:
-         new_request: @utils.transition to @topic.identity_verification
+         new_request: @utils.transition to @subagent.identity_verification
             description: "Start a new request"
          end_conversation: @actions.end_session
             description: "End the conversation"
@@ -197,7 +197,7 @@ topic success_confirmation:
 # ESCALATION (Handoff to Human)
 # ============================================================
 
-topic escalation:
+subagent escalation:
    description: "Escalate to human agent"
    reasoning:
       instructions: |

package/skills/developing-agentforce/references/action-prompt-templates.md

@@ -50,7 +50,7 @@ actions:
 Reference the action definition in your `.agent` file:
 
 ```agentscript
-topic schedule_generation:
+subagent schedule_generation:
   reasoning:
     actions:
       generate_schedule: @actions.Generate_Personalized_Schedule

package/skills/developing-agentforce/references/actions-reference.md

@@ -146,7 +146,7 @@ Agent Script provides two ways to invoke actions:
 The LLM automatically selects appropriate actions from those defined in the `reasoning.actions` block:
 
 ```agentscript
-topic order_management:
+subagent order_management:
    description: "Handles order inquiries"
 
    reasoning:
@@ -355,7 +355,7 @@ public with sharing class CalculateDiscountAction {
 #### Step 2: Reference DIRECTLY in Agent Script via `apex://`
 
 ```yaml
-topic discount_calculator:
+subagent discount_calculator:
    description: "Calculates discount for customer order"
 
    # Level 1: Action DEFINITION with target
@@ -494,7 +494,7 @@ public class WrappedAction {
 
 The `connection` block enables escalation to human agents via Omni-Channel. Always use `connection messaging:` (singular).
 
-> **Service agents only.** The `connection messaging:` block and `@utils.escalate` are only valid for `AgentforceServiceAgent`. Employee agents (`AgentforceEmployeeAgent`) MUST NOT include a `connection` block or `@utils.escalate` actions — including them causes silent failures or "unknown error" at publish time. For employee agents, use `@utils.transition` to a help topic or an action that creates a support case instead.
+> **Service agents only.** The `connection messaging:` block and `@utils.escalate` are only valid for `AgentforceServiceAgent`. Employee agents (`AgentforceEmployeeAgent`) MUST NOT include a `connection` block or `@utils.escalate` actions — including them causes silent failures or "unknown error" at publish time. For employee agents, use `@utils.transition` to a help subagent or an action that creates a support case instead.
 
 ### Basic Syntax
 
@@ -588,7 +588,7 @@ When building agents with external API integrations, follow this order:
 
 | Issue | Cause | Solution |
 |-------|-------|----------|
-| `Tool target 'X' is not an action definition` | Action not defined in topic `actions:` block, or target doesn't exist in org | Define action with `target:` in topic-level `actions:` block; ensure Apex class/Flow is deployed |
+| `Tool target 'X' is not an action definition` | Action not defined in subagent `actions:` block, or target doesn't exist in org | Define action with `target:` in subagent-level `actions:` block; ensure Apex class/Flow is deployed |
 | `invalid input 'X'` or `invalid output 'X'` | I/O name doesn't match `@InvocableVariable` field name in Apex | Use exact field names from the Apex wrapper class (case-sensitive) |
 | `Internal Error` with inputs-only action | Action has `inputs:` but no `outputs:` block | Add `outputs:` block — the server-side compiler requires it (see known-issues.md Issue 15) |
 | `Internal Error` with bare @InvocableMethod | Apex uses `List<String>` without `@InvocableVariable` wrappers | Refactor Apex to use wrapper classes with `@InvocableVariable` annotations |