DMR Inspector Master file. Establish the valid persons who can process DMRs in the system.
Maybe they didn’t want to build the functionality into SysUserFile…instead using this lookup table to govern it. Presumably there’s data integrity between the two.
Clouseau exists in Training environment
Callahan was… um… Dirty… not a good trait for Quality personnel
and just one more thing…
Columbo was only a Detective Lieutenant
There is no out-of-the-box link between Inspectr and SysUserFile. At least once I’ve written BPMs to ensure that only certain UserIDs could create inspection records with certain Inspector IDs.
Guess I was wrong to think they’d be in a 1-to-1 relationship…unless, as you described, you script a BPM to impose external rules and create pseudo-groups…ie UserIDs A1 and B2 considered “Supervisors”, C3 and D4 considered “Asst Supers”, that sort of thing. Maybe it would have required too much alteration to the regular user setups…or maybe I’m thinking too much
I do remember one time a client asked if there was a way to specify that certain parts be tagged to go to a certain inspector… but by the time they got to scoping that out they dropped the request. Pretty much anything CAN be done, but this isn’t something I get asked about a lot. In a perfect world I’d expect it to work like Buyers (like @JasonMcD said originally), but they never asked me my opinion.
Kind of seems like–given the current simplicity of the Inspector app–it should just be a checkbox on the Employee record, like Production Worker, Material Handler, Warehouse Manager, etc.
