Galaxy Stylesheet - ASP 2020 R2 SP1 Patch 01

The exported stylesheet is a normal xml document.
Each element style has a unique id as identification. My guess is that the 'ID' determine under which section it will appear (Trend/Alarms/UserDefined).
One would have thought that it would be possible to extend the stylesheet if you follow the structure of and existing entry and ensure the ID is unique but that is not the case. The allowed ID's must either be hardcoded or exist in some config file. (I couldn't get it in the tables within the Galaxy DB). The importer spits a dummy when it encounters an ID that is not in its pre-configured ID list. (Surely the list is not hardcoded)

Is it possible to extend the stylesheet? 


I have x number of OMI Apps each with their own style requirements. (Customer is always right). Can I assign a different stylesheet to each OMI App?

Parents
  • Hi Marcell,

    Unfortunately one cannot add more styles, which certainly would be useful. Let's see if we can do something about that in future versions.

    However, Application Server and OMI allows for multiple style libraries in the same galaxy. One will be set as default, but the application can easily switch between style libraries in runtime by setting a property ("CurrentStyle" or something) on one of the built-in namespaces (I forget it's name). I'm not sure which version added this but I'm reasonably sure that it is there in 2020 R2 SP1.

Reply
  • Hi Marcell,

    Unfortunately one cannot add more styles, which certainly would be useful. Let's see if we can do something about that in future versions.

    However, Application Server and OMI allows for multiple style libraries in the same galaxy. One will be set as default, but the application can easily switch between style libraries in runtime by setting a property ("CurrentStyle" or something) on one of the built-in namespaces (I forget it's name). I'm not sure which version added this but I'm reasonably sure that it is there in 2020 R2 SP1.

Children