Event Rules Changing When Updating NXAnswered
I have a large number of sites running on NX Witness. We had created event rules for all sites when they were on v4.2 and when upgrading each site, the event rules keep changing and NX automatically adds an additional 10x event rules with mobile notifications that were never there to begin with. This means that every site we update, we need to also correct the Event Rules.
This was raised in another discussion but had been closed off as completed and fixed in v.22.214.171.124270+ but doesn't seem to be as event rules are still changing upon update.
Hi Daniel Kim,
I assumed you are referring to the old post here. However, I'm not sure if you have the same scenario as the previous issue. We may need your help to provide the details about the problem:
1. What's your Nx version? We just release a 5.0 patch and perhaps you could check it first.
You could update it via the following in-client info directly:
Build Number: 36221
2. If the problem persists, please share the test steps with us to reproduce the issue. A screen recording would be good to explain.
Thank you for your cooperation.
The issue described in the older post is slightly different but essentially the same. Event rules are being changed when updating NX witness.
When I update from v126.96.36.199840 to v188.8.131.52745, additional event rules are being added that I never set. Please see below screenshots.
First 2x screenshots show the version and event rules before updating. The last 2x screenshots show the same after updating. You can see that an additional 9x mobile notification and 1x desktop notification event rule that was not set before update. They are added automatically when updating to latest version.
There is no notification to say NX witness has added event rules and no advanced warning to say that event rules would be changed upon updating. This is not a critical issue but pretty annoying. Is there a way we can avoid NX witness changing my settings of it's own volition and without warning?
Also, I updated a site to build# 36221 and the same thing happens.
Dear Daniel Kim,
We appreciate your feedback regarding the recent changes in our system. We would like to inform you that the behavior you have reported is not considered a bug, but rather an intended feature. As of version 5.0, we have implemented default rules to enhance the notification process for important issues that may arise, especially for those users who may not have set up their outgoing email configuration.
Our goal is to ensure that the owner and administrators are promptly informed of any significant matters that require their attention. We think it is important to keep the applicable users informed and updated at all times when issues arise, and we strive to provide the best possible service.
Please do not hesitate to contact us if you have any further questions or concerns.
Please sign in to leave a comment.