Jannes Drijkoningen Posted July 14, 2020 Share Posted July 14, 2020 Hello, The release notes from 1.3.5 mention that reporting in through the notification was fixed: - Fixed a bug when trying to report in from a notification and not properly updating the soldiers last report in date. However, we are still experiencing those issues. Is there something that we need to change? Quote Link to comment Share on other sites More sharing options...
Administrators Jon Erickson Posted July 14, 2020 Administrators Share Posted July 14, 2020 Can you outline your exact keystroke flow that triggers this error? Quote Owner Deschutes Design Group LLC email | jon@deschutesdesigngroup.com Link to comment Share on other sites More sharing options...
Jannes Drijkoningen Posted October 4, 2020 Author Share Posted October 4, 2020 Sorry for the extremely late response, we've just started running into it again, and I'd say the system works as indented but the user interface isn't clear at all. When you get the PERSCOM notification for not reporting in for X days, and you click it, it brings you to the operation center. Over there you must now click on a record on top of your report in history to complete reporting in. A lot of users expect to be able to press the "report in" button instead of having to go into their history and find the record with a different text. I'd suggest changing the report in button to not only filter by date, but also filter by reportin status. I've noticed that people with this error all have a reportin record with status 2. So some logic to make the report in button handle those with status 2, or ignore those with status 2. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.