Inherited tables and business rules, events and notifications.

[NeilOliver]

Hi,

I'm having a litt trouble with notifications being fired from business rules and events.
I have a table inherited from the incident table, which when the business rule incident events (running from incident table) and the new business rule CCID incident events (running from inherited table) runs it forces the events from both tables to notify so essentially the caller with ticket logged against them in the form running from the inherited table recieves both sets of notifications.

Has any one ever experienced this with inherited tables and is there any way to force a stop in the script on the business rule so it does not go on to fire the next business rule. For reference the business rule orders are equal, I've tried to amend the inherited table business rule to a lower number so that it fires first.

BTW, I'm fairly new to this role as admin so I apologise if my description is rubbish/wrong or confusing.....

Cheers

Neil.

[ssears]

You should be able to use different conditions on your notifications. (Something unique from each table perhaps?)

I extended our Incident table as well but use the base table for all events for the notifications and use conditions to determine which email to send.

Shawn

[NeilOliver]

Thanks Shawn, We have set a filter on one business rule for the time being and I'll put in a more permanent fix once I figure the best way.

[CapaJC]

Adding the following condition to the "incident events" Condition should do what you want. Then it won't run for your custom extension table:

current.getRecordClassName() == "incident"

[NeilOliver]

Many thanks for this. It's resolved our issue perfectly.