Configuration
Installation
The website template is delivered as a Solution Pack.
To install the website template:
1. From HOPEX Community, download the HOPEX 360 package into the <HOPEX Installation folder>\Utilities\Solution Pack.
Link: https://community.mega.com/t5/Add-On-V3-V4/HOPEX-360/td-p/23739.
Link: https://community.mega.com/t5/Add-On-V3-V4/HOPEX-360/td-p/23739.
2. Unzip it in the same location.
3. In HOPEX Administration application, connect to the environment.
4. In the Repositories folder, rigth-click SystemDb and select Object Management > Import Solution Pack.
5. Select HOPEX360_V4 and click OK.
The Website Template and all its components are installed.
Required files
The HOPEX environment Mega_Usr folder is updated with the files required by the website template:
• CSS files
• JS files
• Images
• Fonts
Translation
Translations are available on the following items:
• Menu
• Section
• Widget
• Table header
For each of them, a reference is written in the code to the relevant Code Template, as follow:
|
[Variable=CodeTemplate Id=8F68A4995E7868E4/]
|
Where the Id is the HexaIdAbs of the code template, as shown below in the _Code Template property page:
The text can be modified in General > Translation.
Post-generation script JSON files
JSON files are generated as part of the website generation to cover different functionalities. These files are stored in the \json folder of the generated website.
Those JSON files contain the key data used in the reporting, via java script functions.
This is implemented through 4 MetaCommand Managers triggering the relevant macros:
• HOPEX EA_Post Generation Script App JSON. This generates one JSON per Application to enable the Application Impact diagram. The files are named as follows:
o <Application hexaidabs>_integration.json
• HOPEX EA_Post Generation Script CIO Dashboard JSON: this generates 4 JSON files:
o DatasArrayCapabilityMap.js
o DatasArrayPortfolioBusinessCapability.js
o DatasArrayPortfolioTechnology.js
o DatasArrayPortfolioTimePeriod.js
• HOPEX EA_Post Generation Script Process and Capa Trees JSON
o DatasArrayBCMHierarchy.js
o DatasArrayProcessHierarchy.js
o DatasArrayBCMRationalization.js
• “HOPEX EA_Post Generation Script_Search Indexing”
 |
For relative link reason, this JSON is stored in \standard\assets\js folder.
|
o searchindexcontent.json
CIO Dashboard JSON
The ‘HOPEX EA_Post Generation Script CIO Dashboard JSON' MetaCommand Manager generates 4 JSON files:
• DatasArrayCapabilityMap.js
|
Topic
|
Key information
|
|
Purpose
|
This is a list of Business Capability Maps including:
- Name
- HexaIdAbs
The main purpose is to enable a filter for key reports
|
|
Pages using the file
|
The following 2 pages use this data as a filter on the Box in Box:
- Strategic Planning
- Rationalization
|
|
JSON data structure
|
var datasArrayCapabilityMap = [
{
capabilityMapName: "BCM To Be (EN) ", capabilityMapHexaIdAbs: "726B7F225E84F5C5",
},
];
|
• DatasArrayPortfolioBusinessCapability.js
|
Topic
|
Key information
|
|
Purpose
|
This is a list of Applications, the Portfolios they are connected to and the Business Capabilities they support.
|
|
Pages using the file
|
The following pages use this data:
- Main Dashboard: in the Application per Capability Widget
- Main Dashboard: in the Capabilities indicator
- Rationalization: to filter out the Applications overlayed on the BCM box in box
|
|
JSON data structure
|
var datasArrayPortfolioBusinessCapability = [
{
portfolioName: "_Toutes les Applications",
portfolioHexaIdAbs: "#",
applicationName: "API Gateway (EN) ",
applicationHexaIdAbs: "D37AD7455CF088CA",
applicationType: "D\u00e9veloppement Sp\u00e9cifique",
currentState: "Production",
applicationHosted: "Nuage : IaaS",
dataFreshness : "<6M",
gdprCompliance: "App OK",
overallCompletness: "75",
businessCapabilityName: "Gestion des clients (EN) ",
businessCapabilityHexaIdAbs: "F034F0705CF050BA",
},
];
|
• DatasArrayPortfolioTechnology.js
|
Topic
|
Key information
|
|
Purpose
|
This is a list of Applications, the Portfolios they are connected to and the supporting Technologies.
|
|
Pages using the file
|
The following pages use this data:
- Main Dashboard: in the Technology Compliance Widget
- Main Dashboard: in the Obsolete Applications indicator
- Main Dashboard: in the Vendors indicator
- Main Dashboard: in the Application per Vendor widget
|
|
JSON data structure
|
var datasArrayPortfolioTechnology = [
{
portfolioName: "_Toutes les Applications",
portfolioHexaIdAbs: "#",
applicationName: "API Gateway (EN) ",
applicationHexaIdAbs: "D37AD7455CF088CA",
applicationType: "D\u00e9veloppement Sp\u00e9cifique",
currentState: "Production",
applicationHosted: "Nuage : IaaS",
dataFreshness : "<6M",
gdprCompliance: "App OK",
overallCompletness: "75",
technologyName: "No technology",
technologyHexaIdAbs: "",
companyStandard: "",
technologyEndOfSupport: "", technologyEndOfExtendedSupport: "",
obsolescenceDate: "",
vendor: "",
},
];
|
• DatasArrayPortfolioTimePeriod.js
|
Topic
|
Key information
|
|
Purpose
|
This is a list of Applications, the Portfolios they are connected to and the attached Time Periods
|
|
Pages using the file
|
The following pages use this data:
- Main Dashboard: in the Application Evolution widget
|
|
JSON data structure
|
var datasArrayPortfolioTimePeriod = [
{portfolioName: "_Toutes les Applications",
portfolioHexaIdAbs: "#",
applicationName: "API Gateway (EN) ",
applicationHexaIdAbs: "D37AD7455CF088CA",
applicationType: "D\u00e9veloppement Sp\u00e9cifique",
currentState: "Production",
applicationHosted: "Nuage : IaaS",
dataFreshness : "<6M",
gdprCompliance: "App OK",
overallCompletness: "75",
timePeriodName: "API Gateway (EN) [Pr\u00e9paration]",
timePeriodHexaIdAbs: "F5AD10F15E7ECB46",
timePeriodStatus: "Pr\u00e9paration",
timePeriodAbsoluteStartDate: "2016/10/04 12:00:00",
timePeriodAbsoluteEndDate: "2018/01/01 12:00:00",
},
];
|
Tree list JSON
The ‘HOPEX EA_Post Generation Script Process and Capa Trees JSON' MetaCommand Manager generates 2 JSON files:
• DatasArrayBCMHierarchy.js
|
Topic
|
Key information
|
|
Purpose
|
The purpose is to provide the full hierarchical structure of the Business Capabilities and their supporting applications.
|
|
Pages using the file
|
The following page uses this JSON data:
- Business Capability Tree List
|
|
JSON data structure
|
var products = [
{text: "BCM To Be (EN) ",
modification_date:"2020/04/14 08:06:47",
performance:"", execution:"",
link: "726B7F225E84F5C5.htm",
id: "726B7F225E84F5C5",
parent:"0",
applications: [
{text:"N/A"}
},
];
|
• DatasArrayProcessHierarchy.js
|
Topic
|
Key information
|
|
Purpose
|
The purpose is to provide the full hierarchical structure of the Business Processes and their supporting applications.
|
|
Pages using the file
|
The following page uses this JSON data:
- Business Process Tree List
|
|
JSON data structure
|
var products = [
{text: "Business Process-2 (EN) ",
modification_date:"2020/04/16 10:48:07",
performance:"3",
execution:"3",
link: "51797E5D5E77826E.htm",
id: "51797E5D5E77826E",
parent: "9ACC0F275D444F86",
applications:
[{
text:"API Gateway (EN) ",
link: "D37AD7455CF088CA.htm"
},]
},
];
|
• DatasArrayBCMRationalization.js
|
Topic
|
Key information
|
|
Purpose
|
The purpose is to provide the full hierarchical structure of the Business Capabilities and the applications decommissing date
|
|
Pages using the file
|
The following page uses this JSON data:
- Rationalization Table
|
|
JSON data structure
|
var sales = [{
BCM: "BCM As Is",
BC1:"Market Access",
BC2:"Gestion des clients",
link: "F034F0705CF0502C.htm",
id: "F034F0705CF0502C",
date:"2020/06/27 12:00:00",
amount:"1"
}]
|
Application page JSON
The ‘HOPEX EA_Post Generation Script App JSON' MetaCommand Manager generates one JSON file per Application.
|
Topic
|
Key information
|
|
Purpose
|
The JSON file enables the Impact force diagram on each Application page
|
|
Pages using the file
|
Each Application Object Page
|
|
JSON data structure
|
{"root" :
{"id":"D37AD7485CF08ECB",
"name":"service-draws (EN) ",
"type_id":"B1EDB2562C14016F",
"type_name":"Application",
"href":"D37AD7485CF08ECB.htm",
"image":"../standard/appl.ico.gif",
"states":[ ]
},
"sources":
{},
"targets":
{"FD280B395C926AC9":
{"id":"FD280B395C926AC9",
"name":"AngularJS 1.7 (EN)",
"type_id":"2885299152A85717",
"type_name":"Technology",
"href":"FD280B395C926AC9.htm",
"image":"../standard/technology.ico.gif"
},
},];
|
Search
The “HOPEX EA_Post Generation Script_Search Indexing” MetaCommand Manager has a Macro attached which generates a ‘searchindexcontent.json' file.
|
Topic
|
Key information
|
|
Purpose
|
This JSON file is used to reference all the objects included in the website to enable a full text search
|
|
Pages using the file
|
In every page, the menu includes a magnifying glass to toggle the search tool.
This search is implemented using the Fuse library (https://fusejs.io/)
|
|
JSON data structure
|
{pages":
[{
"title":"",
"Object type":"",
"Modification Date":"",
"text":"",
"tags":"",
"url":""
},
{
"title":"<img src='../standard/APPL.ICO.gif'> API Gateway",
"ObjectType":"Application",
"ModificationDate":"2020/04/16 10:14:30",
"text":"",
"tags":"",
"url":"D37AD7455CF088CA.htm"
},
],};
|