More beta testing!
In 2024.2.7 kinetic MES does not clear the previous clocked in employee id. This is causing employees to book time on other employee records.
Anyone else seeing this?
1 Like
Yes somebody else posted about this recently, don’t have the thread handy though.
1 Like
This is also ocurring in 2024.2.4 not just a .7 thing. It’s a PRB: Open Problem PRB0283605
3 Likes
Thanks all! I guess a workaround for now could be a BPM.
1 Like
Were you able to come up with a BPM that cleared the ID field?
1 Like
Nope I’ve been messing with it for a few days now to now avail, with BPM attempts and a Kinetic layer. If anyone has a solution let us know! 
1 Like
Another error we are coming across is having to refresh the browser after each employee. We are using barcodes for the employee ID. After clearing the ID field for the next user, they scan the barcode and it will log them in, only for the mouse clicks to not render when selecting buttons. We have to refresh the page, which automatically signs them out of their ID to start over with clocking out/starting multiple activities.
Look at the event MESControl.Login. It got changed at some point and now has the final row-update duplicated before the condition. You’ll see the same row-update twice in the event.
Hook override a new event that removes the first row-update that shows up before the condition. This has fixed it for us.
3 Likes
That Worked! Thanks! 