question Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx in Developer forum

: com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

Meenal Gharat — Sun, 09 Aug 2020 22:33:43 GMT

Hello expert,

we are receiving the below Errors seems setUseEngines is not accessible in scope xx

Evaluator.evaluateString() problem: com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not allowed in scope xx

Is there any replacement for this or any suggestions?

Thanks in advance!

Meenal

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

MrMuhammad — Sun, 09 Aug 2020 22:42:06 GMT

Hi,

In scoped Application you need to use GlideScopedEvaluator().

Thanks & Regards,

Sharjeel

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

Alok Ranjan Das — Sun, 09 Aug 2020 22:57:51 GMT

Hi Meenal,

Could you please give a try by cresting a script include in global scope and try to invoke the script as mentioned in the below HI link.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0820691

Regards,

Alok

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

paulmorris — Mon, 10 Aug 2020 00:50:54 GMT

Some globally scoped methods are not allowed in application scopes for security reasons.

Can you explain what you are trying to achieve so we can suggest an alternative API?

Creating a Global script include that becomes a dependency on your scoped application as suggested by @Alok Das can be considered a workaround, but I would advise caution. I would see this as a bad design choice as it somewhat defeats the purpose of developing in application scope and in my view should only be undertaken as a last resort.

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

Meenal Gharat — Mon, 10 Aug 2020 05:18:08 GMT

Hi paul,

Thanks for the reply.

setUseEngines function used to ignore data policy updates.

Can you suggest some other API for this?

Thanks and Regards,

Meenal

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

Meenal Gharat — Mon, 10 Aug 2020 05:29:45 GMT

Hi paul,

this business rule is used to Prevent Discovery set FQDN on Hostname

var hn = current.host_name.toString();
var cn = hn.split('.');
var nm = cn[0];

if(hn.contains('.')){
if(isNaN(nm) == true){
current.host_name = nm;
current.setUseEngines(false);
current.setWorkflow(false);
current.update();
}
}

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

asifnoor — Mon, 10 Aug 2020 07:08:13 GMT

Hi,

Create a SI in global scope and put this code there and then in the BR you can call

new global.your_si_name().your_function();//current will be available in your SI so your code can work as is in SI.

Kindly mark the comment as a correct answer if this has solved your problem.

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

Meenal Gharat — Tue, 11 Aug 2020 09:14:06 GMT

Hi asifnoor,

Similarly we are using setUseEngine scripted REST API. where SetUseEngine is used to avoid Duplicate SLA. Can we do the same for this as well ?

below is our code.

kindly suggest.

Thanks,

Meenal

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

paulmorris — Wed, 12 Aug 2020 00:22:28 GMT

It makes sense for that API to be disallowed in an application scope.

What is the reason for doing this in an application scope? Perhaps it would be more appropriate in Global?

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

Meenal Gharat — Wed, 12 Aug 2020 02:15:59 GMT

Hi paul,

This is integration between SNOW and Third party that's the reason it is in Scoped Application.

Thanks and Regards,

Meenal

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

paulmorris — Wed, 12 Aug 2020 02:26:47 GMT

Is this bound for the Application Store?

If so, you can't use the Global Script Include workaround mentioned, as that cannot be packaged as part of your application.

Is there scope to get the existing Data Policies converted to UI Policies?

Re: : com.glide.script.fencing.MethodNotAllowedException: Function setUseEngines is not a allowed in scope xx

Meenal Gharat — Wed, 12 Aug 2020 03:03:17 GMT

Hi Paul,

so in this case according to the comments they're are using setUseEngines(false) to avoid duplicate SLA creation.

Is there any other way to replace this in scope application?

var alertAlias = body.alias;
var note = body.workNotes;

var inc = new GlideRecord('incident');

inc.addQuery("x_alert_alias", alertAlias);
inc.addQuery('state','!=', 6);
inc.addQuery('state','!=', 7);
inc.addQuery('state','!=', 8);
inc.query();

if (inc.next()) {
inc.work_notes = note;

inc.setUseEngines(false);//Added to stop SLA Duplicate issue
inc.update();
gs.info("[Add Note To Incident] Processing finished.");
} else {
gs.error('[Add Note To Incident] Unable to find incident with x_alert_alias : ' + alertAlias);
}

Kindly suggest!

Thanks for the response.

Meenal