In the application variation, checkboxes have a third state (eg. checked, unchecked, and Indeterminate).
But in Kenetic forms, like for filtering, some Search/Find dialogs have checkboxes whereby you check for true or leave them unchecked for false.
However, what if I want both? For example, when trying to search for BPMs in [ ] Shared … I can either get a list of ones that are shared OR a list of one that are not shared. How can I get them all regardless of that setting. This is further exacerbated when there are more than one checkbox like this on the same dialog. You’d basically have to think of all combinations of on/off and iterate over and over to see all the result variations to make sure you’re seeing all the items in the system.
IMHO this a short sighting… in this case, the checkbox is not the correct control, because in Kenetic (like native web checkbox controls) they are only Boolean.
I asked support about this and they didn’t see the merit. Alternatively suggesting that this is a feature request.
Anyone else having this issue or know of a workaround (other than using app version)?
I know nothing about Kinetic, so apologies in advance, but I do know that a 3 state checkbox is possible with native Angular using their Material library. I don’t know if Kinetic implements this or if you can create your own controls, but this is at least theoretically possible in the framework as I understand it.
@Jeff_Owens - If this is Kinetic losing a Classic UI feature, submit an example with the Kinetic Feedback form. Epicor seems to want to keep moving forward, not slide back with Kinetic losing features.
I’m thinking something like BAQ’s where you have the option of searching for “Shared” - Box is checked (true), unchecked (false), or solid (returns both Shared and Not Shared BAQ’s). (BAQ’s isn’t Kineticized yet, though).
One method used was to create a directive calc field set to ‘N’ when the boolean field was true, and ‘Y’ when false.
The filter would then include records not equal to the query value: ‘Y’ selection would include all non-‘N’ records, ‘N’ selection includes all non-‘Y’, with a blank indicator selecting all (non-blank) records.
Alternatively suggesting that this is a feature request.
