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

Responses Overview

Responses Overview

Rules respond to an event condition by invoking a response that you create and then reference in that rule.
For example, you can reference the following types of responses in a rule:
  • Email Message. Generic email with default values for the to, from, subject, and body fields.
  • RTAM Alert. Generic Real-Time Alert Manager (RTAM) alert with default values for the to, subject, channels, and priority fields.
  • IM Message. Generic IM with default values for the screen name and message text fields.
After you create a responder service, you must create a specific response and associate the response with the responder service. Deploying a responder service, automatically deploys the associated response.
When a rule invokes that response, the response implements the service using its specific field values. Additionally, you can override the configuration of the responses by specifying new values in the DRQL of an advanced rule or template. It is not required to have responses configuration in DRQL.
If the response name contains a space, place the response within quotation marks when referencing the response in a rule. If the response name does not contain a space, you do not need the quotation marks. When you reference response parameters in a rule, place the parameter value within quotation marks.
The parameter names in the RulePoint response user interface do not match the parameter names that you define within DRQL syntax.

0 COMMENTS

We’d like to hear from you!