WF Transports

[Jan Spott]

Hi Diane,
 
it depends on your development:
 
If you use Customer task(T) and Workflow task(WF), you have to transport it
as a customizing request. The development is client depending.
 
If you use Standard task(TS) and Workflow pattern(WS), you have to transport
it as a workbench request. The development is client independend. Please
have a look at transaction SE10. You have to transport everything wich is
involved with the workflow development (function groups, tables, objects
etc.).
 
Take care if you want to transport a workflow to a productiv system with
active instances of your development. This is really hard. It could be that
the old instances no longer run after your transport.
 
Regards Jan Spott
IXOS Software
 
 
-----Original Message-----
From: Nobles, Diane [mailto:nobles_dh at nns.com]
Sent: Dienstag, 14. November 2000 18:02
To: SAP-WUG at MITVMA.MIT.EDU
Subject: WF Transports
 
 
Dumb question - We are developing our first workflow in 3.1H.  I know the
various objects are transportable from client to client, but what about the
definition and tasks???  Exactly what parts of the Workflow are
transportable and which aren't?
 
Diane H. Nobles
SDE PM Team
0-7250