Test Batch (Import Provider): Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
| Line 7: | Line 7: | ||
* Document [[Classification]] | * Document [[Classification]] | ||
* [[Data Extraction]] | * '''[[OCR Profile]]''' configuration | ||
* '''[[IP Profile]]''' configuration | |||
* [[Data Extractors|Data Extraction]] | |||
* 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 [[Grooper Dashboard]] workstations. | They are not meant for full fledged, "real world" document processing. These '''Batches''' are not visible to "Production" level users, such as [[Grooper Dashboard]] workstations. | ||
</onlyinclude> | </onlyinclude> | ||
Revision as of 10:14, 25 November 2020
A Test Batch is any Batch created in the "Test" environment (in the Test folder of the Batches folder in the Node Tree).
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 Grooper Dashboard workstations.