How to create devices
Configuring a script execution
Each UserView device contains a script with the sequence of steps created using the EveryStep Scripting Tool. You can create a new script, import a script into EveryStep Recorder from an existing device or upload it from a local machine.
Once the UserView script has been created and saved, you can configure the script execution settings on the Script tab.
The field displays the script that was recorded using EveryStep Recorder. To edit the script, click the Edit Script button, and modify the script with EveryStep Recorder. See also: Editing a UserView Script.
This field displays the browser type selected in the script, device type, and recording resolution.
Enter the time in seconds you expect your script should be completed in case you would like to receive an error if this threshold is exceeded.
There are several default system timeouts:
|Navigation timeout||120 seconds||By default, the system will wait for 120 seconds to complete navigation to a web page. If navigation isn’t completed in 120 seconds the action is aborted and error is generated.||The script execution will continue.|
|User Action timeout||50 second||The system will wait for 50 seconds to complete a user action (click, select, etc.). If the user action isn’t completed in 50 seconds the action is aborted and error is generated.||The script execution will continue.|
|Script Execution timeout||15 minutes||By default, the system will wait for script execution result fro 15 minutes. If the script execution is not finished in 15 minutes it will be aborted.||Script execution is fully aborted either on a successful run or in case of reaching the timeout.|
If you want to see how a web page performs for a frequent visitor, or someone who already has elements from the page cached, you can turn on the return visitor flag on the task edit screen.
Simulate a Return Visitor immediately revisits the web page a second time and only records the results of the second visit. Results may differ from a first visit (which always starts with an empty cache) based upon how the browser handles certain items, such as the expiry of elements on the page.
Record Video on Each Run will record a video capture for every single monitoring session. If this option is not turned on, the task will only record a video on the first session of a day that errors or on the first error detected from a location in a given error period.
In some cases, a monitoring error may affect the execution of subsequent monitoring steps and cause a significant delay in alerting. To stop script execution on the first monitoring error, select Yes.
For example, a monitoring error received on the client login step execution leads to failures on the subsequent monitoring steps. In cases where there are a significant number of the monitoring steps in the script, it will take some time for Dotcom-Monitor to finish the script execution and send an alert. To receive alerts faster, it’s recommended to activate the Abort Script option.
If you do not need to abort the script on minor network errors, add the elements that return errors to the ignore list.
The DNS Options feature allows users to choose how domain name server (DNS) requests are conducted during a monitoring task.
To specify the mode of resolving hostnames, in the DNS Resolve Mode section, select one of the available modes. For more details on the feature configuration, see DNS Mode Options.
The Custom DNS Hosts section contains the mappings of IP addresses to hostnames.
To specify the mapping, enter the IP address and the host name in the corresponding fields.
See also: DNS Mode Options.