- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2014 12:15 PM
We have a request item that for some reason triggers an event 3 times when it is submitted. This then causes an email notification to get sent 3 times. The weird part is that this only happens when this one specific item is created. For every other item the event only gets triggered once and the email only gets sent once.
Any ideas?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-29-2014 09:36 PM
Jennifer,
There is no need to remove the current.update() statement from after BR, as this should not be written in Before BR only. For your Issue am sure about that the problem is only with the order of BR as I also faced the same problem in past and when I changed the order as per appropriate manner then it starts working correctly. Please again check with the order of your BRs.
Thanks,
Rajeev Kumar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2014 12:17 PM
Hi Jennifer,
Does that item have a workflow? Or a specific business rule that runs on that item?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2014 12:19 PM
I'd check a couple things to start. First, do you have any Before Update business rules on this table that you created or modified? If so, check if "current.update()" is in the script for the business rule. If it is, remove it. The BR is already doing an update so there's no need to do it twice which is essentially what this is doing. Second, check your workflow for the same thing. If you have any Set Value workflow activities that run current.update(), it's also unnecessary.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2014 12:29 PM
Greetings Jenifer,
If there is any multiple update to the same record from different sources say business rule, workflow script or weight of the notification with similar condition. Once clear with above three points it will not send multiple notifications.
As your example, it is sending only for particular catalog item, verify that catalog item workflow or Explicit business rule running for that catalog item or UI Actions where it might be updating record thrice.
Please mark answer as Helpful/Correct, if it was really helpful
Regards,
Solutioner
Enhance Knowledge NOW@ www.solutioningnow.com
http://www.solutioningnow.com/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2014 12:27 PM
There is no workflow for this item. The execution plan for it has several tasks but they all open at the same time, nothing fancy there. We also do not have a business rule on the item specifically. I checked the business rules on the sc_task table and none of the before rules have current.update().
When an item is opened it sends an email for each child task to the assignment group stating a task is assigned to the group. This is the email sending duplicates.
