TBSM Service state change after event acknowledged

Body

This document explains how to get TBSM to ignore acknowledged events.  In other words, how to get  a service to go GREEN after the event affecting it is acknowledged but remain in the list of events for the service?
These are the steps to set up an example template, rules and service etc.  
Setup a template and a Good, Bad & Marginal rule with a filter like this:

It may not be necessary to have all these elements, but the ones with Severity=Clear have been included for completeness.

Then create Service with this template and create a Severity 5 event to match the Service and see it go RED.

Then acknowledge the event and set RAD_RawInputLastValue=6 and RAD_SeenByTBSM=0 for it.  After that, TBSM will re-read the event and the service will go GREEN, but the event will remain as affecting the service:

In that example, the step to get TBSM to re-read the acknowledged event was done by manually, but you will need to automate this (the setting of RAD_RawInputLastValue=6 and RAD_SeenByTBSM=0) when an event is acknowledged, here are a couple of ways to do it:

1.  Using an OMNIbus trigger, set RAD_RawInputLastValue=6, RAD_SeenByTBSM=0 whenever an event with RAD_FunctionType='Raw' is acknowledged.

2.  Introduce a new OMNIBus field called, for example, RAD_Acknowledged and add this to the restriction filter in TBSM_tbsmomnibuseventreader.props to re-read events where RAD_Acknowledged does not equal Acknowledged.

The first is probably the simplest to implement.