4 ms·
To be clear, we did support keyboard workflows, like Y/N They were pissed we replaced the Y/N text items with a checkbox. Any deviation, including things like
by banana_giraffe 5y ago
To be clear, we did support keyboard workflows, like Y/N
They were pissed we replaced the Y/N text items with a checkbox. Any deviation, including things like lower case text, were pushed back.
- ddingus 5y agoMaybe that has to do with things like documents workflows, other meta information related to the applications.
- wizzwizz4 5y ago> They were pissed we replaced the Y/N text items with a checkbox. At this point, I'd probably factor out the UI, hand them the client-side source code and tell them to get on with it. If they want to customise the UI, then so long as you're not supporting it… … but yeah; that's a less reasonable objection than I thought it was. (Still a change to their workflow, and still understandable, but there were legitimate business reasons that the workflow needed to be changed.)