
Transport of cross-client tasks
As cross-client transport objects, standard tasks (task type TS) and workflow templates (task type WS) are always connected to the transport system and are automatically included in a transport request, if the client settings (table T000) allow changes to cross-client objects.
Transport of client-specific tasks
Customer tasks (task type T) and workflow tasks (task type WF) are only included automatically in a transport request in a particular client if automatic recording of changes is set for this client in table T000.
In other clients, you can include customer tasks and workflow tasks in a transport request manually. To do this, choose or in the relevant definition environment.
Transport of settings for tasks
You maintain the following settings for tasks on a client-specific basis:
Assignments between tasks and their possible agents
Type linkages and their activation
Workflow configuration
The system automatically includes these settings in a transport request if automatic recording of changes is set for the relevant client in table T000.
Transporting a workflow definition
If a workflow definition is transported into another system, only the active version is transported. If the workflow definition exists in the target system with the same version number, it is overwritten by the transported version if it has no workflows running. Otherwise, the transported workflow definition is saved with a free version number. The transported workflow definition becomes the active workflow definition in the target system.
Client Copy
With a client copy, the assignments between tasks and their possible agents and the event receiver linkages are copied.
The type linkages are always deactivated in the target client after copying.
If you want to copy the activation indicator of each individual type linkage as well, you must specify this explicitly as a parameter option for copying tables of class A.
Event linkages with installation or upgrade
With a new installation or an upgrade, the type linkages are copied into all target clients. But the activation entries are only copied into client 000. Any existing entries are overwritten in this operation.