• of the robot,
• of the counter-robot,
• of the monitor.

1. In the menu, go to the "Settings" group, select "Configure" and then "Parameters of the monitoring robot".
2. A window shows the characteristics of the robot:
   • Name, computer, access directory.
   • Alert options. These options can be configured for:
     • alert via WDBal,
     • alert via Email,
     • alert via third-party program,
     You can configure the reports sent via Email or WDBal.

Alert by WDBal

• In network share mode: directory of the data files.
• In HFSQL Client/Server mode: server used, port and database, as well as user and password.

Alert by email

• SMTP server and port.
• User and associated password to use the SMTP server.
• Security used.

Using a specific program

• configure the error report to be sent to a specific program. This third-party program will handle the alert messages.
  To use this mode of alert message, specify the path of the desired executable. This executable must be accessible from the setup computer of the robot.
• Versions 26 and later
  specify a Webhook. The webhook will be called after each test execution, by passing a JSON file as parameter.
  To use a webhook, just specify the URL of the webhook to call.
  New in version 26
  specify a Webhook. The webhook will be called after each test execution, by passing a JSON file as parameter.
  To use a webhook, just specify the URL of the webhook to call.
  specify a Webhook. The webhook will be called after each test execution, by passing a JSON file as parameter.
  To use a webhook, just specify the URL of the webhook to call.

• %1 = Number identifying the test
• %2 = Name of the test
• %3 = Name of the test category
• %4 = Priority of the test
• %5 = Syntax of the test (associated parameters)
• %6 = Solution proposed for the test
• %7 = Date of the error
• %8 = Time of the error
• %9 = Error message specified in the form of the test
• %10 = Error message returned by the robot

Versions 26 and later
Webhook call
The call will be made after each executed test, passing a JSON file as parameter.

The JSON file has the following format:

{
 "RobotName": "Robot name",
 "ControlName": "Name of the check",
 "ControlCategory": "Category name",
 "Severity": "Error severity level"
 "ResponsibleList": "Supervisor",
 "FirstError": "DateTime of the first error",
 "ErrorMessage": "Error message",
 "IsError": 0/1
 "CustomError": "Custom message"
}

The elements in the JSON file are:

• RobotName: name of the monitoring robot (useful if you have multiple robots in your organization and if you want to direct them all to the same webhook).
• ControlName: name (caption) of the check.
• ControlCategory: name (caption) of the check category.
• Severity: level of severity of the check. In version 26, this parameter is always set to "Error".
• ResponsibleList: list of users who receive alerts about this check.
• FirstError: date and time of the first reported error. This member can be used to determine how much time has passed since an error was detected in a given check.
• IsError: boolean indicating if the check contains errors.
• ErrorMessage: error message of the check.
• CustomError: additional error message (specified in the check settings, from the robot monitor).

Remark: If you want to make a webhook call in WEBDEV:

1. Create a WEBDEV project with a blank Active WEBDEV Page.
2. In the Active WEBDEV Page:
   • Declare the export structure:
     
     // Export structure
     STWebHookExport is Structure
     RobotName is string
     ControlName is string
     ControlCategory is string
     Severity is string
     ResponsibleList is string
     FirstError is DateTime
     ErrorMessage is string
     IsError is boolean
     CustomError is string
     END
      
     garrWebhookInfo is array of STWebHookExport
     
   • Retrieve and deserialize data before using it:
     
     bufPOSTData is Buffer = PageParameter(paramBuffer)
     Deserialize(garrWebhookInfo,bufPOSTInfo,psdJSON)
     

Related Examples:

Training (WEBDEV): WW_Status_List [ + ]

New in version 26
Webhook call
The call will be made after each executed test, passing a JSON file as parameter.

The JSON file has the following format:

{
 "RobotName": "Robot name",
 "ControlName": "Name of the check",
 "ControlCategory": "Category name",
 "Severity": "Error severity level"
 "ResponsibleList": "Supervisor",
 "FirstError": "DateTime of the first error",
 "ErrorMessage": "Error message",
 "IsError": 0/1
 "CustomError": "Custom message"
}

The elements in the JSON file are:

• RobotName: name of the monitoring robot (useful if you have multiple robots in your organization and if you want to direct them all to the same webhook).
• ControlName: name (caption) of the check.
• ControlCategory: name (caption) of the check category.
• Severity: level of severity of the check. In version 26, this parameter is always set to "Error".
• ResponsibleList: list of users who receive alerts about this check.
• FirstError: date and time of the first reported error. This member can be used to determine how much time has passed since an error was detected in a given check.
• IsError: boolean indicating if the check contains errors.
• ErrorMessage: error message of the check.
• CustomError: additional error message (specified in the check settings, from the robot monitor).

Remark: If you want to make a webhook call in WEBDEV:

1. Create a WEBDEV project with a blank Active WEBDEV Page.
2. In the Active WEBDEV Page:
   • Declare the export structure:
     
     // Export structure
     STWebHookExport is Structure
     RobotName is string
     ControlName is string
     ControlCategory is string
     Severity is string
     ResponsibleList is string
     FirstError is DateTime
     ErrorMessage is string
     IsError is boolean
     CustomError is string
     END
      
     garrWebhookInfo is array of STWebHookExport
     
   • Retrieve and deserialize data before using it:
     
     bufPOSTData is Buffer = PageParameter(paramBuffer)
     Deserialize(garrWebhookInfo,bufPOSTInfo,psdJSON)
     

Related Examples:

Training (WEBDEV): WW_Status_List [ + ]

Webhook call
The call will be made after each executed test, passing a JSON file as parameter.

The JSON file has the following format:

{
 "RobotName": "Robot name",
 "ControlName": "Name of the check",
 "ControlCategory": "Category name",
 "Severity": "Error severity level"
 "ResponsibleList": "Supervisor",
 "FirstError": "DateTime of the first error",
 "ErrorMessage": "Error message",
 "IsError": 0/1
 "CustomError": "Custom message"
}

The elements in the JSON file are:

• RobotName: name of the monitoring robot (useful if you have multiple robots in your organization and if you want to direct them all to the same webhook).
• ControlName: name (caption) of the check.
• ControlCategory: name (caption) of the check category.
• Severity: level of severity of the check. In version 26, this parameter is always set to "Error".
• ResponsibleList: list of users who receive alerts about this check.
• FirstError: date and time of the first reported error. This member can be used to determine how much time has passed since an error was detected in a given check.
• IsError: boolean indicating if the check contains errors.
• ErrorMessage: error message of the check.
• CustomError: additional error message (specified in the check settings, from the robot monitor).

Remark: If you want to make a webhook call in WEBDEV:

1. Create a WEBDEV project with a blank Active WEBDEV Page.
2. In the Active WEBDEV Page:
   • Declare the export structure:
     
     // Export structure
     STWebHookExport is Structure
     RobotName is string
     ControlName is string
     ControlCategory is string
     Severity is string
     ResponsibleList is string
     FirstError is DateTime
     ErrorMessage is string
     IsError is boolean
     CustomError is string
     END
      
     garrWebhookInfo is array of STWebHookExport
     
   • Retrieve and deserialize data before using it:
     
     bufPOSTData is Buffer = PageParameter(paramBuffer)
     Deserialize(garrWebhookInfo,bufPOSTInfo,psdJSON)
     

Related Examples:

Training (WEBDEV): WW_Status_List [ + ]

Configuring the status report

• The "Object of email sent" section is used to build the title of the message. Macros are used to get specific information (name of the robot, number of checks in error, ...).
• Versions 17 and later
  The "Alert mode" section is used to choose the alert mode:

  • "Continuous alert" mode (by default):
    If a given check encounters errors multiple times in a row (for example, if the server does not respond for several minutes), the robot will systematically send an alert for each error.
  • "Fail/Resume" mode
    If a given check is in error several times in a row (if the server does not respond during several minutes for example), the robot will perform the following operations:
    1. The robot will send an alert when the first error is detected.
    2. The robot will send intermediate alerts every xx minutes. The timeout between each send operation can be configured.
    You also have the ability to send no intermediate message.
    3. The robot will send a message when the check is no longer is error (if the server is restarted for example).
    Remarks:
    • The "Fail/Resume" mode applies to all the checks (it cannot be specified for a specific check).
    • If this mode is enabled and if the robot monitors sensitive elements, we advise you to send intermediate messages.
    • Example of progress:
      

      Time	Status of the check	Continuous Alert mode	Fail/Resume mode
      Time T	Check with errors	Alert send	Alert send
      Time T+1	Check with errors	Alert send	No alert send
      Time T+2	Check with errors	Alert send	No alert send
      Time T+3	Check with errors	Alert send	No alert send
      Time T+4	Check with errors	Alert send	No alert send
      Time T+5	Check correct	No alert send	Alert send

  New in version 17
  The "Alert mode" section is used to choose the alert mode:

  • "Continuous alert" mode (by default):
    If a given check encounters errors multiple times in a row (for example, if the server does not respond for several minutes), the robot will systematically send an alert for each error.
  • "Fail/Resume" mode
    If a given check is in error several times in a row (if the server does not respond during several minutes for example), the robot will perform the following operations:
    1. The robot will send an alert when the first error is detected.
    2. The robot will send intermediate alerts every xx minutes. The timeout between each send operation can be configured.
    You also have the ability to send no intermediate message.
    3. The robot will send a message when the check is no longer is error (if the server is restarted for example).
    Remarks:
    • The "Fail/Resume" mode applies to all the checks (it cannot be specified for a specific check).
    • If this mode is enabled and if the robot monitors sensitive elements, we advise you to send intermediate messages.
    • Example of progress:
      

      Time	Status of the check	Continuous Alert mode	Fail/Resume mode
      Time T	Check with errors	Alert send	Alert send
      Time T+1	Check with errors	Alert send	No alert send
      Time T+2	Check with errors	Alert send	No alert send
      Time T+3	Check with errors	Alert send	No alert send
      Time T+4	Check with errors	Alert send	No alert send
      Time T+5	Check correct	No alert send	Alert send

  The "Alert mode" section is used to choose the alert mode:
  • "Continuous alert" mode (by default):
    If a given check encounters errors multiple times in a row (for example, if the server does not respond for several minutes), the robot will systematically send an alert for each error.
  • "Fail/Resume" mode
    If a given check is in error several times in a row (if the server does not respond during several minutes for example), the robot will perform the following operations:
    1. The robot will send an alert when the first error is detected.
    2. The robot will send intermediate alerts every xx minutes. The timeout between each send operation can be configured.
    You also have the ability to send no intermediate message.
    3. The robot will send a message when the check is no longer is error (if the server is restarted for example).
    Remarks:
    • The "Fail/Resume" mode applies to all the checks (it cannot be specified for a specific check).
    • If this mode is enabled and if the robot monitors sensitive elements, we advise you to send intermediate messages.
    • Example of progress:
      

      Time	Status of the check	Continuous Alert mode	Fail/Resume mode
      Time T	Check with errors	Alert send	Alert send
      Time T+1	Check with errors	Alert send	No alert send
      Time T+2	Check with errors	Alert send	No alert send
      Time T+3	Check with errors	Alert send	No alert send
      Time T+4	Check with errors	Alert send	No alert send
      Time T+5	Check correct	No alert send	Alert send