×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 19 February 2018 at 10:23, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:
this is conditional masking on system initiated tasks... I'm looking at
strategies to handle masking based on user profile.
Can you describe the business scenario you're working with?
Masking an ID number based on Need To Know (CSR cannot see it at all,
supervisor can see last 4 digits, department head can see all of it)?
Prohibiting update access except for specific persons?
Some of us have puttered around and (for example) ruled RCAC out
because it wasn't a good fit into our business processes. The
question about updating a masked value is one of those business
processes - if (for example) a CSR can't /see/ the credit card number,
how can she be allowed to /update/ it? By and large, we changed
program logic to handle this sort of thing something like a decade
ago, and neither RCAC nor FIELDPROC have been seen as a better fit for
us. I need to stress that this is not a failing of FIELDPROC or RCAC,
but rather not the right size bolts for the holes we already have
drilled.
--buck
midrange.com
