Flow designer "run as system user" issue

Community Alums
Not applicable

When you select "run as system user" option in Flow designer properties for catalog item, the request item creates SCTASK with empty "opened_by" field. This issue never existed on Workflow designer.

I have created a BR on SCTASK table to copy "opened_by" from its sc_request table. However, this BR works only on update, but doesn't work on insert. Any ideas?

Business Rule:

Before Insert/Update

Filter Conditions: opened_by is empty

Actions: opened_by is same as request.opened_by

8 REPLIES 8

Ankur Bawiskar
Tera Patron
Tera Patron

Hi Vikas,

not sure if that is the issue of flow designer

So BR on sc_task should pick opened_by from request and populate to task

It should be before insert in order to set that; why before update you are using?

Script:

current.opened_by = current.request.opened_by;

Mark Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur

 

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Community Alums
Not applicable

Hi Ankur,

Before insert doesn't work whatsoever. I also tried without any filter conditions, still doesn't work.

Before update, however, works, and that is what puzzles me.

Hi Vikas,

seems strange; BR itself not triggering

So if Before update is working then use this

current.opened_by = current.request.opened_by;

current.setWorkflow(false);

current.update();

Mark Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Pradeep Sharma
ServiceNow Employee
ServiceNow Employee

Hello Vikas,

A before business rule gets triggered but looks like you can set opened by field during update operation. Also I recommend to not use current.update() in a BEFORE business rule.

That said for your original issue related to FD- I strongly recommend reaching out to customer support on this one. Sorry.

 

- Pradeep Sharma