Setting User Preferences

This page helps you to customize settings to suit your preferences.

To view the user preferences:

  1. Sign in to Foglight cloud with your Quest account.
  2. Click on your profile icon (top right screen corner) and select User Preferences.

On this page, you can view or edit the following preferences:

  • Language- Set your preferred language. The default, Browser Language, will retrieve the list of your preferred languages from your browser and, in order of preference, use the available data. Foglight is currently localized only to English, but it will still pick up your browser preference locale for use with output of dates, numbers, paper sizes and temperature.

  • Refresh Interval- This is the default interval used to refresh any monitoring views that you are viewing. The default is 300 seconds (5 minutes).

  • Time Zone- You can select an appropriate time zone. By default, the Server Time is selected. To change the time zone, select User Time and then select the desired zone from the list of available time zones.

  • Time range- This is the time range to be used when viewing historical data upon your initial login. The default is “last hour”. To edit the time range, select the required option from the Time Range dropdown list. The default time range is set and displayed on all the dashboards.

  • Working module- Displays your module.

  • User Email Address- Displays your email address.

  • Themes-

    • Print- This specifies the theme to be used for printed views, whether through the browser (Internet Explorer only) or PDF.
    • Remote- This specifies the theme to use when viewing Foglight views remotely in another portal mechanism, such as SharePoint, WebLogic, or Google.
      Following options are available in the dropdown list:
      • Default- Displays the default theme which is the light theme.
      • Application- Displays the views in the light theme.
      • Monitoring- Displays the views in the dark theme.

  • PDF Defaults-

    • Page Size- By default, the page size (A4 or Letter) is inferred from your locale. This can be explicitly overridden here.
    • Orientation- The orientation of the printed page is specified here. This can be overridden by a specific report. If the report does not specify which to use, then this value is employed.

  • Unit Defaults-

    • Temperature- By default, the desired temperature scale is inferred from the local settings, but it can be specifically set here.

  • Advanced The Advanced grouping contains three preferences and has three sub groups.

    • Page Flow Overrides This feature allows drill-downs to a particular page, for this user, to be redirected to a different page instead.

    • Data Sources This is an advanced feature. It is possible at times to have more than one instance of a particular data source. This allows a user to set the default instance that s/he prefers to work with.

    • Validation Exceptions Allow Renderer-based type conversions As of the Ganges release, setting a renderer on a Runtime Value to convert data is discouraged. Converter Functions should be used instead. When this user preference is selected, renderers as converters will be taken into account when a configuration property value is being validated. These are the specific cases where this applies:

      • for properties of type Any or String, if the Runtime Value set on the property has a renderer specified which can convert a list to a single object, the value of the Runtime Value will be considered to be a single object. For example, the List Renderer can do such conversions.
      • for properties of type Color, ImageReference or String, if the Runtime Value set on the property has any renderer specified, it is assumed that the renderer will convert the value to the correct type
      • for all properties types, the type that the Runtime Value set on the property will evaluate to will be determined. If that value does not have a path and there is a Type Registry entry for that type that has a renderer specified or if the value does have a path (which means there’s a corresponding property) and there is a Type Registry entry for the type of the value and there is a renderer specified for the corresponding property, it is assumed that the renderer will convert the value to the correct type.

        If this user preference is on, the for-rendering edit option will be ignored and the renderer attribute of Runtime Values will be made available in the editor.

Allow Renderer input type mismatch As of the Ganges release, validation has been added to ensure that whenever a renderer is set on a Runtime Value, the value to be rendered is assignable to the expected input type/list of the renderer as specified by its Input Value. If the renderer on which the definition is based does not support an Input Value, then the validation will fail.

To disable this validation, check this validation exception user preference.

Hide deprecation warnings As of the Interlagos release, validation has been added to warn about a view/task/renderer based on a deprecated component and when a deprecated property is set. Check this user preference to disable these validations.

Disable User Interaction Persistence By default, Foglight remembers the vales you select on pages and things like splitter locations and selected tabs. It persists this information even if you log out and log back in. This setting prevents that.

As a dashboard developer, it is useful to set this when testing views to allow you to return to the state a page would be in the first time a user ever visits it.

Show legacy Binding attributes By default, Foglight does not show legacy Binding attributes, such as the Iterate Over 1st Parameter attribute of Query Selection Runtime Values. Check this user preference to show such attributes.

Always show legacy configuration properties By default, Foglight only shows legacy configuration properties in the Configuration tab in the Definitions Editor if a legacy configuration property is set to a value which is not the property’s default value (or not set at all if the property does not have a default value). However, if the this user preference is on, then legacy properties will always be shown.

Show deprecated Definitions By default, deprecated definitions are not shown in the list of definitions in the Definitions Editor (including when a search is applied). Check this user preference to show deprecated definitions. Of course, even if this user preference is on, if an advanced search is applied that has a rule where Deprecated “is false”, then deprecated definitions won’t be included in the search results.

Include individual scripts For significant performance gains, many of the supporting files that are sent to the browser to enable the advanced functionality of the Foglight UI, are combined and compressed before they are sent to the browser.

This makes it difficult to debug and identify problems. Checking this and reloading the UI enables the slower, discrete files and provides more useful information in case of failure.