Grooper Service (Concept): Difference between revisions
m Randallkinard moved page Grooper Service to Grooper Service (Concept): new naming convention |
No edit summary |
||
| Line 1: | Line 1: | ||
{{stubs}} | {{stubs}} | ||
<blockquote> | <blockquote>{{#lst:Glossary|Grooper Service}}</blockquote> | ||
Grooper | |||
</blockquote> | |||
For example, '''Import Watcher''' is a service that watches an assigned external storage location, like a Windows folder or an email inbox, and will automatically import its contents into Grooper for automated '''[[Batch]]''' creation. | For example, '''Import Watcher''' is a service that watches an assigned external storage location, like a Windows folder or an email inbox, and will automatically import its contents into Grooper for automated '''[[Batch]]''' creation. | ||
Revision as of 14:29, 23 April 2024
|
STUB |
This article is a stub. It contains minimal information on the topic and should be expanded. |
Grooper Services are various executable programs that run as a Windows Services to facilitate Grooper processing. Service instances are installed, configured, started and stopped using Grooper Command Console (Or in older Grooper versions, Grooper Config).
For example, Import Watcher is a service that watches an assigned external storage location, like a Windows folder or an email inbox, and will automatically import its contents into Grooper for automated Batch creation.
Grooper Config must be ran as an administrator to install and configure Grooper Services.
| ⚠ |
The Grooper Service User must have the "Log on as Service" permission. |