2.72:Grooper Config (Application): Difference between revisions

From Grooper Wiki
m Randallkinard moved page 2.72:Grooper Config to 2.72:Grooper Config (Application) without leaving a redirect: new naming convention
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
__NOINDEX__
{{AutoVersion}}
{{AutoVersion}}
{{stubs}}
{|class="important-box"
|
'''!!'''
|
'''LEGACY TECHNOLOGY DETECTED!!'''
 
With the advent of the Grooper web client, the Grooper Config application is going away.  Its analog in the web client is the "[[Grooper Command Console]]" application. 
|}
 
<blockquote style="font-size:14pt">
<blockquote style="font-size:14pt">
Grooper Config is part of the Grooper Product Suite.  This program is used to configure settings specific to a server or workstation (whereas Grooper Design Studio is used to architect objects such as Content Models and Batch Processes used by ''all'' servers and workstations).
Grooper Config is part of the Grooper Product Suite.  This program is used to configure settings specific to a server or workstation (whereas Grooper Design Studio is used to architect objects such as Content Models and Batch Processes used by ''all'' servers and workstations).

Latest revision as of 12:09, 5 February 2026


This article is about an older version of Grooper.

Information may be out of date and UI elements may have changed.

2025202320212.72

!!

LEGACY TECHNOLOGY DETECTED!!

With the advent of the Grooper web client, the Grooper Config application is going away. Its analog in the web client is the "Grooper Command Console" application.

Grooper Config is part of the Grooper Product Suite. This program is used to configure settings specific to a server or workstation (whereas Grooper Design Studio is used to architect objects such as Content Models and Batch Processes used by all servers and workstations).

Grooper Config has two main purposes: