User Criteria for logged in user not working

RudhraKAM · ‎07-19-2018

I have a user Criteria where logged in uses / users who are active can view , but seems like its not working as expected

can some one help me whats wrong in the code

scriptAut();

function scriptAut() {

var retVal;

if (gs.getUser() =="") { // i tried this as well if (gs.getUser() ==active) {

retVal = false;

} else {

retVal = true;

}

return retVal;

}

RudhraKAM · ‎05-21-2020

Yes ,, gs.getuser is not supported in user criteria ,, there is a problem ticket opened

This is the solution given by Hi team

Solution Proposed: ============ IS THIS A BUG? ============

So we are dealing with a bug on our platform which is intermittent and occurs very rarely. This is recorded in PRB1319258 with the following description: Using GlideSystem objects such as gs.getUser(), gs.getUserID(), gs.getSession() in User Criteria does not work as expected consistently. This problem has been declared as "Working As Expected" with the reason that the issue happens very rarely.

============ ANY WORKAROUND? ============ However, we have a workaround in place which will involve moving your implementation to using script include (which is aware of application scope changes). This will ensure that the value returned correctly every time without failing intermittently. Please throughly review this knowledge article regarding this (has examples): https://hi.service-now.com/kb_view.do?sysparm_article=KB0719846

View solution in original post

RudhraKAM · ‎07-20-2018

Mike Patel · ‎07-24-2018

Can you share KB article screenshot?

RudhraKAM · ‎07-24-2018

Mike Patel · ‎07-24-2018

try

condition = answer();
 
function answer(){
var gr = new GlideRecord('sys_user');
gr.addQuery('sys_id', gs.getUserID());
gr.addQuery('active', true);
gr.query();
condition = gr.hasNext(); 
	return condition;
}

Mike Patel · ‎07-24-2018

I just tested my code and it worked fine in my dev instance.