fix: edit messages for agent create and agent generte spec #41
Conversation
jshackell-sfdc
requested review from
shetzel and
WillieRuemmele
and removed request for
a team
|
|
||
| # flags.name.summary | ||
|
|
||
| The name of the agent. | ||
| API name of the new agent. |
There was a problem hiding this comment.
I believe this is actually the label, not the API name (aka developer name).
There was a problem hiding this comment.
@WillieRuemmele said it was the API name. I originally thought it was the label.
| @@ -1,25 +1,25 @@ | |||
| # summary | |||
|
|
|||
| Create an Agent from an agent spec. | |||
| Create an agent in your org from a local agent spec file. | |||
There was a problem hiding this comment.
This is going to change with the v2 agent creator APIs that will allow "agent preview" behavior, meaning the metadata will not be created in the org but sent back in the response to be previewed by the customer.
There was a problem hiding this comment.
Gotcha. I was writing this with the Dec milestone in mind, so I will change it when you implement v2. Okay?
|
|
||
| # flags.job-spec.summary | ||
| When this command finishes, your org contains the new agent, which you can then edit in the Agent Builder UI. The new agent already has a list of topics and actions that were automatically created from the list of jobs in the provided agent spec file. This command also retrieves all the metadata files associated with the new agent to your local DX project. |
There was a problem hiding this comment.
This is true with the current implementation but not necessarily with the v2 implementation.
There was a problem hiding this comment.
see my previous comment.
|
|
||
| # description | ||
|
|
||
| Create an Agent spec, which is a list of job titles and descriptions that the agent performs. | ||
| When using Salesforce CLI to create an agent in your org, the first step is to generate the local JSON-formatted agent spec file with this command. |
There was a problem hiding this comment.
This is true for the existing commands but not necessarily true with v2. The v2 APIs allow agent creation from the fields used to generate a spec and not only from a spec.
There was a problem hiding this comment.
see my previous comment.
|
I'll update the --help after you implement v2. I was writing this for the Dec milestone, in case Vivek wants to run --help on the commands in his demo. :) |
What does this PR do?
Edits and adds a bit more info to the --help of "agent generate spec" and "agent create"
What issues does this PR fix or reference?
@W-17417430@