Manifest Defining a Single Agent Version

This example package.xml manifest file defines the metadata for version two of the agent NGA_Service_Agent. The file also defines the agent’s flows, prompt templates, and Apex classes.

Before deploying a single agent version into an org, you must have deployed the full agent to the org. Deploying the agent before deploying an agent version ensures all required metadata and artifacts are created in the target org.

Note

1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3 <!-- Use BotVersion instead of Bot to get a specific version of an agent -->
4    <types>
5        <members>NGA_Service_Agent.v2</members>
6        <name>BotVersion</name>
7    </types>
8    <types>
9        <members>NGA_Service_Agent_v2</members>
10        <name>GenAiPlannerBundle</name>
11    </types>
12    <types>
13        <members>NGA_Service_Agent_2</members>
14        <name>AiAuthoringBundle</name>
15    </types>
16
17    <types>
18        <members>*</members>
19        <name>GenAiPlugin</name>
20    </types>
21    <types>
22        <members>*</members>
23        <name>GenAiFunction</name>
24    </types>
25
26    <types>
27        <members>CaseEmail</members>
28        <name>ApexClass</name>
29    </types>
30
31    <types>
32        <members>Field_Generation_Flow</members>
33        <members>Sales_Email_Flow</members>
34        <name>Flow</name>
35    </types>
36    <!-- The version of metadata to extract -->
37    <version>66.0</version>
38</Package>