And… another one bookmarked thanks for that it will come in handy.
Becuase people are too nosy for their own good sometimes. And, people are too damn sensitive as well… So I was trying to avoid “issues” in the future.
The T&E screen defaults to the employee attached to the current user record, so by making the txtEmpNum control read-only, disabling the open with, and disabling the search toolbar button, I’ve basically made it only work for the logged in employee. I thought about putting in some code that would just check to see of the EmpID matched the CurrentEmpID, but this seems to work, so I didn’t bother.
@Mark_Wonsil, all I can say is be glad you are not a government sub-contractor!
We also use to have shared Windows & Epicor logins for the shop MES computers, then the government passes a Cyber Security ruling that included NIST 800-171, which requires the ability to know who accessed/modified/deleted information, and shared logins does not allow us to do that. So every employee will have a login, and I’m looking at setting up SSO as well.
On top of that, we just had a DCAA audit for a new SBIR contract that has all of these labor recording & approving requirements, which includes direct labor employees to have their own password to clock in & out…
It’s going to be a long next 2 months…
2 Likes
Would it be easier to put a BPM with an exception in the GetListForTE where you check for the logged in user and the employee that is being searched for has to match? I’m not 100% sure is that would work, bit if it does, if anyone tries to search, it won’t pull anything up. They might still be able to see a list of employees, but they won’t be able to open the records.
Just a thought.
Bahaha! Oh @nhutchins, I know your pain all too well. We made B-1B, F16, and Patriot launcher parts. Back in the day, we had a full-time DCAA auditor in our building but all of our time keeping was kept on paper! (Mid to late 80s) Thank goodness we weren’t fully computerized in the shop! I feel for you man. Hang in there!!!
Mark W.