ExtraView 7 is certified to support the following browsers.
These browsers are supported on the following platforms (where available) – Windows XP, Windows Vista, Windows Server platforms 2005 and greater, Apple Macintosh, Linux, Solaris and UNIX.
If you use Microsoft Excel to view ExtraView reports, you may need to ensure that the character set being sent from ExtraView to Excel is correct. If your data in ExtraView contains double-byte characters (this normally means Asian languages) then you should set your Microsoft Office character set to windows-1250 within your personal options.
The resolution of the monitor or screen on which users should use ExtraView should be a minimum of 1024 x 768 pixels. While ExtraView will work at lower resolutions than this, users may have to scroll up, down and sideways more than they would like. The administrator can make decisions in the design phase that will affect this. For example, the settings in the style sheets that control the small, medium and large font sizes can be tailored, as can the number of columns and rows that appear on screen layouts.
The recommendation is that administrators should design their layouts to fit within a resolution of 1280 x 1024 pixels. This covers the widest majority of monitors that users own.
Most browsers have cookies turned on as a default setting and this is what ExtraView expects. If they are not turned on, ExtraView will warn the user that cookies are not turned on, and will not function until they are turned on. ExtraView only uses session cookies, and no cookie or other information is ever stored within the client browser after the ExtraView session is complete.
JavaScript must be turned on within the client browser.
Users should never use the browser’s back button within ExtraView. They should only navigate by the buttons that are displayed on ExtraView’s menus.
The reason is that ExtraView must maintain integrity of its information at all times. For example, if you press the button on ExtraView’s Add Issue screen to add a new record, then pressed the back button and pressed the add button again, you will have two records inserted. Similar problems occur if the user attempts to go back to a record he has edited, or to go back to a screen that was refreshed from the server during adding or editing an issue.
Similar to the Back button, the Refresh button within your browser should not be used. At the times that a Refresh is allowable, ExtraView will offer a Refresh button in its menu bar.
ExtraView must work consistently with a single character set, in order that information entered within different browsers across an organization will be compatible, and can be stored on and retrieved from the ExtraView server in a consistent manner. This is less of a problem with languages based on the Roman alphabetic, but is an essential ingredient of correctly configuring a system where users use double-byte languages such as Japanese and Chinese.
There is a behavior setting (see the following section) named HTTP_CHARSET that defines the character encoding for input from all browsers, for all users of the ExtraView instance. By default this is set to UTF-8, a character set that is universal and supports all languages. The recommendation is to have all users set their local browser character set to UTF-8. If this is to be changed, then it must be changed on the server and in every client browser.
Note: It is strongly recommended that HTTP_CHARSET is set to a value of UTF-8, and that all users only set their browser character set to UTF-8, so that characters will be displayed correctly and consistently.
