Table of Contents

Search

  1. Preface
  2. RulePoint
  3. RulePoint Concepts
  4. Using RulePoint
  5. RulePoint Objects
  6. Working with Topics
  7. Working with Connections
  8. Working with Sources
  9. Working with Responders
  10. Working with Responses
  11. Working with Watchlists
  12. Working with Analytics
  13. DRQL
  14. Working with Rules
  15. Working with Alerts
  16. Setting Access Controls
  17. Troubleshooting RulePoint Issues
  18. Connecting to an Ultra Messaging Application
  19. Creating an Ultra Messaging JMS Source

User Guide

User Guide

Wizard Rule

Wizard Rule

The Rule Wizard provides an easy-to-use interface for creating a rule, including selecting topics, conditions, and responses.
Rules created using the Rule Wizard cannot be edited in Advanced Mode and vice versa. However, a wizard rule can be converted to an advanced rule or template.
Wizard rules do not support nested analytics. An example of a nested analytic is where you use the sum() analytic inside the geoInsideArea() analytic.
To use nested analytics, you can select one of the following options:
  • Wizard mode. Create two conditions. The first condition performs the inner analytic (for example, sum()) and assigns to a temporary variable using the AS clause. The second condition is the outer analytic that uses the AS temp variable name.
  • Advanced Mode. Use this mode if the outer analytic itself supports an inner analytic.
The Rule Wizard consists of the following steps that correspond to the WHEN, WITH, and THEN statements in DRQL:
  1. Select the event topics, how many events to evaluate for each topic, and a time frame in which to evaluate all of the events for the topics you select.
  2. Define the conditions for your rule. You can define one, multiple, or no conditions.
  3. Define your responses. At least one active response must be available in RulePoint before using the Rule Wizard.
  4. Select if you want parallel processing for the rule. Parallel processing is enabled by default.
  5. Specify execution settings.
The comparison of string literals and topic property string values are case sensitive. For example, when evaluating a rule, "xyz" does not equal "XYZ."

0 COMMENTS

We’d like to hear from you!