2022:Upgrading Grooper to a New Version - Revision history

Dgreenwood at 16:10, 5 August 2025

2025-08-05T16:10:14Z

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

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

2024-04-18T19:24:59Z

Randallkinard moved page 2022:Upgrading Grooper to a New Version (Concept) to 2022: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 2022:Upgrading Grooper to a New Version to 2022:Upgrading Grooper to a New Version (Concept) without leaving a redirect: new naming convention

2024-04-18T17:54:29Z

Randallkinard moved page 2022:Upgrading Grooper to a New Version to 2022: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: Dgreenwood moved page Upgrading Grooper to a New Version - 2022 to 2022:Upgrading Grooper to a New Version without leaving a redirect

2024-01-02T19:13:18Z

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

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

Dgreenwood at 19:13, 2 January 2024

2024-01-02T19:13:07Z

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

	~~</onlyinclude>~~
	~~[[Category:Articles]]~~
	~~[[Category:Version 2021]]~~

Dgreenwood at 15:34, 7 March 2023

2023-03-07T15:34:46Z

← Older revision		Revision as of 10:34, 7 March 2023
Line 42:		Line 42:
	\|}		\|}

	== How To ==		=== How To Perform a Simple Upgrade ===

	~~===~~ Perform a Simple Upgrade ===

	{\|cellpadding="10" cellspacing="5" style="margin:12px; width: 100%"		{\|cellpadding="10" cellspacing="5" style="margin:12px; width: 100%"

Dgreenwood at 19:52, 6 March 2023

2023-03-06T19:52:41Z

← Older revision		Revision as of 14:52, 6 March 2023
Line 4:		Line 4:

	== About ==		== About ==
			<onlyinclude>
	You can upgrade directly from version 2.72, 2.80, 2.90 or 2021 to version 2022 (For upgrading from versions older than 2.72, you must upgrade to 2.72 before upgrading to 2022).		You can upgrade directly from version 2.72, 2.80, 2.90 or 2021 to version 2022 (For upgrading from versions older than 2.72, you must upgrade to 2.72 before upgrading to 2022).

Line 266:		Line 266:
	</tabs>		</tabs>

			</onlyinclude>
	[[Category:Articles]]		[[Category:Articles]]
	[[Category:Version 2021]]		[[Category:Version 2021]]

Dgreenwood at 19:34, 12 December 2022

2022-12-12T19:34:44Z

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

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

Dgreenwood at 19:10, 8 December 2022

2022-12-08T19:10:11Z

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

	~~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.

			\|}

	'''IMPORTANT!!!''' The organization of object resources in the node tree has changed drastically in version 2022 with the introduction of '''Projects'''. For more information on '''Projects''' please visit the following:		{\|cellpadding="10" cellspacing="5" style="margin:12px; width: 100%"
			\|-
			\|style="font-size:200%; background-color:#662d91; color:white; width:28px; text-align:center"\|'''‼'''
			\|style="border: 4px solid #662d91\|
			'''IMPORTANT!!'''

			The organization of object resources in the node tree has changed drastically in version 2022 with the introduction of '''Projects'''. For more information on '''Projects''' please visit the following:
	* [[Project]] - This is the full '''Projects''' article. It has general information about the new '''Project''' object in Grooper.		* [[Project]] - This is the full '''Projects''' article. It has general information about the new '''Project''' object in Grooper.
	* [[Project#Projects and Upgrading to 2022\|Projects and Upgrading to 2022]] - This contains specific guidance around upgrading from an older version of Grooper to version 2022 and how to navigate the new '''Project''' architecture.		* [[Project#Projects and Upgrading to 2022\|Projects and Upgrading to 2022]] - This contains specific guidance around upgrading from an older version of Grooper to version 2022 and how to navigate the new '''Project''' architecture.
			\|}

	== How To ==		== How To ==
Line 23:		Line 46:
	=== Perform a Simple Upgrade ===		=== Perform a Simple Upgrade ===

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

Line 36:		Line 61:
	\|}		\|}

			{\|cellpadding="10" cellspacing="5" style="margin:12px; width: 100%"
	{\|cellpadding="10" cellspacing="5"
	\|-		\|-
	\|style="font-size:125%; background-color:#36b0a7; color:white"\|'''FYI'''		\|style="font-size:125%; background-color:#36b0a7; color:white; width:28px; text-align:center"\|'''FYI'''
	\|style="border: 4px solid #36b0a7"\|		\|style="border: 4px solid #36b0a7"\|
	~~The process of~~ upgrading to version 2021 ~~and~~ upgrading to version ~~2022 is identical~~. ~~This article is taken from the v2021 installation~~ and ~~setup guide~~.		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.
	\|}		\|}

	<tabs style="margin:20px">		<tabs style="margin:20px">
	<tab name="Before You Begin" style="margin:20px">		<tab name="Before You Begin" style="margin:20px">

Dgreenwood at 21:07, 1 June 2022

2022-06-01T21:07:18Z

← Older revision		Revision as of 16:07, 1 June 2022
Line 1:		Line 1:
	<blockquote style="font-size:~~14pt~~">		<blockquote style="font-size:125%">
	So you're ready to upgrade?		So you're ready to upgrade?
	</blockquote>		</blockquote>
Line 24:		Line 24:

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5"
	\|-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:225%; background-color:#f89420; color:white"\|⚠
			\|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'''.

	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]].
	\|}		\|}


	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5"
	\|-style="background-color:#36b0a7; color:white"		\|-
	~~\|style="font-size:14pt~~"\|'''FYI'''\|\|The process of upgrading to version 2021 and upgrading to version 2022 is identical. This article is taken from the v2021 installation and setup guide.		\|style="font-size:125%; background-color:#36b0a7; color:white"\|'''FYI'''
			\|style="border: 4px solid #36b0a7"\|
			The process of upgrading to version 2021 and upgrading to version 2022 is identical. This article is taken from the v2021 installation and setup guide.
	\|}		\|}

	<tabs style="margin:20px">		<tabs style="margin:20px">
	<tab name="Before You Begin" style="margin:20px">		<tab name="Before You Begin" style="margin:20px">
Line 59:		Line 65:

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5"
	\|-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:225%; background-color:#f89420; color:white"\|⚠
			\|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'''.

	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]].
	\|}		\|}

Line 105:		Line 115:

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5"
	\|-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:225%; background-color:#f89420; color:white"\|⚠
			\|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'''.

	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]].
	\|}		\|}

Line 152:		Line 166:

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5"
	\|-style="background-color:#36b0a7; color:white"		\|-
	~~\|style="font-size:14pt~~"\|'''FYI'''		\|style="font-size:125%; background-color:#36b0a7; color:white"\|'''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 212:		Line 226:

	{\|cellpadding="10" cellspacing="5"		{\|cellpadding="10" cellspacing="5"
	\|-style="background-color:#f89420; color:white"		\|-
	\|style="~~font-size~~:~~14pt~~"~~\|'''⚠'''~~		\|style="font-size:200%; background-color:#f89420; color:white"\|⚠
	\|		\|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.
	\|}		\|}
	\|		\|