question current.setWorkflow(false); in Developer forum

current.setWorkflow(false);

Servicenow10 — Fri, 06 Dec 2019 08:55:55 GMT

can anyone explain me why using current.setWorkflow(false) should not be followed or is it an unethical way?

and if i use would it be a wrong method for a developer

curious to know just for knowledge

thanks

Re: current.setWorkflow(false);

Mark Roethof — Fri, 06 Dec 2019 08:59:28 GMT

Hi there,

Completetly up to your situation/need. It can be valid to use setWorkflow(false) sometimes. For example, if you are updating records and don't want Business rules or Workflows to be triggered.

It would be different if you would always use this. That would be odd 🙂 Though it really depends on your situation if it's useable or not.

For the usage, see:
https://developer.servicenow.com/app.do#!/api_doc?v=newyork&id=r_GlideRecord-setWorkFlow_Boolean

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

Re: current.setWorkflow(false);

admin1 — Fri, 06 Dec 2019 09:21:26 GMT

hi mark,

Am using this in my change request workflow where i set the value false so is it right way to proceed

Re: current.setWorkflow(false);

Mark Roethof — Fri, 06 Dec 2019 09:42:27 GMT

The question: what is the need for your query? Just for every GlideRecord query... absolutely not! If it's for a valid reason, like on purpose you don't want Business rules to execute, oke fine.

So again, why do you want to use setWorkflow(false)? What is your need? Or is it just because someone told you about this option and your thinking that could be nice? Though actually there's no reason for applying it?

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

Re: current.setWorkflow(false);

Servicenow10 — Fri, 06 Dec 2019 11:00:19 GMT

I have customized change request workflow where after approver's rejection it goes new state ideally but customization it goes to closed state.

however, i used current.setworkflow(false) in my wf

so is this the correct way

Re: current.setWorkflow(false);

Mark Roethof — Fri, 06 Dec 2019 11:18:24 GMT

So what customization makes the state go to Closed? Why not have a look at that?

Just applying setWorkflow(false) for this feels like a quick escape / easy workaround. Will work, though have a look at the actual issue instead of working around it.

So in my opinion, not a valid use of setWorkflow(false).

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

Re: current.setWorkflow(false);

Servicenow10 — Fri, 06 Dec 2019 11:56:14 GMT

then what should be the approach

Re: current.setWorkflow(false);

Mark Roethof — Fri, 06 Dec 2019 11:57:08 GMT

Like I mentioned:

So what customization makes the state go to Closed? Why not have a look at that?

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

Re: current.setWorkflow(false);

Servicenow10 — Fri, 06 Dec 2019 12:12:44 GMT

I have wrote a code in my run activity script:

current.close_notes = "rejected ";
current.close_code = "unsuccessful";
current.state = 3;

can you please help me to achieve this through script include

Re: current.setWorkflow(false);

asifnoor — Sun, 08 Dec 2019 19:58:37 GMT

Hi,

In this current case, where the requirement is to have CR state to be closed (instead of cancelled) When it is rejected.

The OOB BR restricts the change of state.

Hence suggested to use setworkflow(false) in the run script so that the Br does not run on this record and the state is changed to closed.

Re: current.setWorkflow(false);

sivaprince231 — Mon, 09 Dec 2019 06:14:40 GMT

Prior to updating your task, add a call to setWorkflow(false) on the GlideRecord object for the task within the business rule that is updating the task. This prevents the business rules from being processed.

Re: current.setWorkflow(false);

Servicenow10 — Mon, 09 Dec 2019 09:12:44 GMT

according to you which br should be stop if i stop this State model - Can change state? this will affect others too which i don't want

Re: current.setWorkflow(false);

asifnoor — Wed, 18 Dec 2019 11:23:04 GMT

Hi,

In this current case, where the requirement is to have CR state to be closed (instead of cancelled) When it is rejected.

The OOB BR restricts the change of state.

Hence suggested to use setworkflow(false) in the run script so that the Br does not run on this record and the state is changed to closed.

Kindly mark the comment as a correct answer and helpful if it helps.