Setting Alert Type Properties
The Properties tab enables you to specify the alert type name and description, and associate it with Task ManagerTask Manager orSupplemental Data Manager object, such as a task or schedule. An individual alert can be associated with multiple objects.
You can place restrictions on the relationship between the alert and its associated object. Not all restrictions can be applied to all objects.
Table 24-22 Alert Restrictions
Restriction | Description | Example |
---|---|---|
None |
No restrictions on the status of the object and the status of the alert |
A user raises a ‘slow performance’ alert while working on a reporting task. While this affects how long the task takes, it does not prevent the task from completing normally. Even if the task completes, the user still wants the alert open until the performance issue is resolved. |
Prevent Workflow |
Workflow on the object cannot proceed forward (no submits, approvals, and so on) until the alert is closed. This does not prevent claims or rejections (workflow moving backward). It also does not prevent an Administrator or Owner from forcing the workflow forward. |
A user raises an alert that the reporting system is down. This will prevent any work on reporting tasks until the alert is resolved. Preventing workflow includes preventing status changes from Pending to Open and Open to Closed. |
Prevent Close |
The object cannot be moved into a closed state until the alert is closed. However, intermediate workflow may proceed. This does not prevent an Administator or Owner from closing or ‘force closing’. |
A user raises an alert that some comparison data is missing for a reporting task. While this does not prevent the report from being created and going through initial approvals, the report should not be fully signed off until it can be compared to the missing data. |
An object may have multiple alerts with different restrictions. If this is the case, the following rules will apply in order of precedent:
-
If any open alert associated with the object has a Prevent Workflow restriction, Prevent Workflow will stop the object's (for example, a Task) workflow until the alert is closed.
-
If any open alert associated with the object has a Prevent Close restriction, then the object cannot be closed until the alert(s) is closed.
In addition, an alert may be associated with multiple objects. If it has more than one Prevent Close restriction to different objects, the alert will only be closed when the last object is closed.
To set alert type properties: