2021:Upgrading Grooper to a New Version - Revision history

Dgreenwood at 16:12, 5 August 2025

2025-08-05T16:12:53Z

← Older revision		Revision as of 11:12, 5 August 2025
Line 1:		Line 1:
			__NOINDEX__
	{{AutoVersion}}		{{AutoVersion}}
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">

Randallkinard: Randallkinard moved page 2021:Upgrading Grooper to a New Version (Concept) to 2021:Upgrading Grooper to a New Version without leaving a redirect: undo naming

2024-04-18T19:24:48Z

Randallkinard moved page 2021:Upgrading Grooper to a New Version (Concept) to 2021:Upgrading Grooper to a New Version without leaving a redirect: undo naming

← Older revision	Revision as of 14:24, 18 April 2024
(No difference)

Randallkinard: Randallkinard moved page 2021:Upgrading Grooper to a New Version to 2021:Upgrading Grooper to a New Version (Concept) without leaving a redirect: new naming convention

2024-04-18T17:54:17Z

Randallkinard moved page 2021:Upgrading Grooper to a New Version to 2021:Upgrading Grooper to a New Version (Concept) without leaving a redirect: new naming convention

← Older revision	Revision as of 12:54, 18 April 2024
(No difference)

Dgreenwood at 13:42, 12 January 2024

2024-01-12T13:42:43Z

← Older revision		Revision as of 08:42, 12 January 2024
Line 14:		Line 14:
	# Upgrade Grooper Repositories from the older version to 2021.		# Upgrade Grooper Repositories from the older version to 2021.

	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px; width: 100%~~"		{\|class="attn-box"
	\|-		\|
	~~\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|~~⚠		⚠
	~~\|style="border: 4px solid #f89420"~~\|		\|
	This article instructs users on how to perform simple upgrades. The instructions in this article outline the basic steps for all upgrades.		This article instructs users on how to perform simple upgrades. The instructions in this article outline the basic steps for all upgrades.

Line 78:		Line 78:
	\|}		\|}

	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px~~"		{\|class="attn-box"
	\|-		\|
	~~\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|~~⚠		⚠
	~~\|style="border: 4px solid #f89420"~~\|		\|
	You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.		You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.

Line 128:		Line 128:
	=== Step 0: Back up your Database and File Store ===		=== Step 0: Back up your Database and File Store ===

	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px~~"		{\|class="attn-box"
	\|-		\|
	~~\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|~~⚠		⚠
	~~\|style="border: 4px solid #f89420"~~\|		\|
	You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.		You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.

Line 237:		Line 237:
	# Don't forget to press the "Save" button in the main screen of Grooper Config.		# Don't forget to press the "Save" button in the main screen of Grooper Config.

	{\|~~cellpadding~~="~~10" cellspacing="5" style="margin:12px~~"		{\|class="attn-box"
	\|-		\|
	~~\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|~~⚠		⚠
	~~\|style="border: 4px solid #f89420"~~\|		\|
	'''IMPORTANT''' - If present, make sure you compile all '''Object Libraries''' after the upgrade.		'''IMPORTANT''' - If present, make sure you compile all '''Object Libraries''' after the upgrade.

Dgreenwood: Dgreenwood moved page Upgrading Grooper to a New Version - 2021 to 2021:Upgrading Grooper to a New Version without leaving a redirect

2024-01-02T19:14:46Z

Dgreenwood moved page Upgrading Grooper to a New Version - 2021 to 2021:Upgrading Grooper to a New Version without leaving a redirect

← Older revision	Revision as of 14:14, 2 January 2024
(No difference)

Dgreenwood at 19:12, 2 January 2024

2024-01-02T19:12:38Z

← Older revision		Revision as of 14:12, 2 January 2024
Line 1:		Line 1:
			{{AutoVersion}}
	<blockquote style="font-size:14pt">		<blockquote style="font-size:14pt">
	So you're ready to upgrade?		So you're ready to upgrade?
Line 251:		Line 252:
	</tab>		</tab>
	</tabs>		</tabs>

	~~[[Category:Articles]]~~
	~~[[Category:Version 2021]]~~

Dgreenwood at 19:34, 12 December 2022

2022-12-12T19:34:36Z

← Older revision		Revision as of 14:34, 12 December 2022
Line 251:		Line 251:
	</tab>		</tab>
	</tabs>		</tabs>

			[[Category:Articles]]
			[[Category:Version 2021]]

Dgreenwood at 19:09, 8 December 2022

2022-12-08T19:09:30Z

← Older revision		Revision as of 14:09, 8 December 2022
Line 13:		Line 13:
	# Upgrade Grooper Repositories from the older version to 2021.		# Upgrade Grooper Repositories from the older version to 2021.

	~~Depending~~ on your Grooper install, your upgrade process may be ~~slightly~~ more involved. If you are running scripts in your environment to customize Grooper's functionality, you may need to update the associated '''Object Libraries''' code. ~~However~~, ~~these three basic steps will apply~~ to all ~~upgrades~~.		{\|cellpadding="10" cellspacing="5" style="margin:12px; width: 100%"
			\|-
			\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|⚠
			\|style="border: 4px solid #f89420"\|
			This article instructs users on how to perform simple upgrades. The instructions in this article outline the basic steps for all upgrades.


			However, depending on your Grooper install, your upgrade process may be more involved.
			* If you are running scripts in your environment to customize Grooper's functionality, you may need to update the associated scripting code and '''Object Libraries''', as some code objects may have been altered or obsoleted or their names may have changed.
			** If present, make sure you re-compile all '''Object Libraries''' after the upgrade.
			** Custom scripts are not guaranteed to work without changes upon upgrading to a new major version of Grooper.
			* If you are running custom reports polling the Grooper database, you may need to update the report query, as Grooper's database tables may have changed.
			* If you are using expressions in your '''Batch Processes''', '''IP Profiles''', '''Data Models''' or '''Import/Export Mappings''', please verify all expressions are working as intended as some as some code objects may have been altered or obsoleted or their names may have changed.
			* If you are moving across multiple major versions, it's likely Grooper's architecture has changed more than if upgrading from one major version to the next. Your solution design may not be taking advantage of newly added features in newer versions.
			** In all cases, you should take some time to test your Grooper system after an upgrade to ensure everything is working as expected. When upgrading across multiple major versions, please take extra care to do so.

			\|}

	== How To ==		== How To ==
Line 19:		Line 35:
	=== Perform a Simple Upgrade ===		=== Perform a Simple Upgrade ===

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5" style="margin:12px; width: 100%"
	\|-style="background-color:#~~f89420~~; color:white"		\|-
	\|style="~~font-size~~:~~22pt~~"\|~~⚠\|\|~~You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.		\|style="font-size:250%; background-color:#662d91; color:white; width:28px; text-align:center"\|'''‼'''
			\|style="border: 4px solid #662d91"\|
			'''IMPORTANT!!'''

			You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.

	If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could loose critical components, such as your '''Batch Processes''', '''Content Models''', or document files for any '''Test''' or '''Production Batches'''.		If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could loose critical components, such as your '''Batch Processes''', '''Content Models''', or document files for any '''Test''' or '''Production Batches'''.
Line 29:		Line 49:
	For information how to backup and restore your Grooper database and filestore, [[Backup and Restore Grooper Repository\|please visit this article]].		For information how to backup and restore your Grooper database and filestore, [[Backup and Restore Grooper Repository\|please visit this article]].
	\|}		\|}
			{\|cellpadding="10" cellspacing="5" style="margin:12px; width: 100%"
	{\|cellpadding="10" cellspacing="5"		\|-
	\|-style="background-color:#36b0a7; color:white"		\|style="font-size:125%; background-color:#36b0a7; color:white; width:28px; text-align:center"\|'''FYI'''
	~~\|style="font~~-~~size~~:~~14pt~~"\|'''FYI'''\|\|If you are upgrading from version 2.72, 2.80 or 2.90 to 2021, you may upgrade directly to version 2021. However, if you are upgrading from version 2.70 (or older) to 2021, you must first upgrade to version 2.72, and then upgrade to version 2021.		\|style="border: 4px solid #36b0a7"\|
			If you are upgrading from version 2.72, 2.80 or 2.90 to 2021, you may upgrade directly to version 2021. However, if you are upgrading from version 2.70 (or older) to 2021, you must first upgrade to version 2.72, and then upgrade to version 2021.
	\|}		\|}

Line 56:		Line 77:
	\|}		\|}

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5" style="margin:12px"
	\|-style="background-color:#f89420; color:white"		\|-
	~~\|style="font~~-~~size~~:~~22pt~~"\|⚠\|\|You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.		\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|⚠
			\|style="border: 4px solid #f89420"\|
			You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.

	If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could loose critical components, such as your '''Batch Processes''', '''Content Models''', or document files for any '''Test''' or '''Production Batches'''.		If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could loose critical components, such as your '''Batch Processes''', '''Content Models''', or document files for any '''Test''' or '''Production Batches'''.
Line 104:		Line 127:
	=== Step 0: Back up your Database and File Store ===		=== Step 0: Back up your Database and File Store ===

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5" style="margin:12px"
	\|-style="background-color:#f89420; color:white"		\|-
	~~\|style="font~~-~~size~~:~~22pt~~"\|⚠\|\|You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.		\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|⚠
			\|style="border: 4px solid #f89420"\|
			You should always perform a complete backup of your Grooper Repository's file store and database before upgrading to any newer Grooper version.

	If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could loose critical components, such as your '''Batch Processes''', '''Content Models''', or document files for any '''Test''' or '''Production Batches'''.		If, for whatever reason, something goes wrong during the upgrade process and your file store and/or database is corrupted, you could loose critical components, such as your '''Batch Processes''', '''Content Models''', or document files for any '''Test''' or '''Production Batches'''.
Line 151:		Line 176:
	After the installer has finished running, open Grooper Config to upgrade the older versioned Grooper Repositories to the newly installed version.		After the installer has finished running, open Grooper Config to upgrade the older versioned Grooper Repositories to the newly installed version.

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5" style="margin:12px"
	\|-style="background-color:#36b0a7; color:white"		\|-
	~~\|style="font~~-~~size~~:~~14pt~~"\|'''FYI'''		\|style="font-size:125%; background-color:#36b0a7; color:white; width:28px; text-align:center"\|'''FYI'''
	\|		\|style="border: 4px solid #36b0a7"\|
	Major versions of Grooper change the Grooper Database in meaningful ways. These changes to the database must be reflected by upgrading the Grooper Repository. For major version upgrades (For example, 2.80 to 2021), ''all'' Grooper Repositories configured on an older version ''must'' be upgraded in order to connect to them in Grooper Design Studio or Grooper Dashboard.		Major versions of Grooper change the Grooper Database in meaningful ways. These changes to the database must be reflected by upgrading the Grooper Repository. For major version upgrades (For example, 2.80 to 2021), ''all'' Grooper Repositories configured on an older version ''must'' be upgraded in order to connect to them in Grooper Design Studio or Grooper Dashboard.

Line 211:		Line 236:
	# Don't forget to press the "Save" button in the main screen of Grooper Config.		# Don't forget to press the "Save" button in the main screen of Grooper Config.

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5" style="margin:12px"
	\|-style="background-color:#f89420; color:white"		\|-
	~~\|style="font~~-~~size~~:~~14pt~~"\|~~'''~~⚠~~'''~~		\|style="font-size:250%; background-color:#f89420; color:white; width:28px; text-align:center"\|⚠
	\|		\|style="border: 4px solid #f89420"\|
	'''IMPORTANT''' - If present, make sure you compile all '''Object Libraries''' after the upgrade.		'''IMPORTANT''' - If present, make sure you compile all '''Object Libraries''' after the upgrade.

	'''IMPORTANT''' - The devs ''also'' strongly recommend that you perform validation on your repository ''after'' upgrading.		'''IMPORTANT''' - The devs ''also'' strongly recommend that you perform validation on your repository ''after'' upgrading.
	~~<li style="color:white>~~'''Object Libraries''' should be compiled ''before'' validating your repository to ensure best results.~~</li>~~		* '''Object Libraries''' should be compiled ''before'' validating your repository to ensure best results.
	\|}		\|}
	\|		\|

Dgreenwood: /* Perform a Simple Upgrade */

2022-06-01T20:59:40Z

Perform a Simple Upgrade

← Older revision		Revision as of 15:59, 1 June 2022
Line 63:		Line 63:

	Performing a backup will ensure you have something to revert to in the rare cases where the upgrade does improperly overwrite existing database values or files in your file store.		Performing a backup will ensure you have something to revert to in the rare cases where the upgrade does improperly overwrite existing database values or files in your file store.

			For information how to backup and restore your Grooper database and filestore, [[Backup and Restore Grooper Repository\|please visit this article]].
	\|}		\|}

Dgreenwood at 20:58, 1 June 2022

2022-06-01T20:58:45Z

← Older revision		Revision as of 15:58, 1 June 2022
Line 26:		Line 26:

	Performing a backup will ensure you have something to revert to in the rare cases where the upgrade does improperly overwrite existing database values or files in your file store.		Performing a backup will ensure you have something to revert to in the rare cases where the upgrade does improperly overwrite existing database values or files in your file store.

			For information how to backup and restore your Grooper database and filestore, [[Backup and Restore Grooper Repository\|please visit this article]].
	\|}		\|}