Loss of tasks agent assignment when transported

Question

I have a task in a workflow with an agent assignment. When I transport the workflow, I lose the agent assignment. How can I fix this? I tried to re-transport the workflow but it did not help things.
A little more information: the agent assignment is to a Position that I had existing in the development environment, but not in the test environment before the first transport of the workflow (I forgot to create it).
I have now created it, but still cannot get the agent assigned.

Answer 1

G'day Anthony,
Are you refering to use of the Position against the Task as a Possible Agent or at the step level as the Responsible Agent?
Typically you don't transport the possible agent info because as you've realised the Org data isn't the same between systems. Realistically you normally would want different possible agents anyway during testing and QA. This does mean that you need to set up possible agents after transport.
If you're refering to step level responsible agent, the use of a position directly is not recommended. In this case you could try using the position as the only possible agent and leave the responsible agent at the step blank (therefore it will go to all possible). Alternatively you can have a simple resposibility rule which will allow you to maintain the position though OOCU_RESP in each system/client.
Good luck,
Mark