Configure actions

Actions are the part of a rule that define what the policy should do if it detects an event that matches (or does not match) the rule's condition. The action can consist of one or more of the following:

Send a message to the active message browser
This is the most common action. A message notifies the operator that an event has occurred, can supply the operator with instructions for responding to the event and can provide a link to a command that the operator can run. You can also configure messages acknowledge or suppress duplicates.
Send a message to the acknowledged messages browser
You may want to send a message to the management server for tracking reasons, but don't need to have the user take any action or acknowledge the message. In this case, you can send the message directly to the acknowledged messages browser.
Automatically run a command
Certain events could represent conditions that can always be helped by running a certain command. If you know that a command should always be run in response to an event, you can configure an automatic command.
Nothing
In some circumstances, you may want a rule to stop the policy from evaluating the event (to improve performance) without providing the operator with any notification.

NOTE:
The maximum supported string length for an operator-initiated or automatic command is 2048 characters. Be particularly careful to stay within this limit when using variables substitution within the action call.