How to update GCR version (1.0.0 vs 1.0.2)

Options
Center of Excellence
Center of Excellence Employee
5 Likes First Anniversary First Comment Name Dropper
edited February 26 in How-To Guides
1088x612_Article_Cover_How-to-Guide.png

1. Abstract

As you may know, in Q2 2023 the first version of GCR, the new Board Solution to manage Financial Consolidation has been released.

Since then, the development of the solution is not finished, and new patch releases will be frequently released.

The goal of this document is to provide guidance on how to update your current GCR version to the latest available.

More in detail, this document will be focused on the update between GCR 1.0.0 and GCR 1.0.2.

2. Context

The GCR update version will be managed through a Transporter Package, here below you will find guidance on how to use this tool with a specific focus on GCR solution.

3. Content

3.1 Preliminary Instructions

  • The first step needed is to clear these entities because they need to be reused in the latest version.
image.png
  • In the GCR patch release package you will find the folder “Application_Reset” and “Standard_Entities”.

Please take these two folders and replace them with the existing ones.

image.png

3.2 Snapshot

  • Go to “System Administrator” and click on “Data Model Snapshot”
image.png
  • Click on “+ Snapshot” in order to create your Snapshot of GCR and GCR_Log Database and assign to the Snapshot a name as you prefer.
image.png
  • In the same package release received, you will also find a snapshot version. Click on upload and select the snapshot from your folder
image.png

3.3 Update GCR data model

The Core of the GCR solution is the GCR data model, so we will explain in detail how to update the GCR Database, The same approach can be used to migrate also the GC_LOG Database

In order to proceed, please select the 2 relative snapshots (The one provided by Board Team and the one created by You), After having selected them, please click on Transporter Package.

Please make sure that on the left as Source Snapshot you must have the one provided by Board, and on the right, as Target The snapshots created by you.

image.png

By default, the Transporter will take all the changes of the source Database and apply those to the target.

However, it may be that your Database has been customized in different ways. (For example, the use of some customizable cubes, entities, or Data reader or for example modification of max item number of entities).

One fundamental assumption in order to be eligible to use the transporter is to not have created any Data reader, Cubes, or Entities from scratch, but instead have used the available ones of the Data model that are named “Customizable”.

Having said that, before proceeding, unflag all the cubes, Entities, and Data readers that have been modified compared to the standard version.

image.png

Click next, and you will find a check consistency button. Click on it.

image.png

The possible results of this check are:

  1. Success → If no errors are detected.
  2. Error → A possible case when the error appears is when the entity that has been unflagged is used in a cube.
  3. Warning → A possible case of Warning is when you are replacing a cube that already contains data.
image.png

The next step is to assign a name for this Transporter Package and decide if to flag or unflag the backup option. We warmly suggest keeping the backup option always flagged. Click Save in order to proceed.

You will find another screen with the list of all existing Transporter Packages. Consider only the one just created and click on Run in order to execute the update.

image.png

If everything works as expected, you will find the Last run log and the result as “Success”.

Please note that you may receive a warning message due to the several cubes for which the structure has been changed between the two different versions. You can proceed with the package, then make sure you follow the instructions here below.

The list of warnings will include the cubes:

image.png

3.4 Update GCR_LOG Database

Follow exactly the same process for the Update of the GCR_LOG Database. Of course, make sure to select the right Database.

3.5 Update Version

After having completed the transporter package a last step is needed.

Open the capsule Admin, and navigate to the screen “Quick Configuration Wizard”.

image.png

Click on “Update Version”.

image.png

This procedure will:

  • Update the GCR version name;
  • Eventually update new Entities;

After having completed successfully all those actions, you will be able to use the GCR application taking advantage of the fix and enhancements of the patch release.

For any doubts or additional info related to the Transporter tool, please refer To the Board manual in the Transporter overview section.

Tagged:

Comments

Categories