Workflow transport and prefix problem

[#1]

Hello workflow experts,

I wanted to import a workflow template and several tasks in to the test system without knowing that the framework was not customized. The objects couldn't be created the in import and the customizing also had errors.

I've started the automatic customizing and it worked except I did't activate the prefix. After several attempts I've finally managed to activate the prefix direct in the test system .... but unfortunately the import still does not work. The workbench transport request is imported without any errors but the tasks in the workflow template are still missing ?!

Does anyone have any ideas why this is happening?

Thankx

Johann.

[Former Member]

Hi Rob,

the workbench transport has no errors. The customizing transport has warnings: object x,y,z does not exist.(TS tasks) so the customizing for the agent assignment cannot be saved.

If I try to open the missing tasks with PFTC I get the message "... does not exist".

I have changed the workflow template (which got imported) and all of the tasks, so that they would be registered in a transport request and that I could import them. I tried this 3-4 times without succes.

Regards

[Former Member]

Hi,

Not only all tasks, also all methods (bor or class) and all data dictionary references in container elements.

Kind regards, Rob Dielemans