Don't want Background Work Item as run as a tRFC

[Former Member]

I have a purchase requisition approval workflow. My problem is that the purchase requisition is showing WF-BATCH as the user-id that did the release of the PR.

My workflow has a sync dialog user-decision step for the approve or reject. If the user approves the PR then it calls a background synchronous release step. I have the "Advance with dialog" check box on the background task.

When I look at the workflow log the background task starts with the dialog user-id, however it then creates a tRFC entry so the work item actually finishes under the WF-BATCH user-id.

What setting(s) do I have to change so that the background work item doesn't execute as a tRFC?

Thanks,

Jeff

[Former Member]

Hi Jeff,

I presume you are using the custom workflow and not the std one.

If so, in your workflow, is the user who is approving the PR is supposed to release he PR or it is different authority who will release PR ?

If it the same authority who acts on user decision and who should release the PR, I could not get the purpose of not using the step <i>Overall Release</i> similar to std PR release workflow as against using the decision and background release step.

Because, in this step of std workflow, user will have to act and release the PR and then you will have his name under workflow log.

As Glauco indicated, for background steps, you will always have name of WF-BATCH.

Regards,

Akshay Bhagwat