Hierarchy

⤷

⤷

Basic Data
Data Element | SWD_NODDSC |
Short Description | Name of Step or Outcome |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SWD_NODTXT | |
Data Type | CHAR | Character String |
Length | 80 | |
Decimal Places | 0 | |
Output Length | 80 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Step |
Medium | 20 | Step name |
Long | 0 | |
Heading | 40 | Step name |
Documentation
Definition
User-defined name under which this step or outcome appears in the workflow definition.
Supplementary Documentation - SWD_NODDSC0001
Use
In an activity within the workflow definition, the step contains a reference to a task from the task catalog of Organizational Management.
The step description is a text which is displayed within the workflow definition.
An activity is followed by at least one outcome in a workflow definition. The outcome describes the state reached and has no other effects.
Enter a text here which describes the state.
Supplementary Documentation - SWD_NODDSC0002
Use
A condition or a loop (UNTIL) is always followed by two outcomes. Enter a text for each outcome as a name. These names are used to label the two outcomes in the workflow definition.
Supplementary Documentation - SWD_NODDSC0003
Use
Within a multiple condition in the workflow definition, the step name is a short description of what is evaluated.
The possible outcomes are defined with the comparison values and are identified with names.
Supplementary Documentation - SWD_NODDSC0004
Use
The individual branches within a multiple condition are described by outcomes.
Assign a self-explanatory name to each outcome, describing the result which has occurred.
Supplementary Documentation - SWD_NODDSC0005
Use
A condition is always followed by two alternatives which can occur in the course of processing.
These two alternatives are identified by 0000 and 0001. To describe this internal representation in more detail, self-explanatory names should be specified as the outcome name.
Supplementary Documentation - SWD_NODDSC0006
Use
A user decision is always characterized by several alternatives. You can define each of these alternatives by specifying an outcome name. This event is a name for the relevant alternative.
A decision text is also entered for each alternative, which is displayed to the agent at runtime.
Supplementary Documentation - SWD_NODDSC0007
Use
The name of the task is proposed as the step name.
Procedure
You can overwrite the proposed text.
Examples
Dependencies
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in |