Tuly Posted August 24, 2017 Report Posted August 24, 2017 whenever you make a change in a callflow you get a reminder to save the changes with a warning " You have modified this Callflow, don't forget to save it! but when you change anything inside a ring group, it will not say this warning, and the ring group will not be saved only if you click the green button save changes, would be good to have this warning also when you edit a ring group, Thank you! , "
2600Hz Employees Brooke Shepherd Posted August 24, 2017 2600Hz Employees Report Posted August 24, 2017 Hi Tuly! Thank you for the question & feedback, personally I like a well placed warning pop-up myself....so I will get in touch with engineering and respond here when I hear back from one of our talented engineers. Thanks again and take care!
2600Hz Employees JR^ Posted August 24, 2017 2600Hz Employees Report Posted August 24, 2017 I created https://2600hz.atlassian.net/browse/UI-2880 to track that feature request. Thanks for the report!
2600Hz Employees Brooke Shepherd Posted August 24, 2017 2600Hz Employees Report Posted August 24, 2017 Thanks @JR^ !
Karl Stallknecht Posted August 24, 2017 Report Posted August 24, 2017 Wait...I thought when you change a ring group and click okay, it saves it when the popup closes so there isn't a need to save the call flow? (hence no warning message) - I just tested it and confirmed this behavior.
2600Hz Employees JR^ Posted August 28, 2017 2600Hz Employees Report Posted August 28, 2017 So after testing what you both described, I actually can't reproduce either behavior. Testing on both ui.zswitch.net or monster.sandbox.2600hz.com, If I edit a ring group, I DO get the "warning message" telling me to save the callflow to apply the changes. Updating the ring group alone will not save any changes in the callflow, so I'm also curious how you were able to do that @Karl Stallknecht. Could you possibly take a video reproducing this behavior to see if I'm missing anything?
Tuly Posted August 28, 2017 Author Report Posted August 28, 2017 @JR^ ummm Very interesting, the only way I can re-created now is if I change the "timeout" to less than the current time, for example the current timeout is 40 seconds, change it to anything less (20 or 10) or change it to anything more but less than 10 seconds (45 or 49) but more then 10 seconds is good,
2600Hz Employees JR^ Posted August 29, 2017 2600Hz Employees Report Posted August 29, 2017 Thanks Tuly, I'm able to reproduce that too and will work on a fix for that case.
Recommended Posts