The default SA Project template, comes with SOE list where system alarms and states are defaulted to be shown independent of any filter applied.
From what I see this comes form the FUNCTION _AlarmPage_UpdateFilter() being set with "OR StateNumeric = 0".
Request to implement filter function that can filter system alarms and states.
This case has been raised in the Community forum and AVEVA developers has confirmed the issue:
"It looks like the code deliberately include system events regardless of whether filter is applied or not. This might be part of the requirement at the time. Will need to check past requirement to confirm.
In terms of “OFF” state, system events are not alarms which do not have concept of ON / OFF, and the State column just shows the default state."
"The issue was that whenever we filter on non-historic fields, such as Equipment, Category, Priority etc., the system events will disappear from the SOE list. This is due to those fields do not exist in the event journal table in the database. When the historic table is joined with the configuration tables, their values will be NULL and be always filtered out. For example if we just want to filter out priority 3 alarms, i.e. Priority<>3, the system events will be gone too.
The resolution at the time was to always display the system events regardless of filtering is turned on or off to prevent the above issue. The side-effect is that the user won’t be able to filter out the system events if they want to. Perhaps we can provide a way for the user to filter out the system events if needed. One of the ways may be to only include system events if none of the filtered fields are from the event journal table."
Guest
|
Idea business value
It's a bit confusing when you apply filter to hide "OFF" state and it do not remove the System alarms with "OFF" state for instance even though the system events are not alarms, they still hold/show OFF state. |
|
| Idea priority | 4 – Important to my company |
