What's New in Grooper 2026 - Revision history

Dgreenwood: /* GWS URL format change (action required) */

2026-11-02T14:04:13Z

GWS URL format change (action required)

← Older revision		Revision as of 08:04, 2 November 2026
Line 285:		Line 285:
	=== GWS URL format change (action required) ===		=== GWS URL format change (action required) ===

	*<li class="attn-bullet"> '''Action required~~'''~~ if you use GWS, Grooper's REST API. Otherwise, no action is needed.		*<li class="attn-bullet"> '''Action required if you use GWS, Grooper's REST API.''' Otherwise, no action is needed.

2026-11-02T14:03:54Z

AppXtender and FileBound connections moved to Object Libraries (action required)

← Older revision		Revision as of 08:03, 2 November 2026
Line 249:		Line 249:
	=== AppXtender and FileBound connections moved to Object Libraries (action required) ===		=== AppXtender and FileBound connections moved to Object Libraries (action required) ===

	*<li class="attn-bullet"> '''Action required~~'''~~ if you use AppXtender or FileBound CMIS Connections. Otherwise, no action is needed.		*<li class="attn-bullet"> '''Action required if you use AppXtender or FileBound CMIS Connections.''' Otherwise, no action is needed.

2026-11-02T14:03:28Z

Settings moved from web.config to appsettings.json (action required)

← Older revision		Revision as of 08:03, 2 November 2026
Line 103:		Line 103:
	=== Settings moved from web.config to appsettings.json (action required) ===		=== Settings moved from web.config to appsettings.json (action required) ===

	*<li class="attn-bullet"> '''Action required~~'''~~ if you configured Entra ID, Content Security Policy, or cookie settings in <code>web.config</code>.''' These values are not migrated on upgrade and must be re-entered in <code>appsettings.json</code>. Otherwise, no action is needed.		*<li class="attn-bullet"> '''Action required if you configured Entra ID, Content Security Policy, or cookie settings in <code>web.config</code>.''' These values are not migrated on upgrade and must be re-entered in <code>appsettings.json</code>. Otherwise, no action is needed.

	Both the Grooper and GWS sites now have an <code>appsettings.json</code> file for application-level configuration.		Both the Grooper and GWS sites now have an <code>appsettings.json</code> file for application-level configuration.

2026-11-02T14:03:00Z

Settings moved from web.config to appsettings.json (action required)

← Older revision		Revision as of 08:03, 2 November 2026
Line 103:		Line 103:
	=== Settings moved from web.config to appsettings.json (action required) ===		=== Settings moved from web.config to appsettings.json (action required) ===

	*<li class="attn-bullet"> '''Action required if you configured Entra ID, Content Security Policy, or cookie settings in <code>web.config</code>.''' These values are not migrated on upgrade and must be re-entered in <code>appsettings.json</code>. Otherwise, no action is needed.		*<li class="attn-bullet"> '''Action required''' if you configured Entra ID, Content Security Policy, or cookie settings in <code>web.config</code>.''' These values are not migrated on upgrade and must be re-entered in <code>appsettings.json</code>. Otherwise, no action is needed.

	Both the Grooper and GWS sites now have an <code>appsettings.json</code> file for application-level configuration.		Both the Grooper and GWS sites now have an <code>appsettings.json</code> file for application-level configuration.

2026-10-30T15:48:36Z

Settings moved from web.config to appsettings.json (action required)

← Older revision		Revision as of 09:48, 30 October 2026
Line 114:		Line 114:
	This had one major downside. Every time the application was uninstalled and reinstalled, <code>web.config</code> was replaced with the default file. This wiped out any configuration and required users to re-enter the values.		This had one major downside. Every time the application was uninstalled and reinstalled, <code>web.config</code> was replaced with the default file. This wiped out any configuration and required users to re-enter the values.

	~~Storing these settings~~ in <code>appsettings.json</code> ~~removes this limitation. This~~ file is not removed or overwritten when the application is uninstalled ~~or upgraded~~.		Grooper 2026 removes this limitation in two ways:
			# The 2026 Grooper installer can now perform an upgrade without requiring the user to uninstall Grooper first.
			# The <code>appsettings.json</code> file is not removed or overwritten when the application is '''upgraded'''.
			#*<li class="attn-bullet"> Be aware, the <code>appsettings.json</code> file is still removed when Grooper is uninstalled.

	'''File locations'''		'''File locations'''

2026-10-30T13:18:44Z

Upgrade Notes for 2026

2026-10-29T19:17:42Z

AppXtender and FileBound connections moved to Object Libraries (action required)

← Older revision		Revision as of 13:17, 29 October 2026
Line 104:		Line 104:

	*<li class="attn-bullet"> '''Action required''' if you use AppXtender or FileBound CMIS Connections. Otherwise, no action is needed.		*<li class="attn-bullet"> '''Action required''' if you use AppXtender or FileBound CMIS Connections. Otherwise, no action is needed.


	We have removed the following CMIS Bindings from the core Grooper application.		We have removed the following CMIS Bindings from the core Grooper application.

2026-10-29T19:17:29Z

GWS URL format change (action required)

← Older revision		Revision as of 13:17, 29 October 2026
Line 139:		Line 139:

	*<li class="attn-bullet"> '''Action required''' if you use GWS, Grooper's REST API. Otherwise, no action is needed.		*<li class="attn-bullet"> '''Action required''' if you use GWS, Grooper's REST API. Otherwise, no action is needed.


	The GWS API URL format has changed. Previously, the Grooper Repository ID was a required query string parameter at the end of the URL. Now it is a required part of the URL path. All GWS endpoints use the following format:		The GWS API URL format has changed. Previously, the Grooper Repository ID was a required query string parameter at the end of the URL. Now it is a required part of the URL path. All GWS endpoints use the following format:

2026-10-29T19:17:19Z

GWS URL format change (action required)

← Older revision		Revision as of 13:17, 29 October 2026
Line 144:		Line 144:
	<pre>https://{hostname}/GWS/{repositoryId}/{endpoint}</pre>		<pre>https://{hostname}/GWS/{repositoryId}/{endpoint}</pre>

	~~'''~~Example~~'''~~		<big>Example</big>

	The <code>GET batches</code> endpoint returns a list of Batches in the Grooper Repository.		The <code>GET batches</code> endpoint returns a list of Batches in the Grooper Repository.

2026-10-29T19:17:02Z

GWS URL format change (action required)

← Older revision		Revision as of 13:17, 29 October 2026
Line 137:		Line 137:

	=== GWS URL format change (action required) ===		=== GWS URL format change (action required) ===

			*<li class="attn-bullet"> '''Action required''' if you use GWS, Grooper's REST API. Otherwise, no action is needed.

	The GWS API URL format has changed. Previously, the Grooper Repository ID was a required query string parameter at the end of the URL. Now it is a required part of the URL path. All GWS endpoints use the following format:		The GWS API URL format has changed. Previously, the Grooper Repository ID was a required query string parameter at the end of the URL. Now it is a required part of the URL path. All GWS endpoints use the following format: