Monitors are transactions that watch for processes or circumstances
that are out of bounds of the constraints the business defines and
then raise alerts.
A business process is made up of a series of transactions that
are modeled in a pipeline. For each of these transactions, there is
the possibility for a failure scenario that you need to be notified
of, for example, a transaction that is doing duplicate order checks
or fraud checks, if one of those transactions fails, you can configure
your system to send an alert/message to a queue for review and to
address the issue. This module allows you to create alerts, group
them in specific queues, assign users to specific groups to monitor
specific queues, and to notify, process, and fix any alert that is
received. Additionally, as part of the monitoring framework, you are
enabled to hold documents from further processing. A document can
be put on hold from further processing until the hold is resolved
either manually or automatically. At times a general business rule
may need to overridden, for example allowing a manager to accept an
expired coupon. As part of this module the validation rule framework
is designed to be used to enable manager overrides. As part of the
validation Framework, the application provides additional out of the
box framework to implement additional business validation. Event management
involves using the alert and queueing mechanisms to respond to alerts
that are detected by your monitors. You can also configure monitors
to alert you when specific defined events have occurred and to track
items. Monitoring rules allow you to control which event is raised
when an alert situation is detected by the monitor. When the issue
is detected, the response you want to happen is configurable, such
as Alert to queue, send mail, and so on.
An alert is a message directed to a user or queue about a transaction
that may need manual intervention or manual review.
A queue is a line or list of items waiting to be processed,
for example, work to be performed or messages to be displayed or transmitted.
Queues can be designed to notify specified users of alerts at configured
levels and times.
A hold is applied to an order to prevent certain modification
types and transactions from processing the order or order line until
the hold is released.