Grooper Service (Concept)

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 account must have the following permissions: File store access Type: NTFS\Share Reason: Read and write access to the Grooper file store location Database access Type: SQL Reason: Read and write access to the Grooper database Logon As Service Type: Local Security Policy Reason: Run services installed via Grooper Command Console

See Also

• Activity Processing
• Grooper Licensing
• Import Watcher

Addressing "ghost services" - Deleting services from Windows

⚠

Very rarely, a Grooper service will not uninstall properly when you uninstall a Grooper service service. Or, a user may delete a Grooper Repository connection or purge a Grooper Repository without uninstalling services first. This can make it appear as though a duplicate or "ghost" Windows service is installed without being listed in GCC (or Grooper Config before version 2024). If this does occur, you will need to manually delete the service. If you know the name of the service instance (something like Grooper.ServiceTypeName.##) you need to delete, you can use the following command lines to stop the service (if necessary) and manually delete it. SC STOP Grooper.ServiceTypeName.## SC DELETE Grooper.ServiceTypeName.## OR You can delete the service from the Windows Registry Editor, using the following steps: Open the Registry Editor (regedit.exe) Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. Select the key of the service you want to delete. Grooper services will always be named something like Grooper.ServiceTypeName.## From the "Edit" menu select "Delete. You will be prompted "Are you sure you want to delete this Key?". Click Yes. Exit the Registry Editor.

Glossary

Activity Processing: Activity Processing is the execution of a sequence of configured tasks which are performed within a settings Batch Process to transform raw data from documents into structured and actionable information. Tasks are defined by Grooper Activities, configurated to perform document classification, extraction, or data enhancement.

Activity Processing: Activity Processing is a Grooper Service that executes Activities assigned to edit_document Batch Process Steps in a settings Batch Process. This allows Grooper to automate Batch Steps that do not require a human operator.

Activity: Activity is a property on edit_document Batch Process Steps. Activities define specific document processing operations done to a inventory_2 Batch, folder Batch Folder, or contract Batch Page. Batch Process Steps configured with specific Activities are frequently referred by the name of the Activity followed by the word "step". For example: Classify step.

Batch: inventory_2 Batch objects are fundamental in Grooper's architecture as they are the containers of documents that get moved through Grooper's workflow mechanisms known as settings Batch Processes.

Grooper Licensing: Grooper Licensing is a Grooper Service that distributes licenses to multiple workstations running Grooper applications.

Grooper Service: 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).

Service: Grooper Service is a conceptual term that refers to the various executable programs that run as a Windows Services to facilitate Grooper processing. Service instances are installed, started and stopped using Grooper Command Console.