|
Authentication mode
|
Check in HOPEX V5.0
|
Supported in Aquila
|
|
OpenID
|
Installation options, Installation > Authentication > Identify providers > Open ID Connect (OIDC)
'Activation of the OpenID Connect identity provider' is checked
|
Yes
|
|
SAML2
|
Installation options, Installation > Authentication > Identify providers > SAML2
'Active' is checked
|
Yes
|
|
Windows (IIS)
|
Installation options, Installation > Authentication > Identify providers > IIS Windows
'Activation of Windows IIS identity provider' is checked
|
Yes
|
|
HOPEX (MEGA)
|
Active by default
|
Yes
|
|
|
|
|
|
LDAP
|
Environment options
Installation > User Management > LDAP
'Authentication mode' is set to 'LDAP'
|
No
|
|
Solution Pack
|
Module
|
|
Archimate V3
|
Archimate V3.1 (**)
|
|
HOPEX360
|
HOPEX360
|
|
NAF
|
NAF Framework
|
|
Privacy Management
|
Privacy Management Content
|
|
SGBD SQL Type - DB2 OS 390 Version 10
|
Database Design DB2 OS 390 V10
|
|
SGBD SQL Type - DB2 OS 390 Version 11
|
Database Design DB2 OS 390 V11
|
|
SGBD SQL Type - DB2 UDB Version 10.5
|
Database Design Postgres SQL 9.3
|
|
SGBD SQL Type - DB2 UDB Version 10.5
|
Database Design DB2 UDB V10.5
|
|
SGBD SQL Type - DB2 UDB Version 9
|
Database Design DB2 UDB V9
|
|
SGBD SQL Type - MySQL Version 4.1
|
Database Design MYSQL V4.1
|
|
SGBD SQL Type - MySQL Version 5
|
Database Design MYSQL V5
|
|
SGBD SQL Type - Oracle 11
|
Database Design Oracle 11
|
|
SGBD SQL Type - SQL Ansi ISO 9075.1992
|
Database Design SQL Ansi ISO 9075 1992
|
|
SGBD SQL Type - SQL Server 2008
|
Database Design SQL Server 2008
|
|
SGBD SQL Type - TeraData Version 14
|
Database Design TeraData V14
|
|
Key changes (not exhaustive list)
|
Indications
|
|
Searchable Metaclass
|
List of MetaClass available with tool Search by Object Type can be different because a previous filtering (Technical level, option 'Metamodel access') is no longer considered.
Tuning of profiles can be required using permission CRUDS (searchable).
|
|
Advanced MetaClass
|
The list of MetaClass available with certain tools can be different because a previous filtering (Technical level, option 'Metamodel access') is no longer considered.
Tuning of metamodel can be required using property 'Meta Usage' (Business, Technical) on MetaClass.
Option ‘Display Technical Metamodel' enables to display systematically MetaClass flagged as 'Technical'.
|
|
Questionnaire Template
|
This applies if you did not use Questionnaire Builder. Custom questionnaire templates are automatically converted to new format (Questionnaire Builder)
It is necessary to check if converted templates are fully compatible. A specific report enables to understand this. If ever specifications of custom questionnaire templates cannot be fully converted automatically, a change of customization will be required on project resources.
|
|
Profiles of solution 'HOPEX Data Architecture' (e.g.:_Information Architecture)
|
This applies if you do not use the Solution 'HOPEX Data Governance' in HOPEX Aquila but only 'HOPEX Data Architecture'.
It is necessary to run the utility MEGA Repository - Conversion of Profile 'Data Asset Manager' to 'Data Architect'. Then use profile 'Data Architect' instead of profile 'Data Asset Manager' used in HOPEX V4.0)
|
|
GraphQL
|
Core GraphQL modules are installed by default with bundle HOPEX. GraphiQL is an optional module named HOPEX GraphQL IDE (graphql.ide). Authentication mode is different. An API key is required instead of bearer token.
Calls to GraphQL queries are different in HOPEX Aquila. It is required to review calls in third party applications
|
|
Private workspace
|
With HOPEX Aquila, all web desktops are configured with public workspaces except the one used by profile HOPEX Customizer (required for customizations)
Behavior of a desktop varies with its configuration: • Public workspace: updates are made public automatically so that users share the same vision.
• Private workspace: end user has its private vision and can decide to refresh, discard or dispatch it.
|