Further information can be found in Configuring the Sidebar
applications.json file defines the contents of the sidebar in Hub. All Hub applications use the same instance of this file served from
Defines all application entries.
|The case-sensitive id of the application. Must match the |
|The name of the application, shown in the sidebar.|
|A brief summary of the application.|
|The relative path to your application. |
v1 a path. Eg.
v2 and React a hash. Eg
|The icon classes for the application. Usually from Font Awesome|
|A case-sensitive list of permission names.|
|How to assert |
|Limits the application entry to the given environment and below. Eg. If this is set to "rc" the application will show in "dev", "int", and "rc".|
|A list of feature toggles required to show this application.|
|The version of Hub the application is built in. Used by the shell when loading. |
React apps use
Applications in the Hub sidebar are displayed as groups. What appears to be single application entries in the sidebar are groups with one application.
|The name to display for iQmetrix users or when no |
|A hash of brands to the name to display for that brand.|
|An array of applications ids to display in the group.|
|The application to open when the group is selected directly.|
|The icon classes for the group.|
|Hides the group when |
Defines the groupings of applications for users that do not have a parent entity of role
iQmetrix users will use these groups.
Defines the groupings of applications for users with a parent entity of role
Most end users fall under parent entities with the
settings Application Group#
The settings application group is a special case. It is used both as a standard sidebar application group and by the settings app.
Merging a change will trigger a build and a release into
INTautomatically through Azure DevOps Pipeline.
Though we try to ensure that
applications.jsonis always able to be promoted, it is still required that you ensure this prior to releasing beyond
INTby asking in #hub-developers