- This line was added.
- This line was removed.
- Formatting was changed.
This article describes how to customize the look and feel and the text content in the Nexus Service Station application and how to make general configurations that applies to all views. For configuration of the individual views, see the separate view pages.
There are three files used for configuration of Nexus Service Station:
|Type of file||File name||Folder|
|Style file||Program Files (x86)\Technology Nexus\Nexus Service Station\|
“xx-XX” is the name of each locale folder
Program Files (x86)\Technology Nexus\Nexus Service Station\locales
Each locale available will have its own sub folder, named xx-XX (for example, sv-SE for Swedish text content).
|Configuration file||Program Files (x86)\Technology Nexus\Nexus Service Station\| Expandall
Individual configuration of views
The views can be configured in different ways. For information about how to configure each individual view, see Views.
General configuration of views
An app flow contains views (visible to the user to interact with). There must always exist an app flow called “default”. The reason for this is if something fails in the application and it can not find the flow it is looking for, it will jump back to the flow called "default."
These are the settings made when an app flow is added.
These are mandatory settings that are used by all views.
When a view is added to an app flow by using the <add...> tag, these settings (that are shared by all views) can be made:
The <add> tag can also define a child-tag, <next...>. This tag has the following settings:
An IDC condition key that evaluates to true or false.