While parameterized fixlets are not supported in the webUI, it would be helpful to warn the operator against deploying them, or outright prevent them from doing so. Many of our operators attempt to deploy parameterized fixlets, not realizing there are fields they're missing because they can't seem them, causing the fixlet to fail or process indeterminately.
Parameterized fixlets appear in the webUI without any fields or indicators that more options are available in the desktop console.
2 Likes
I originally raised this back in 2020 as part of BFP-I-82 – “WebUI Missing Features & Suggestions”. Six years later, it still hasn’t been delivered.
BFP-I-82 is now the most-voted idea on the entire Ideas portal, with 115 votes, yet it remains in “Future Consideration” status.
Unfortunately, it feels like WebUI may be heading in the same direction as the classic Web Reports, where enhancements and new capabilities have become very limited over the years.
The new Web Reports experience was also introduced with a lot of enthusiasm, but I don’t feel it is being actively refined or enhanced at the pace many users expected.
It would be great to see more focus on these areas, particularly on highly requested features that have had strong community support for several years.
I think I cast my vote on that around 5 years ago myself.
For this idea though, I'm past asking for parameterized fixlet functionality — I just want a way to prevent less experienced operators from attempting to deploy complex fixlets without understanding that something's wrong.
I'd certainly prefer having parameterized fixlets directly, but barring that, I think they're in a bad limbo state that's causing confusion.