Installation and Deployment > How to Migrate to HOPEX V4 > Check upgraded data
Check upgraded data
 
First control of migration
Check data modelling consistency
Other checking indications
It is highly recommended to back up each environment once it has been upgraded.
 
The standard installation and upgrading process takes care of all the conversions that can be automated. Technically speaking, conversion success is guaranteed by:
1. The correct execution of the environment automatic upgrade processing.
If errors are met at this step, the migration process must be stopped so that a diagnosis is made. Carefully check the Mega error log.
2. The correct execution of all mandatory conversions for the system database.
If errors are met at this step, the migration process must be stopped so that a diagnosis is made.
3. The correct execution of all mandatory conversions for each data repository.
If errors are met at this step, the migration process must be stopped so that a diagnosis is made.
 
After complete execution of the migration process, it is highly recommended to check data and customizations through:
• First control of migration: run a quick tour to check that data looks correct.
• Check of data consistency: run utilities to enforce rules regarding data structure.
• Other checking indications.
 
First control of migration
It is highly recommended to run a quick tour and check that upgraded data looks correct. Of course, this kind of check cannot be exhaustive, but it usually enables to have a first feedback and quickly identify certain migration issues.
 
Example of scenario:
1. Open a private workspace (ex-transaction).
2. Browse through objects using query tools, navigation trees and diagrams.
3. Perform insignificant updates (ex: change a character in a comment value, slightly move an object in a diagram...).
4. Dispatch private workspace.
 
Check data modelling consistency
In previous versions, many things were tolerated, although not recommended. In order to ensure better consistency, there is a need for a thorough review of the repository content and, potentially, some cleaning and tidying tasks to perform. This should be considered as a separate project.
 
Other checking indications
If extensions were made to the metamodel, they must be reviewed regarding the structuring rules described above.
 
If customizations have been made (property pages layer, diagram configuration layer, templates, programs based on script APIs…), a specific check is required based on initial customization specifications. As customizations are often based upon standard layers, they may not be ready to use, and they may have a different look and feel. This check requires functional and platform development skills.
 
Topic
Comment
Business Person
From HOPEX V4, Business Person is not supported
A conversion tool converts links to Business Persons towards Responsibility Assignment to Person (System).
It is recommended to review customizations related to this
Solution HOPEX Business Process Analysis
With HOPEX V4, there is a new behavior for process diagrams (Organizational Process Diagram…)
Items that are considered as part of the model are automatically added to each diagram which can create unexpected behaviors. This feature is disabled by default from HOPEX V4.0 CP4 using the related option. For more details see KB 00009414 in HOPEX Knowledge Base
Custom API code
It is recommended to review the customized macros and applications using API script, in particular for Administration APIs. Review should be based on initial functional specifications.
Custom authentication
It is required to review authentication in case of fully customized authentication provider. Review should be based on initial functional specifications.
Custom questionnaire templates converted to Standard Mode (questionnaire builder)
A specific report enables to understand to what extend custom questionnaire templates are compatible with Standard mode.
If ever specifications of custom questionnaire templates cannot be fully converted automatically, a change of customization will be required on project resources.
See document 'New Questionnaire Builder – Migration of Existing Clients' for more details.
IRM Solutions (ex-GRC Solutions)
For certain solutions (HOPEX Enterprise Risk Management, HOPEX Internal Control, HOPEX LDC, HOPEX Internal Audit), the web desktop have changed.
It is required to review desktop execution if customization have been made or if projects wants to keep classic desktops for compatibility (not recommended). Review should be based on initial functional specifications. This is a customization expert work.
Note also that certain profiles related to Solution IRM/Internal Audit have been deprecated and are not available by default. See KB 00008953 in MEGA Community for more details
HOPEX Explorer
This product is deprecated. Profile Explorer Writer is no longer available. It is recommended to implement
• Viewer users for consultation access
• Contributor users for limited edition access
Contact your MEGA account manager if you need more details.
HTTP deployment
From HOPEX V4 each new deployment should be made in HTTP/SSL mode (communication between HTML browser and HOPEX Front-end). This is a standard security practice
MEGA is not committed to investigate all errors met in HOPEX V4 and higher version with HTTP mode
If no SSL certificate is available when installing, installation can be made temporarily in HTTP mode. It must be configured to HTTPS/SSL mode before switch to production.
Options
This list of changes is not exhaustive
Option 'Authorize HOPEX data modification' was moved to folder 'Installation > Customization'.
Option 'Business person management' is removed as this Metaclass and related feature are removed. Conversion tools are available.
Note that Option 'Paste without formatting' is now enabled by default. This means that values are paste in text only format.
Profiles management
It is recommended to review the profile execution for custom profiles. Review should be based on initial functional specifications.
Note that from HOPEX V3, CRUD configuration is saved on a system object Set of UI Access Rights (no longer directly on Profile). A conversion tool is run automatically.
See KB 00008641 in MEGA Community for more details
Report Template
Certain standard report templates (HTML) are removed from standard: they are no longer maintained by MEGA.
Situation varies with the history of the environment
For environments created with HOPEX V4 and higher, such Report Templates are not available (not installed). Actions are necessary to restore them if needed.
For environments updated to HOPEX V4 and higher, such Report Templates are available. They are renamed with a prefix: ex: _(Out of Support)_Activity Exchange Balance
See KB 00008963 in MEGA Community for more details
Web Desktops
It is highly recommended to switch to Universal Desktop configuration
• When developing new desktops
• When migrating data to HOPEX V4
Web services
It is required to review web services execution. Review should be based on initial functional specifications.
 
The above list is not exhaustive.