Transport and Client Copy 
Transport and Client Copy
Process Flow
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 Task
® Transport or Workflow task ® Transport in the relevant definition environment.Transport of settings for tasks
You maintain the following settings for tasks on a client-specific basis:
The system automatically includes these settings in a transport request if Automatic recording of changes is set for the relevant client in table
T000 .Client copy
With a
client copy , the assignments between tasks and their possible agents and the event receiver linkages are copied.
The event receiver linkages are always deactivated in the target client after copying.
If you want to copy the activation indicator of each individual event receiver 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 event receiver 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.