When setting application policy Can Use Application to value No One, the following exception is printed:
I do not see a way to set this value without viewing it on the Web-UI. So this looks like being a useless option, isn't it?
Judge | |
Sep 25 2014, 3:41 PM |
F208968: Unbenanntes_Bild.png | |
Sep 25 2014, 3:41 PM |
When setting application policy Can Use Application to value No One, the following exception is printed:
I do not see a way to set this value without viewing it on the Web-UI. So this looks like being a useless option, isn't it?
We use the same policy control everywhere, but some policies aren't meaningful in some contexts. We could do a better job about hiding them, although that would also create some confusion ("why can't I select 'no one' in this dropdown?"). Since it's fairly obvious why "no one" doesn't work with the current workflow once you save, I don't think this is too bad. It could be a bit cleaner, but the ideal version of this would look roughly the same ("no one" present, tells you why you can't use it when selected, just looks less exception-ey).