Just make the BAQ interface work 100% of the time.
I was just in a BAQ and the Table query was blank - but the icon for the Table showed a checkbox.
It still is very buggy.
Like @aosemwengie1 I have given up reporting bugs and issues because they aren’t getting addressed. Instead we get what is my carbon footprint of the products that I am selling.
PLEASE dont give up on reporting… when you report, it gets into our backlog. While you may still have open issues, we have a huge effort going on to reduce and resolve this backlog of issues. But note that some of these issues take specialized teams to resolve, and while that is happening, we are also adding new features with the other development team members (like carbon tracking, which is a 100% requirement for our European and Asian customers.)
This all has to do with how the web UI works, and the entire design. Note that you CAN change the “tab order” but it is not by changing numbers… it is literally by changing teh position on the screen. The browser goes through the fields in the sequence they appear on the screen, but there is also the concept of grouping fields, and so once grouped, it will also follow the sequence of those groups as well. so by regrouping and rearranging fields on the screen, you can define an order for the fields that works for you.
Barcodes are where keyboard navigation really hits home!
Efficiency and accessibility outcomes usually only affect users who aren’t making software decisions.
“The new version doesn’t work with our barcode scanners” is a sentence that can encourage major projects and life changes.
Accessibility is a requirement if automation is a consideration.
WHY should tab order matter? In my mumble…mumble…mumble years in IT, pushing automation through the UI has ALWAYS been brittle - for this and many other reasons.
We need a barcode interface that is intelligent. The UI should accept the whole string from the reader and process it logically. AIAG labels have the type of the field, so it will know if it’s a part or a quantity etc. The screen can wait for UI validation and then move onto the next field. Put the intelligence back into reading barcodes and stop throwing them over wall and expect good results. It was a bad idea in the late 90s and it hasn’t gotten any better.
Yeah, I’m the annoying guy who never answers the question asked but comes back asking, “why are we still doing it that way if it doesn’t work well?”
In my first Vantage implementation, I tried using what we would call Robotic Process Automation today to load the parts. It was slow. The automation got ahead of the screen, the information for part x got the information from part y, ugh, it was a mess. What I needed was a reliable contract. I thought, “hey, this client is DOTNET, let’s use the business object.” So, I wrote a VB.NET program that loaded the parts, captured the failures to another file and it was so much better.
(BTW, the recent RPA craze seems to have calmed recently too. )
What I’m proposing is doing it in a way that does not have this dependency on tab order. In classic, it would take a lot of client side code. In Kinetic, we can create our own applications! Why use the standard UI if I can customize it to be barcode friendly? Think outside the textbox, as it were.
Hot Key Parity:
You can’t remove a hot key once you create one.
Workaround is to set the item to the F999999 key.
If you assign a hot key it doesn’t show on a menu item that a hot key was assigned.
Hot keys should probably be added to the over flow menu as an item, why are hot keys only accessible thru using hot keys?