Test Batch (Import Provider): Difference between revisions
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
* Whole or portions of '''[[Batch Process]]es''' ( or '''[[Activity]]''' configurations more generally) | * Whole or portions of '''[[Batch Process]]es''' ( or '''[[Activity]]''' configurations more generally) | ||
They are not meant for full fledged, "real world" document processing. These '''Batches''' are not visible to "Production" level users, such as | They are not meant for full fledged, "real world" document processing. These '''Batches''' are not visible to "Production" level users, such as in the "Batches" or "Tasks" page. | ||
Revision as of 10:43, 22 November 2024
|
STUB |
This article is a stub. It contains minimal information on the topic and should be expanded. |
"Test Batch" is a specialized Import Provider designed to facilitate the import of content from an existing inventory_2 Batch in the test environment. This provider is most commonly used for testing, development, and validation scenarios, and is not intended for production use.
- Looking for information on "production" vs "test" Batches in Grooper? See here.
Test Batches are only visible to Grooper Design Studio users and are used to test anything configured in Grooper, such as:
- Document Classification
- OCR Profile configuration
- IP Profile configuration
- Data Extraction
- Whole or portions of Batch Processes ( or Activity configurations more generally)
They are not meant for full fledged, "real world" document processing. These Batches are not visible to "Production" level users, such as in the "Batches" or "Tasks" page.