Maintenance of Basic Data of Multistep Task

Use

The basic data is used to identify a multistep task.

Features

The tab page Basic Data is used for processing the names of the multistep task.

Identification of a multistep task

Each multistep task is identified with an 8-digit number and the organizational object type WS (for workflow template) or WF (for workflow task). The number is assigned automatically by the system when a newly created multistep task is saved.

You define the first three digits of the number (prefix number) in Customizing.

Transport

As cross-client transport objects (transport object PDWS), workflow templates are always connected to the transport system.

Workflow tasks are only connected to the transport system in a particular client if Automatic recording of changes is set for this client in table T000. In other clients, you can include workflow tasks in a transport request manually. To do this, choose Start of the navigation pathWorkflow Task Next navigation step TransportEnd of the navigation path.

Activities

If you do not save the multistep task as a local object, you must specify a package when saving. The system completes the fields Package and Application Component from this.