You mentioned that open events are getting propagated to AO as expected. What does that rule look like?
Thanks Smith for a quick response.
We have configured below rule.
propagate modify_event_to_AO : EVENT ($EV)
where [ $EV.mc_priority == PRIORITY_1 ]
The rule below looks to be the same as the link you provided previously. One thing to note: Once an event has been propagated to a destination, it cannot be propagated to the same destination (i.e. when slots change).
The same rule is propagating open events.
How can we send update events(slot change) as well to AO(same destination). There should be some way to do that because in same way ibrsd gateway receives update( msg/severity/msg/priority) events.
I believe status changes to events, e.g. going from OPEN to CLOSED should be propagated, as long as the cell or gateway is configured to propagate modifications to the status slot. The goal is not to propagate the event twice, but to propagate changes to slots.
I don't see any obvious reason why this is not working for Sarita. I suggest opening a case with BMC Customer Support if that has not yet been done.
Yes. Maybe I misunderstood what he was expecting. Slot synchronization is controlled by the mcell.propagate (B for backward, F for forward, and BF for both).
check this out while you figure out how to get the events propagated:
I forward all events from the BAO cell and create a pseudo slot, to identify if the event was sent before.
The pseudo slot contains a value, it tells the workflow to ignore.
You get all the events and status and then let the workflow act according to your requirements.
Let me know if that helps.