By using this website, you agree to our Terms of Use (click here)
Hello,
Automation notifications settings are not sending notification if system has already sent notification with the same parameters.
For example: We have configured automation notifications on Opportunity object. Let us assume that conditions are the following: if opportunity’s amount is greater than 20, system should send notification to the specific user.
- Opportunity is created with amount 21. System sends notification to the user that object is created with amount more than 20.
- Suppose amount in the opportunity is changed by the user and it is set as 15 (any amount less than 20). In this case notification is not generated as amount is less than 20.
- Suppose that amount is changed again and it is set as 21 (same number that was in the first example). In this case notification should be sent as amount is greater than 20, but it is not. Reason is that previously sent notification was the exactly the same.
- Please consider that, if we would have indicated any other number (greater than 20) notification would have been sent. Only case in which notification is not sent is when the previous notification was exact duplicate of new notification.
Below is given amount flow example for better understanding:
- Amount = 21 - notification was generated
- Amount = 15 - notification was not generated
- Amount = 21 - notification was not generated (It should have been)
- Amount = 23 - notification was generated
- Amount = 18 - notification was not generated
- Amount = 22 - notification was generated
- Amount = 26 - notification was generated
- Amount = 22 - notification was generated
- Amount = 10 - notification was not generated
- Amount =22 - notification was not generated (It should have been)
As we checked this issue happens in all objects: e.g. Purchase Order, AP Invoice, etc.
Do you have any idea, how to solve this issue?
Looking forward for reply,
Kind Regards,
Ia
Hi Ia,
I'm sorry that I missed your post a few months ago. Some of my email notifications landed in SPAM without me realizing.
This looks like a bug to me. At least that's my opinion. You'll need to create a case with Acumatica to get this escalated to engineering so they can fix it.