If at any point a workflow running under the username(User A) initiating the workflow fails or needs an activity re-run, if an Admin user(User B) goes to the K2 Workspace and forces to re-run the Activity with the Go To Activity tool of the workflow instance.
Does that force a name change to the workflow process from User A to User B? Reason being I found that a workflow was running under an Admin user in the K2 SQL DB even though the end-user started the process.
Thank you in Advance
No, using GoToActivity method either in the workflow via API call or in workspace as an administrative function will not change the originator of the process. If UserA is the user that started the process and UserB performs a GoToActivity the originator of the process is always going to be UserA. That value is set once at the start of the process and doesn't change during the lifetime of the process.
Though, I am curious as to where you were looking in the K2 database to see that the workflow was running under a different user and what did you mean by running under? For clarity for anyone that finds this thread in the future, workflows are not executed in the context of any user interacting with the workflow and the workflow is executed by the K2 Service account with the rare execeptions where a developer has configured a step in the workflow to execute under alternate credentials using the "Run As" feature.
Can you tell us what table you were looking at that lead you to this conclusion? If you are seeing unexpected results it would be something else than GoTo.