Open bksubhuti opened 3 years ago
bksubhuti
commented
3 years ago So how would the record locking work? And what if they simply skip without hitting the skip button?
The problem is they might be "browsing" and just jump around.. that is why I'm not sure auto marking as "skipped" would be good. My guess is if they do not do an action on a record, it can be sent to another general user.. right?
bksubhuti
commented
3 years ago edited colors shown are 50% opaque color for easy making edits and seeing text.. ignore that and use standard colors already there. However.. Gray needs to be a shade darker.. please use the one shown. If save is done by CL code edit, it should turn green.. if edit but no cl code cl box should turn red When CL code is selected.. red goes away. This is only for saved items. Not for skip and send to expert
Buttons should have respective associated colors if enabled. Nothing happens when i do nothing and save a field (assuming it is correct) I change the CL code and hit save.
We actually don't need a save button :) since db writes happen as edits are done.. but just keep the button for now. The save button was originally intended for writing to db all at once. It is fine the way it is and i didn't mention this before.
Need to incorporate a multi-word interface similar to quick view but for the whole group. As I was sending a round of records to the difficult team (just choosing the big definitions which are usually sent to them), I noticed it was addictive and I wanted to go fast. Below is a reworked quick view screen. CL and buttons are swapped. I think that if they are working from the phone, that this interface would not be possible. However, tablets & ipads should be okay from daw wai2 testing before.