Catalog tasks are created by 'system' instead of the requestor

Thi Dinh Nguyen
Tera Expert

Hello all,

I have a workflow for a catalog item that calls another child workflow, which creates catalog tasks. And all the catalog tasks that are created by that child workflow have "system" as the "Created by" value instead of the requestor. Is there any way so that the catalog tasks are created by the requestor instead of the "system" user?

Thanks,

Thi

1 ACCEPTED SOLUTION

Maik Skoddow
Tera Patron
Tera Patron

Hi @Thi Dinh Nguyen 

 

unlike Flows the old school Workflows do not provide an option to specify the "Run as" behavior manually. Basically, the Workflow context is created in the name of the currently logged-in user. But there are some special Workflow activities like "Timer" which switch the context to the "system" user and all following activities will inherit that system user. This is as expected and cannot be changed.

If you really want to control the "Run as" user, I recommend migrating to Flows.

Maik

View solution in original post

7 REPLIES 7

Hi @Thi Dinh Nguyen 

 

did you see my initial response to your question? I wrote:

 

"But there are some special Workflow activities like "Timer" which switch the context to the "system" user and all following activities will inherit that system user. This is as expected and cannot be changed."

 

Maik

Thanks Maik, I removed the Timer activity and it seems to be working again. Sorry for missing your previous reply.

Ankur Bawiskar
Tera Patron
Tera Patron

@Thi Dinh Nguyen 

Since you have a delay in your workflow it's OOB behavior that created by will show as system since timer activity runs with that user

check this link

Opened By field is populated as system for Task created by a workflow 

If my response helped please mark it correct and close the thread so that it benefits future readers.

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