You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: messages/agent.activate.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,23 +4,29 @@ Activate an agent in an org.
4
4
5
5
# description
6
6
7
-
Activating an agent makes it immediately available to your users. An agent must be active before you can preview it with the "agent preview" CLI command or VS Code.
7
+
Activating an agent makes it immediately available to your users. A published agent must be active before you can preview it with the "agent preview" CLI command or VS Code. Agents can have multiple versions; only one version can be active at a time.
8
8
9
-
You must know the agent's API name to activate it; you can either be prompted for it or you can specify it with the --api-name flag. Find the agent's API name in its Agent Details page of your org's Agentforce Studio UI in Setup.
9
+
If you run the command without the --api-name or --version flags, the command provides a list of agent API names and versions for you to choose from. Use the flags to specify the exact agent and version without being prompted. If you use the --json flag and not --version, then the latest agent version is automatically activated.
10
+
11
+
The value of the --version flag is always a number, corresponding to the "vX" part of the "BotVersion" metadata in your project. For example, if you have a force-app/main/default/bots/My_Agent/v4.botVersion-meta.xml file in your project, then you activate this version with the "--version 4" flag.
10
12
11
13
# examples
12
14
13
-
- Activate an agent in your default target org by being prompted:
15
+
- Activate an agent in your default target org by being prompted for both its API name and version:
14
16
15
17
<%= config.bin %> <%= command.id %>
16
18
17
-
- Activate an agent with API name Resort_Manager in the org with alias "my-org":
19
+
- Activate version 2 of an agent with API name Resort_Manager in the org with alias "my-org":
Copy file name to clipboardExpand all lines: messages/agent.deactivate.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Deactivate an agent in an org.
6
6
7
7
Deactivating an agent makes it unavailable to your users. To make changes to an agent, such as adding or removing topics or actions, you must deactivate it. You can't preview an agent with the "agent preview" CLI command or VS Code if it's deactivated.
8
8
9
-
You must know the agent's API name to deactivate it; you can either be prompted for it or you can specify it with the --api-name flag. Find the agent's API name in its Agent Details page of your org's Agentforce Studio UI in Setup.
9
+
If you run the command without the --api-name flag, the command provides a list of agent API names for you to choose from. Use the flag to specify the exact agent without being prompted.
10
10
11
11
# examples
12
12
@@ -20,7 +20,7 @@ You must know the agent's API name to deactivate it; you can either be prompted
20
20
21
21
# flags.api-name.summary
22
22
23
-
API name of the agent to deactivate.
23
+
API name of the agent to deactivate; if not specified, the command provides a list that you choose from.
0 commit comments