The following sections only pertain to Browser Checks - you will not be able to specify Returned Value for ZebraTester checks, for example. For components which are editable for every check type, see https://apica-kb.atlassian.net/wiki/spaces/ASMDOCS/pages/2148991311/Editing+Checks#Edit-Check-Components-Common-to-All-Check-Types.
...
Individual files can be deleted from the scenario with the “delete file” button. The scenario can be replaced by a different scenario, or a newer version of the same scenario by uploading a locally stored scenario file. Refer to the article Understanding the Debug Scenarios Page for information on the Debug Scenarios functionality.
...
Disable Automatic Page Breaks
Page breaks are automatically inserted into Browser Check Results by default. The location of these automatically inserted page breaks is determined by the engine which is responsible for running Browser ChecksDisables the insertion of automatic page breaks which are generally inserted when the ASM scenario runs the “open” and any of the “…andWait” commands (e.g. clickAndWait). If automatic insertion of page breaks is disabled in the Browser Behavior section, page breaks can still be entered via the ASM scenario using the insertPageBreak command.
...
Item | Description | Comment |
|---|---|---|
Check Fail Severity | This will be the Severity that the check will be assigned if it fails. This can be used to trigger a different Severity for the check results. | Default is |
High Warning Threshold | Thresholds are used to set custom thresholds for triggering Severity changes of checks. If the returned value from the check passes over High Warning Threshold it will trigger a Severity change of the check Warning (Yellow). | A warning is triggered above this value. |
High Error Threshold | Thresholds are used to set custom thresholds for triggering Severity changes of checks. If the returned value from the check passes over High Error Threshold it will trigger a Severity change of the check Error (Orange). | Error is triggered above this value. |
Low Warning Threshold | Thresholds are used to set custom thresholds for triggering Severity changes of checks. If the returned value from the check drops below Low Warning Threshold it will trigger a Severity change of the check Warning (Yellow). | A warning is triggered below this value. |
Low Error Threshold | Thresholds are used to set custom thresholds for triggering Severity changes of checks. If the returned value from the check drops below Low Error Threshold it will trigger a Severity change of the check Error (Orange). | Error is triggered below this value. |
Severity Mapping | See dedicated “Severity Mapping” section below. | See dedicated “Severity Mapping” section below. |
Preserve Value | Enable this option to preserve the Returned Value for a check run with URL errors that are mapped to I, W, or E (and there is no selenium error). | By default, a check run with URL errors are shown as a failed check run and the Returned Value is not saved or shown in the Check Result message. |
Error Wildcard | Error Status Codes pattern '*' applies to:
| This feature allows a user to configure what the wildcard character applies to when it is used in the “Error Status Codes” field. If a user wishes to “map” the wildcard character to 4** and 5** errors only, they should select “Bad HTTP status only (0, 4*, 5*). |
Target SLA % | Sets a 1st Target SLA in percentage e.g 99.5 or 99. | This is used in certain types of reports. |
Target SLA %(2nd) | Sets a 2nd Target SLA in percentage e.g 99.5 or 99. | This is used in certain types of reports. |
...