cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

FRACAS, Incident Count Alert

FRACAS, Incident Count Alert

Make all fields of the System Tree Items table available for display in the incident count alert email. The pertaining system tree item is parent to the incidents triggering the incident count alert.

Make the "System Name" field of the FRACAS Incidents table available for display in the incident count alert email. The "System Name" field of the FRACAS Incidents table is identical to the incidents triggering the incident count alert.

Incident count alerts are triggered if a number of incidents per system tree item, meeting some matching criteria, has been reached.

The data inserted into the corresponding email to the incident count alert is based on the system tree item which is parent to the incidents.

It is possible to insert into the triggered email the field "System Tree Item" of the FRACAS Incidents table, in fact some data characterising the parent system tree item to the incidents.

The field "System Tree Item" of the FRACAS Incidents table is the primary field of the System Tree Items table.

Why isn't it possible to add to the triggered email other details of the parent system tree item like the fields Name, Description or Part Number of the System Tree Items table?

The outcome of these fields is also unique, and there is no ambiguity, as they characterise the System tree parent to the incidents.

2 Comments
Newbie

Thanks Mihaela.  We appreciate the suggestion. 

As you say, the FRACAS Alerts system includes many classes of Alerts, including an Incident Count Alert.  This Incident Count alert triggers when  the number of Incidents that match stated criteria exceed a threshold.  It may be number of Incidents against any System Tree Item, any Configuration or any System Tree Item and Configuration combination.  A representative alert is: "notify me when any System Tree Item has 3 or more Incidents that have Severity = Critical in the last 30 days". 

Along with the conditions, the user can create a configurable email or leverage one of the out of the box templates.  The email can be configured to contain fields from the affected incidents so that the user is notified not just that there is an issue, but also where the issue occurred.

There are many classes of Alerts supported, this being one of them.

Also as you stated, this class of Alert only permits the System Tree Item and Configuration fields from the Incident Table to be included in the message, as the Alert is auto-indexing the Incidents against those fields.  Data contained in the System Tree Item field is configurable, and may be the Identifier, Name, Description, Part Number, LCN, etc.  This should be enough to notify the user of which item is being identified.

Finally, and unfortunately, it is not currently possible to add System Tree fields into this Alert email for this class of Alert.  We're investigating the level of effort to provide the ability to include System Tree fields in the alert email, and based on the level of effort and customer interest will prioritize it in our roadmap.

If we have an update on this, I'll let you know.  And thanks again for the input!

Community Manager
Status changed to: Archived