The enumerative array input field of smart actions
Observed behavior
When I have one or more values selected in this field and I select a new value from the dropdown, then this new value gets added to the list, but another value gets removed.
Expected behavior
When I have one or more values selected in this field and I select a new value from the dropdown, then the newly selected value should be added to the list without removing any previously selected values. This was how it was working before.
Failure Logs
I assume, this issue only relates to the frontend of ForestAdmin. It does not depend on communication from our FA servers.
Our internal operations team is really losing quite some time due to this bug.
This smart action functionality is an important part of our OPS flow, and the operators are getting frustrated about this sudden malfunction, which has been lasting for 7 days.
So any, prioritization to solve this tomorrow, would be highly appreciated.
We had to revert the fix. Thanks for the feedbacks, we will fix it as well.
Again, we apologise for the concerns and are working in the briefest delays.
If you have reverted the fix, then the new bug, which was released with said fix, is not reproduceable.
Anyway, this revert is not cool and our patience has run out. Our company’s operations workflow is heavily impacted, since 9 days, due to this bug. You need to understand, that this UI glitch has almost doubled the time required for our operators to process incoming cases.
It was long awaited news, that the issue was fixed after 7 days. So, this revert now comes with a lot of frustration.
Alternatively, it would be good to know, for us, how long this will take. We are completely underwater and might need to stop service for some customers, which would be a big problem for us.
The fix is released. Let me know if the bug which appeared after the first release is present again.
The video that you sent us helped a lot for the comprehension of the struggle. We are, once again, really sorry for the issue.
I can confirm, that it is working, on our end. I’m still waiting for confirmation from our OPS team, but as long as you don’t hear from me again, you can consider this fixed.
Thanks for delivering, and for the future, it’s good to know, that a video helps to explain the problem.
I am afraid will have to revert the latest patch due to the fact that it introduced a bigger regression somewhere else.
On another hand, you can still benefit from the patch using future.forestadmin.com (instead of app.forestadmin.com).
We will let you know once definitively fixed.
Thanks for your patience.