10. Migrating to HOPEX V5?
If you are an existing customer of HOPEX, you will be migrating your environment to HOPEX V5.
You must follow the following rules:
• The custom package is now mandatory starting from HOPEX V5 onward.
• All resources previously contained in Mega_Usr folder must now be stored in the custom module.
For the customization already imported within the SystemDb. You have 2 possibilities:
Option 1: Use the existing customization
This means:
• Let the customizations within the SystemDB repository.
• Add all of the new customizations (even modifications of existing customization) following the process described in this document.
Benefit:
Safe to avoid regression on customization.
Drawback:
The custom module does not contain “all” the customizations since “Day-0”.
Option 2: Rebuilt the environment
This means:
• Start from a totally new environment (with no customization).
• Recreate previous customization and package them following the process described in this document.
• Any new customizations must follow the process described in this document.
Benefit:
Safe to start from a “clean” ground and get rid of the past.
Drawback:
Takes more time and a is bit riskier in terms of regression.