2. Customization Capabilities
As mentioned in the introduction a wide range of elements can be customized. Depending on the customization you need to perform the action may be different. In the end, what is mandatory is that, including history, all your customization is contained in the “has.custom” module.
2.1. Metamodel, desktops, profiles
HOPEX contains a minimum of two repositories that can be impacted by your customizations:
• the SystemDB repository: it holds all metamodel, desktops… customized content.
• the Data repository: it contains objects that can be used sometime for customization such as “Keywords” or “Tags”.
Each change performed within the HOPEX Studio desktop is stored in the mentioned repositories.
At some point in the lifecycle of your customization you will need to extract these changes to push them in STAGE and then in PRODUCTION.
To generate this extract, see “Creating ” chapter.
2.2. Other resources
This section is not exhaustive.
Customizations include:
• Changing shapes in diagrams (*.MGS)
• Changing icon of object (*.ICO)
• Changing default logo or background (*.PNG or *.JPG)
• Changing some style (*.CSS)
• Changing some script (*.JS)
• Changing or adding behaviour (JAR/DLL)
For these customizations most of the changes are not stored in any databases. These are changes made to files of different types.
The rules are as follows:
• You cannot edit or replace the standard files provided by HOPEX.
• You store all your new or replacing/overriding files into the “has.custom module”.
If you respect the folder structure and hierarchy your custom file will be considered instead of the standard one.
Create your new resources and save them in the right location.
