Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

DB Rule sending too many notifications

Highlighted
Kumar Microland
Regular Collector

DB Rule sending too many notifications

Hi all,
We are using HPOV SD 4.5(SP10)
My requirement is:

To Send L1 notification after 5 minutes from Created time, L2 notification after 30 min from created time & L3 notification after 1 hr after created time.

My DB rule for Level 3 notificationis :

When incident is created or modified
where NOT (Status equals ResolvedORResolved - Under ObservationORClosed, Schedule the validation of this condition at 1 hour After Registration;Created, Only execute once)
AND Priority equals XYZ-P1
Level 3 Escalation (Send e-mail message) , Send to: XXXXXX Subject:*******
Message:
Thanks and Regards



This rule is sending notifications continuously after 1hr till the exution.

Please suggest me for any modification.

Thankx in advance...
4 REPLIES
Venkatesha_1
Esteemed Contributor

Re: DB Rule sending too many notifications

Hi,

In the DB rule conditions, you need to select one or more field for value change.

That is check the option "Evaluate this rule when this field has been changed" for as many need field.

HTH
Venkatesha
Venkatesha_1
Esteemed Contributor

Re: DB Rule sending too many notifications

Also select the checkbox "Only execute once" based on the requirement
George M. Meneg
Honored Contributor

Re: DB Rule sending too many notifications

"In the DB rule conditions, you need to select one or more field for value change."

No, you don't. Actually this is a cool feature of DB rules that allows to trigger a condition if anything is changed in contrast with UI rules that you must explicitly check a field.

However, if you want to check a particular field for modification, you should follow Venkatesha's advice.
menes fhtagn
Kumar Microland
Regular Collector

Re: DB Rule sending too many notifications

Thank you all for supporting me in resolving the issue
//Add this to "OnDomLoad" event