Permissions on variables: only allow certain individuals to view the variable on the RITM

 go to the variable> permission tab






masked variables:

see https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0681163 

 

other ideas:

 

Push sensitive variables into a single multi-line variable on submit of the cat item

 

Example onsubmit client script:

function onSubmit() {

    //Type appropriate comment here, and begin script below

 

    var sVars = g_form.getValue('test_variable_1') + '\n' + g_form.getValue('test_variable_2');

   

   

    g_form.setValue('sensitive_data', sVars);

 

    g_form.setMandatory('test_variable_1', false);

    g_form.setMandatory('test_variable_2', false);

   

    g_form.setValue('test_variable_1', '');

    g_form.setValue('test_variable_2', '');

 

}


 


Use display business rule with g_scratchpad to determine visibility

 

Business rule

(function executeRule(current, previous /*null when async*/) {

 

    // Add your code here

    var reqFor=current.requested_for;

    var opBy=current.opened_by;

   

    g_scratchpad.reqFor=reqFor.toString();

    g_scratchpad.opBy=opBy.toString();

   

    gs.addInfoMessage('requested for: ' + current.requested_for);

   

    gs.addInfoMessage('opened by: ' + current.opened_by);

 

})(current, previous);

 

Client script (on RITM, task)

function onLoad() {

   //Type appropriate comment here, and begin script below

   alert('scratchpad req for: '+g_scratchpad.reqFor);

    alert('scratchpad op by: '+g_scratchpad.opBy);

}

 

Use a UI policy to hide the blanked variables on RITM and Task

 

Or, set the rules directly on the variable with access granted via a role


 


 

 

Comments

Popular posts from this blog

GlideRecord setValue

URL link in addInfoMessage