New/Properties: Transaction : General

From WebWatchBotWiki
(Redirected from Transactions Adding General)
Jump to: navigation, search
 Share 

Description

Creating a new watch item or viewing an existing watch item's properties will open the Transaction properties window:

Fields and Buttons

Transaction Name

  • The name of the Transaction.
  • If no name is entered, the name automatically used is "Transaction".
  • If the name entered already exists as a Transaction or Watch Item, the name will have a number appended to the end. For example: If the Transaction "Checkout" is already used, and a second Transaction named "Checkout" is created, the second watch item's name will be changed to "Checkout(2)". If a third watch item named "Checkout" is created, it's name will be changed to "Checkout(3)". And so on.

Frequency - How Often to Monitor

  • Specifies the frequency which the Transaction should be checked
  • A Transaction can be checked from once a second to once every 8760 hours (once a year).
  • Specifying an interval of less than 15 seconds will impact performance of this application and the resources being monitored.

Response Time Maximum in ms (milliseconds)

The maximum amount of time in milliseconds (1/1000 of a second) that a Transaction must respond or the Transaction will fail with a timeout.

Number of Milliseconds to pause between running each Watch Item

Specifies the number of milliseconds (1/1000 of a second) that a step should pause after completion before continuing to the next step.

Active (Unchecking this box will SUSPEND this entire Transaction - Individual Watch Items may still be active)

Checking this check box will allow the watch item to run for the specified frequency, unless WebWatchBot is in Maintenance Mode.

Continue After A Step Fails

When checked, the Transaction will continue to run the next step even if a step fails. When unchecked, the Transaction will stop running if a step fails for any reason.

Persist Form Data

Checking this option will cause all steps after the first to use form data from the previous step. For example if step one has a form variable with a name that matches a form variable on step two, the value from step one will be persisted on step two.

Enhancement in v6.1: New settings window allows for the input of form variable names. When the Transaction is run, the specified form variables value will be saved from the previous step and then when that form variable is found in the source of the next transaction step, it's value will be set to the previous page's value.

Example:
Page 1: <input type="textbox" name="username" value="Fred">
(value of "Fred" saved)
Page 2: <input type="hidden" name="username" value="">
(WebWatchBot sets the value of "username" which is blank, to "Fred")

transaction_properties_persist_form_data.gif

Session ID in URL

Use this option if dynamically generated Session IDs are located in the URL, then click "Session ID Settings" button below.

Token Used

Use this option if tokens are used within the page source of a web application and need to be persisted from page to page.
Tokens are often used with the Apache web server to manage "state" of a user and to prevent duplicate form submission. When a user logs into a web application, a token (series of numbers and letters) are assigned to a user and then passed from one page to another in order to keep track of who the user is.
In order to use this feature with a non-Apache web server, you must identify the first page that a "token" is assigned in a form, typically in the form of:

<input type="hidden" name="someToken" value="LSIKDF98S9DF9D8FKLJWOEIUR">

The token must then be persisted or passed from one page to another in the query string (part of the URL). This feature will not work if the token is only passed via form variables.

Assign Icon

Select one icon to represent the Transaction in the My Watch and Watch Explorer window panes.

Screenshots

WebWatchBot Manager

transaction_properties_general.gif

WebWatchBot Online

general.jpg