Context when Invoking Long Running Processes

Avatar

Avatar

NW987

Avatar

NW987

NW987

01-07-2010

When I use a long running process to invoke another long running process, the creator of the second long running process is always "System Context Account".

Is it possible to invoke one long running process using another long running process using the context of the workspace user?  The primary need here is to be able to track the process in the audit tab.

View Entire Topic

Avatar

Avatar

Gary_Gilchrist

Avatar

Gary_Gilchrist

Gary_Gilchrist

05-07-2010

This is not a very useful answer, but might be relevant added info: You can browse services (that arise from your deployed processes) in the Admin UI and configure their "Run As" behavior. The Run As can be set to the Invoking User, a named user or System. I think you may be able to set the Run As for any long lived process to be the process invoker, which will in turn get passed through to any sub processes that get called. The downside of course is that you may not really want those processes running as the end user because it performs activity steps for which the end user is not authorized to invoke etc.

That said, even if you do propagate the invoker's identity through to the invocation of sub processes. Workspace might not track it. I think this is beacuse Workspace only tracks the process that it paricipated in (through inintiation of task assignment) not other processes that get a knock-on assignemnt. I need to check with the Workspace team to verify that suspicion though.