@salesforce/plugin-agent 1.40.5 → 1.42.0

package/messages/agent.adl.update.md

@@ -0,0 +1,49 @@
+# summary
+
+Update an Agentforce Data Library.
+
+# description
+
+Updates the label, description, or other mutable properties of an existing data library.
+
+# examples
+
+- Update the label of a data library:
+
+  <%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --name "New Name" --target-org myOrg
+
+- Update the description:
+
+  <%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --description "Updated description" --target-org myOrg
+
+- Update Knowledge library content fields (triggers re-indexing):
+
+  <%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --content-fields "Answer**c,Summary**c" --target-org myOrg
+
+- Restrict Knowledge library to public articles:
+
+  <%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --restrict-to-public-articles --target-org myOrg
+
+# flags.library-id.summary
+
+Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).
+
+# flags.name.summary
+
+New display name for the data library (max 80 characters).
+
+# flags.description.summary
+
+New description for the data library (max 255 characters).
+
+# flags.content-fields.summary
+
+Comma-separated list of content fields for KNOWLEDGE libraries (triggers re-indexing).
+
+# flags.restrict-to-public-articles.summary
+
+Restrict to public Knowledge articles only (KNOWLEDGE libraries, triggers re-indexing).
+
+# error.updateFailed
+
+Failed to update data library: %s

package/messages/agent.adl.upload.md

@@ -0,0 +1,55 @@
+# summary
+
+Upload a file to an SFDRIVE Agentforce Data Library.
+
+# description
+
+Performs the multi-step upload workflow: checks upload readiness, obtains a pre-signed S3 URL, uploads the file, triggers indexing, and optionally polls until the library is ready (retrieverId is populated).
+
+This command only works with SFDRIVE libraries. KNOWLEDGE libraries index automatically after creation, and RETRIEVER libraries require no file upload.
+
+# examples
+
+- Upload a file and wait for indexing to complete:
+
+  <%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --file ./docs/guide.pdf --target-org myOrg --wait 10
+
+- Upload a file without waiting:
+
+  <%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --file ./docs/guide.pdf --target-org myOrg
+
+# flags.library-id.summary
+
+Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).
+
+# flags.file.summary
+
+Path to the file to upload.
+
+# flags.wait.summary
+
+Number of minutes to wait for indexing to complete. If not specified, returns after triggering indexing.
+
+# error.uploadReadiness
+
+Library is not ready for upload: %s
+
+# error.getUploadUrl
+
+Failed to get upload URL: %s
+
+# error.s3Upload
+
+Failed to upload file to storage: %s
+
+# error.indexing
+
+Failed to trigger indexing: %s
+
+# error.polling
+
+Failed to poll library status: %s
+
+# error.timeout
+
+Indexing did not complete within the specified wait time. Use "sf agent adl get --library-id %s" to check status.

package/messages/agent.test.create.md

@@ -6,7 +6,7 @@ Create an agent test in your org using a local test spec YAML file.
 
 To run this command, you must have an agent test spec file, which is a YAML file that lists the test cases for testing a specific agent. Use the "agent generate test-spec" CLI command to generate a test spec file. Then specify the file to this command with the --spec flag, or run this command with no flags to be prompted.
 
-When this command completes, your org contains the new agent test, which you can view and edit using the Testing Center UI. This command also retrieves the metadata component (AiEvaluationDefinition) associated with the new test to your local Salesforce DX project and displays its filename.
+When this command completes, your org contains the new agent test, which you can view and edit using the Testing Center UI (legacy) or Agentforce Studio (NGT). This command also retrieves the metadata component associated with the new test to your local Salesforce DX project and displays its filename. By default, the legacy AiEvaluationDefinition is created; use --test-runner agentforce-studio to author an AiTestingDefinition (NGT) instead.
 
 After you've created the test in the org, use the "agent test run" command to run it.
 
@@ -16,7 +16,7 @@ Path to the test spec YAML file.
 
 # flags.preview.summary
 
-Preview the test metadata file (AiEvaluationDefinition) without deploying to your org.
+Preview the test metadata file without deploying to your org.
 
 # flags.force-overwrite.summary
 
@@ -40,13 +40,17 @@ API name of the new test; the API name must not exist in the org.
 
   <%= config.bin %> <%= command.id %> --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test --preview
 
+- Author an Agentforce Studio (NGT) test from an NGT-shaped YAML; writes an AiTestingDefinition metadata file:
+
+  <%= config.bin %> <%= command.id %> --spec specs/ReturnsCheckout.ngt.yaml --api-name Returns_Checkout --test-runner agentforce-studio --target-org my-org
+
 # prompt.confirm
 
 A test with the API name %s already exists in the org. Do you want to overwrite it?
 
 # info.success
 
-Local AiEvaluationDefinition metadata XML file created at %s and agent test deployed to %s.
+Local test metadata XML file created at %s and agent test deployed to %s.
 
 # info.preview-success