Dashboard Limitations

When sending customized displays to the Web Application, there are certain features which are currently not supported, these include:

General

  • Windows Themes for different colors and fonts are not supported. The Web Application has a standard background and foreground colors as well as standard fonts.

  • Status and caption bars for individual windows within a Display are not supported.

  • Row numbers on the left of tables are not supported.

  • Pop-up prompts are not supported.

  • Reports are now set up under Report Central and drill-downs from Displays to reports are not supported.

  • Options for clearing the workspace or leaving the workspace unchanged when drilling down through links etc. are no longer supported. Users will need to utilize the tab functionality supported on the browser. However, drill-downs from chart legends do not support “Open in new tab”.

  • Spacing between windows, as well as margins for displaying data inside a window, is different in the Web Application when compared to the Windows Client. At times, it will be necessary to resize the windows in a Display to ensure that data remains visible in the Web Application.

  • Icon color setting, regarding whether data is available, is no longer supported.

  • Sending multiple Displays to the web with the same name, under different directories, will end up having only the last one sent being available.

  • MIN/MAX are not supported in the Web Application. If a data field MIN/MAX option is selected for a Display that is sent to the web, only the STD value will be rendered.

  • Time modes other than ‘Server Time’ are not supported. Data will always be rendered based on server time.

  • Time Display modes including ‘Time and Mode’, ‘Time and Offset’ and ‘Time, Mode and Offset’ are no longer supported. Time will be rendered as ‘Time Only’ mode in the Web Application.

  • Visual alarms on columns are not supported in the Web Application. Displays with visual alarms on columns are converted to have the visual alarm on the cell only.

  • The maximum length of a Custom Legend in a display window is (about) 4096 characters. If there are more characters, sending the display to the Web Application may appear to succeed, but a dashboard is not created. Custom Legends are created by default for each window in a customized display and are a concatenation of all key fields in the record that is displayed. Therefore, customized displays for records with a lot of key fields may experience this problem. It is advised to change the Custom Legend before sending the display to the Web Application.

Databases

  • Drill-downs and links to Database Collections, Database Summaries, Thresholds, Analysts and Commands are disabled in the Web Application.
  • Drill-downs and links to a Database Replay where there is a specific stop time based on interval may not show the expected timing in the Web Application.
  • When a Database Replay reaches the 'end of data' as stored on disk, the replay will not refresh to automatically show new data as it is added to the database. This is by design, and in order to see newly added intervals, refresh the browser to load new data.

Charting

  • Cache Intervals in chart presentations are not supported.
  • Chart Trending is not supported.
  • Threshold line is not supported.

  • 3D charts are not supported. They will be rendered as 2D charts only.

  • Stacked ‘Column-Line’ and ‘Line-Line’ charts are not supported.

  • Stacked line charts are not supported. They will be rendered as stacked area charts.

  • Line thickness is not supported. All line graphs are drawn with the same line thickness. Line charts with a thin line and a large number of intervals or a large number of lines in the Windows Client might not be readable under the Web Application. In this case, please consider reducing the number of items plotted on the line graph.

  • Charts are always visible under the Web Application. Displays, where chart legends are enlarged to take up the space of the entire window to hide charts will not be supported.

  • Chart legends are not resizable in the Web Application. Displays, where chart legends are resized to show limited data in the Windows Client will not display the same way under the Web Application.

  • Very small spark line style charts without legend and axis labels are not supported in the Web Application.

  • Spacing for time scales in charts is different between theWindows Client and the Web Application. If an ‘Automatic Label’ is not selected, the time scale may be rendered with large overlaps, making the time scale unreadable. Change the time scale to use ‘Automatic Label’ and send to web again, if necessary.

Meta Fields

  • Not all META fields are supported in the Web Application. Support for the following items has been removed and Displays using these fields will need to be adjusted before they can be sent to the web.

META.CHARTSTARTTIME

META.CHARTENDTIME

META.INTERVALFORMATTED

META.STARTTIME

META.TOTALCOLUMN

META.USERNAME

  • META.SHORTFIELDNAME in a chart series condition is not supported. Series coloring may not be as expected in the Web Application.

EMPTY Fields

  • Checking if a field is EMPTY in a where clause via a prompt such as FIELD = #EmptyPrompt is not supported. It will be necessary to adjust the where clause in the dpy file to check for (FIELD = EMTPY AND #EmptyPrompt = EMPTY) explicitly.

  • Checking if a field is EMPTY in a where clause can be done with either FIELD = EMPTY or FIELD = “EMPTY” under the Windows Client. However, only FIELD = EMPTY is supported under the Web Application. FIELD = “EMPTY” will be checking for the literal string “EMPTY” instead.

Prompt Substitution

  • The Web Application is much stricter regarding field and prompt comparison, a prompt must be of the same type as the field. Therefore, a prompt with a value of “All” cannot be used for comparison with an integer field, such as the port number.

  • Prompts that are not explicitly specified in a drill-down may not be available in the Web Application as part of the URL. If prompts are missing from the URL, it will be necessary to ensure that the prompts are explicitly specified in a drill-down in the display file for IRGUI. Sometimes this will require adding extra user defined fields in order to temporarily store prompts so that they can be passed between multi-level drill-downs.

  • When a field with the Display option ELAPSED TIME is used as a prompt in the Web Application, it will only be passed as a string in the time format with colons instead of the number of seconds. Therefore, the ELAPSED TIME prompt may not work as expected in the Web Application.

  • When a field with the Display option TIMESTAMP is used as a prompt in the Web Application, it will only be passed as a string in ISO 8601 format instead of the Windows Client format. Therefore, the TIMESTAMP prompt may not work as expected in the Web Application.

  • Advance packaging where prompts are used to specify field and record names are not supported.

  • Advance packaging where prompts are used to substitute an entire where clause is not supported.

Provide feedback on this article