Internet Explorer Settings
Default Browser
If you are using a URL to pop a Script, you should ensure that Internet Explorer is your default browser. This is set in Start --> Control Panel --> Programs --> Set Default Programs.
Toolbars
Some add-ons and toolbars can also interfere with the application, notably the Google Toolbar, which should be disabled or uninstalled. This can be set in Internet Explorer --> Settings --> Manage Add-ons.
|
!
|
Remove Internet Explorer Toolbar Add-ins
|
Internet Explorer Settings
1. Go to Settings--> Internet Options --> General Tab
Browsing History --> Settings - Select "Check for newer versions of stored pages" choose "Every time I visit the webpage." and click OK.
2. Go to Settings--> Internet Options --> Security Tab
Trusted Sites --> Sites Button - Add your CallScripter domain to the list, e.g., http://myCallScripterServer or https://myCallScripterServer. If you do not force https, you should add both.
|
!
|
Add your CallScripter website to your trusted sites and set security levels for the trusted sites zone
|
Security level for this zone - Custom Level -
Under the sub-heading ActiveX controls and plugins, enable the following:
- Initialize and script ActiveX controls not marked as safe for scripting (Only needed on CS versions 4.5.40 and below, or when using the Alerter or Legacy Agent Desktop in all versions).
- Script ActiveX controls marked safe for scripting
Under the sub-heading "Miscellaneous"
- Enable "Access data sources across domains"
If using windows authentication to log in to CallScripter:
- Under the sub-heading "User Authentication"- Enable "Automatic logon with current user name and password"
In order to ensure a windows user can then login to the CallScripter application CallScripter expects that the username set up in the application is the same as that of the windows user - assuming that the windows user is a member of the appropriate AD Group. (usually CallScripter Users)
Click OK
3. Go to Settings--> Internet Options --> Privacy Tab
Turn off the popup blocker or add the CallScripter Domain to the exceptions list.
4. Go to Settings --> Compatibility View
CallScripter runs in compatibility view to allow for differences in the way different versions of Internet Explorer display the application. So you will need to add the CallScripter website domain to your Compatibility View list (default IE7 mode).
Type your CallScripter domain in to the top text box, e.g., http://myCallScripterServer or https://myCallScripterServer. If you do not force https, you should add both.
Click Add.
Your website will now appear in the list below the Add button. You will need to repeat the process for each CallScripter domain
5. Auto Complete
The Auto Complete feature is set to 'Enabled' for Forms in Internet Explorer Versions 11 and later. This circumvents the data writing procedure, so we recommend this feature is turned off. This feature can be found under Internet Options --> Content --> Auto Complete --> Settings --> Untick Forms.
6. ActiveX Filtering
CallScripter requires that ActiveX Filtering is disabled on its web site within Internet Explorer. This can be set by loading the CallScripter website and under "Tools" and unticking the "AcitveX Filtering" option.
7. Close all Internet Explorer Windows
A number of these settings only apply when Internet Explorer is opened. So all Internet Explorer windows must be closed after applying the settings, prior to CallScripter's use.
Setting Explanations
CallScripter does not require Internet Explorer caching to be disabled, however we do require that every time a web page is visited that a new version is checked for. This is to ensure that Internet Explorer always gets the latest script page and doesn't try to use any previously viewed ones. The setting is to “Check for newer versions of stored pages” “Every time I visit the webpage”.
This ensures that IE checks with the web server for each page requested to confirm if there is a newer version. If there is not a newer version then the cached page copy is used, however if a newer version is available this is downloaded from the web server and shown on screen.
Without this setting IE will sometimes fail to correctly identify a page as being dynamically generated and so only checks the page hasn’t reached its expiry time. This can lead to cases where old page content is shown to the user.
This setting does create a degree of additional network and processing load as last modified dates have to be checked, however the IE cache does still operate in its usual fashion for content which has the same last modified dates.
