Use the
Threshold-Based Automation Process window (accessed
from within the Automation Process Editor) to create a Threshold-Based
Automation Process. Define when and how an Action is run when a threshold is
breached.
To create a Threshold-Based Automation
Process:
- Open the Automation Process Editor.
- Select
New, and then select
Threshold-Based Process.
- Define general properties:
- Provide a name and description. You can search these
properties in
CSM
Item Managers.
- Select the type of Business Object against which this process
will operate.
- Select a priority level, which provides a hint to the
Business Process Server as to the importance of the Automation Process. This
allows the system to attempt to execute higher priority processes before normal
or low priority processes.
- Define the value that the Automation Process should monitor:
- Select the
Value
page.
The
Value page opens below the general
properties.
- Number of Records: Select this option
to monitor the number of records that meet the defined criteria.
- Function: Select this option to apply
a mathematical function against a field (example: Average, total) if there is a
numeric field on the records being evaluated.
- Duration Function: Select this option
to apply a mathematical function against the range of time between two
time-based fields (example: Determining the average amount of time that
Incidents take to resolve).
If you select a duration function, you must specify the fields
that define the start/end date times and the unit(s) to use (example: Hours,
days, months).
- Define criteria for the records included in the calculation:
- Select the
Criteria page.
The
Criteria page opens below the general
properties.
- Search Criteria: Select the
ellipsis to select an existing saved search or select
Search to define a custom query to limit the records
considered.
- Open Incidents Only: Select the check
box to only include open Incidents in the results.
- Define one or more thresholds:
- Select the
Thresholds
page, and then define threshold properties:
Use the
Check threshold values every option to set
how often threshold values should be checked. Checking begins when Automation
Process is enabled or when an Automation Process Blueprint is published.
Every time value is checked (if the
threshold is crossed): |
Select this option to execute the action if the check is
completed every hour and the value is above the threshold. |
When the threshold is first
crossed: |
Select this option to execute the
Action the first time the value is above the threshold, but not execute the
Action again unless the
at least operator is specified. |
Each time a threshold is
crossed: |
Select this option to execute the
Action the first time the value is above the threshold, but not execute the
Action again until the value falls below the threshold at least once and then
goes above the value again. |
At least: |
Specify this operator for the rules to be reconsidered. If the option is set to
When the Threshold is First Crossed and
the threshold is crossed, the Action will be executed a single time. If you
specify that at least one day must pass between operations, then a day later
the Action will be executed again if the threshold is crossed. This option is
only available if you select the Automation Process to operate every time a
value is checked or each time a threshold is crossed.
|
Create a threshold
|
Select
Add to add a threshold to the list.
|
Edit a
threshold
|
Use the controls underneath the
threshold list to customize the threshold. |
Remove a
threshold
|
Select
Remove to permanently delete a threshold.
|
Reorder the
threshold
|
Select
Reorder to organize the threshold list.
This option sorts all of the thresholds based on the threshold values, but does
not affect the Threshold-Based Automation Process functionality.
|
Above/Below
threshold
|
Specify whether the threshold should
be considered breached when the value exceeds or falls below the threshold
value.
|
Threshold
value
|
Specify the value against which the
returned result will be compared.
|
Action
|
Select
or define a
One-Step™
Action
to run when the threshold is breached.
Note: The Action must be an unassociated
One-Step Action
(not tied to a particular Business Object). This is necessary because there is
no single record to operate against, just a single resulting value.
|
- Select
Save.
Important: If you are working with Automation Processes
after a
Protected mApp™ Solution
has been applied to your system, note the following:
- If you create or open an Automation Process Blueprint which has
a
Protected mApp Solution
installed, protected processes have shield icons
.
- If you select a content-protected process and right-click, you
cannot delete the process.
- If you edit a content-protected Threshold-Based, or
Simple/Event Automation Process, you must use
Save As to create a copy.
- If you view Automation Processes in a Blueprint or by opening
an Automation .bp file from
CSM Administrator,
they cannot be edited in any way.