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?
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.
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.
How does your workflow look like? This might be caused because of your workflow design (this will happen when you've got for example a timer to wait for N seconds). You could work around this creating the Task scripted. Though I don't know anything about your workflow design and which steps are causing this so can't answer more in depth.
Basically we have Workflow A for the entire catalog item. Based on a condition, Workflows B, C, D, etc. will be called. Catalog tasks are created in the Workflows B, C, D.
