Grooper Service (Concept): Difference between revisions
Dgreenwood (talk | contribs) No edit summary |
Dgreenwood (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
<onlyinclude> | <onlyinclude> | ||
<blockquote style="font-size:14pt"> | <blockquote style="font-size:14pt"> | ||
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 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> | ||
| Line 8: | Line 8: | ||
Grooper Config must be ran as an administrator to install and configure Grooper Services. | Grooper Config must be ran as an administrator to install and configure Grooper Services. | ||
</onlyinclude> | </onlyinclude> | ||
=== See Also === | |||
* '''[[Activity Processing]]''' | |||
* '''[[Grooper Licensing]]''' | |||
* '''[[Import Watcher]]''' | |||
Revision as of 09:42, 6 October 2021
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.