PLATFORM - Installation and Deployment > How to Migrate to HOPEX Aquila (V6.0) > Post-migration
4. Post-migration
 
Review changes of HOPEX Aquila
Study adaptations to HOPEX Aquila
Test customizations and interfaces
Organize UAT session
Loop until migration is ready
 
4.1. Review changes of HOPEX Aquila
 
Review again the release notes on MEGA Community to focus on changes and items removed and deprecated.
• An item removed in HOPEX Aquila can no longer be used in this version.
• An item deprecated in HOPEX Aquila still be used in this version.
However it will be removed in a future version and it is recommended not to use it.
 
 
Key changes
(not exhaustive list)
Indications
Product removed
 
Discuss with the account manager to see if MEGA has an offer to your need.
Profiles removed
 
This will impact the web desktops (GUI) and workflow definitions used. This can also impact custom featured plugged on web desktop.
Switch to recommended profiles
Profiles deprecated
 
Think about switching to recommended profiles
Authentication mode removed
LDAP authentication is removed. Think about implementing SAML2 or OpenID
Look of homepage
With new web desktops (GUI), look of homepage is different. It is no longer possible to display tiles.
Cards view
With new web desktops (GUI), a cards view provides an overview on the essential properties.
Macros calling CreateObject
 
From HOPEX V6.0, it is forbidden to call CreateObject in a macro for security reason (example Set fso = CreateObject("Scripting.FileSystemObject")
…
 
 
If source version is HOPEX V4.0, see also Additional changes of HOPEX Aquila (HOPEX V4.0).
 
MEGA can assist you in managing changes. For this please contact your Service Director.
 
 
4.2. Study adaptations to HOPEX Aquila
 
Once changes and impacts are identified to need to decide and plan changes.
 
Common changes
(not exhaustive list)
Comment
Adapt homepage
Tiles displayed by default or tiles added manually (Add tiles) can be replaced with links (shared for the profile). A customization is needed for this.
Shortcut tiles created from objects (add to homage page) are converted automatically to links.
Adapt customization of made to removed profiles
Custom feature (ex: menu item calling a specific processing) plugged on web desktop need to be adapted to the new web desktop.
Adapt fully customized profiles
A specific study is needed.
Adapt custom profiles and
Custom featured plugged on web desktop.
 
Adapt cards view
Cards view are configured for standard Metaclass. A customization is needed to configure custom MetaClass.
 
MEGA can assist you in any kind of adaptation. For this, please contact your Service Director.
 
See online documentation for HOPEX V6.0
• Adapt homepage: PLATFORM - Customization (Windows) > Customizing the User Interface > Versatile Desktop > Using a Working Environment Template (WET) … Customizing the Quick Access block
• Adapt web desktop: PLATFORM - Customization (Windows) > Customizing the User Interface > Versatile Desktop
 
Note that customizations (external files, update of SystemDb) must follow procedure used by customization module (has.custom) and be documented.
 
4.3. Test customizations and interfaces
 
Once customizations are made, customizations need to be checked.
If a test plan exists, follow it.
Otherwise, an inventory is needed to identify and check customizations.
 
Main customization types
Indication
Report Template
Run an check each custom template on sample data
Report Template (MS Word)
Run an check each custom template on sample data
Web site
Run and check each custom web site
Workflow Definitions
Run and check each custom workflow on sample data
MetaPropertyPage
Check each custom property page on sample data
Questionnaire Template
Assessment Template
Run and check each assessment template on sample data (*)
 
(*) If source version is HOPEX V4.0 and Questionnaire Builder was not used, a conversion is required. See Additional changes of HOPEX Aquila (HOPEX V4.0).
 
Interfaces and authentication also need to be checked.
If a test plan exists, follow it.
Otherwise, an inventory is needed to identify and check interfaces.
 
Main items
Comment
Web site generation scheduler
Run and check scheduler. Review should be based on initial functional specifications
GraphQL
Check API key used. Check connection to GraphQL interface
Web services
Review web services execution. Review should be based on initial functional specifications. It may be necessary to re-generate API keys
External authentication (SAML2, OpenID, IIS)
Configure and check authentication. Review should be based on initial functional specifications
…
 
 
It is useful to have access to data and customizations in the source version to compare source and target.
 
Note that if several HAS instances exist on a machine, only one can run components using Administration API script at a given moment.
See later in this document: How to set a HAS Instance as current in registry?
 
4.4. Organize UAT session
 
Once data are migrated and customizations are checked, it is required to test the end user scenarios and data (diagrams…).
If a test plan exists, follow it.
Otherwise, it is recommended to organize UAT.
 
4.5. Loop until migration is ready
 
Each negative test feedback should lead to a change in the migration procedure.
 
A change can be:
• A data or customization reprocessing in the source version
• A change in configuration (modules deployed, options…) in the target version
• A change in customization in the target version
• A fix on HOPEX Aquila provided by MEGA
 
Each change should be documented in the specific migration document.
Each change in customization should be packaged in the customization module.
 
Then a new migration loop is needed to test changes:
• Initialize again test platform (restore again production data…)
• Follow specific migration document (updated version)
• Test data and customization
 
When no significant test feedback is detected, you can run the migration for real:
• Initialize again test platform (restore again production data…)
• Follow specific migration document (final version)
 
MEGA can assist you and manage the whole migration process. For this, please contact your Service Director.