Batch Object - Copy To Test Batch

Copies selected items to a test batch, optionally flagging them for review or testing.

Remarks

The Copy To Test Batch command duplicates the selected Batch Objects and appends them to the specified test batch. This command is ideal for scenarios where you need to create test cases, reproduce issues, or validate solution changes without affecting production data.

Use this command to:

• Create copies of documents, folders, or pages for regression testing, QA, or solution development.
• Reproduce real-world issues in a controlled test environment for troubleshooting or support.
• Validate extraction, classification, or export changes using actual production data, while preserving the original items in their source batch.

When executed, the selected items are cloned and added to the target test batch, maintaining their structure, metadata, and content. Optionally, you can set the 'Flag Reason' property to annotate the copied items in the test batch, providing context for testers or reviewers.

> Note: This command is enabled when one or more items are selected and a valid target batch is specified. > The original items remain unchanged in their source batch.

Properties

Name	Type		Description
Target Batch	Batch	►	The test batch to which items will be sent. EditorTest Batch Editor Requiredtrue The Target Batch property specifies the destination test batch for the selected items. You must select a valid batch to enable the command. Choose a batch that is configured for testing, validation, or review. This property is required; the command cannot be executed without a target batch. Selecting the correct batch ensures that items are routed to the appropriate environment for further processing or analysis.
Flag Reason	String	►	The reason to assign when flagging items in the target batch. ConverterFlag Reason Converter The Flag Reason property allows you to annotate copied or moved items in the target batch with a message describing why they require review or special handling. Optionally specify a flag reason to help reviewers or testers understand the context or issue. The list of available reasons is determined by the current Task View and may include standard or custom messages. If left blank, no flag will be applied to the items in the target batch. Example flag reasons might include: For regression testing, Suspected data issue, or Requires manual review.

See Also

BatchBatch FolderBatch Page