Grooper Service (Concept): Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{stubs}} | {{stubs}} | ||
< | <section begin="grooper_service_glossary" /> | ||
<blockquote> | |||
Grooper Services are various executable applications that run as a Windows Service to aid Grooper. Service Instances are installed, configured, started and stopped using [[Grooper Config]]. | Grooper Services are various executable applications that run as a Windows Service to aid Grooper. Service Instances are installed, configured, started and stopped using [[Grooper Config]]. | ||
</blockquote> | </blockquote> | ||
<section end="grooper_service_glossary" /> | |||
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 17:42, 5 January 2024
|
STUB |
This article is a stub. It contains minimal information on the topic and should be expanded. |
Grooper Services are various executable applications that run as a Windows Service to aid Grooper. Service Instances are installed, configured, started and stopped using 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.