Maintenance of User Decisions (SAP Library

Maintenance of User Decisions

Purpose

In a user decision, the task description is displayed to the current agent together with the possible decision options during execution. You can use a user decision in the following situations:

Only one of several possible alternatives can be processed in the workflow from a business point of view at execution time..

A decision about the progression of the workflow must be made in dialog with a user.

An instruction (= user decision with only one decision option) is required to continue the workflow.

For approval and release steps, possibly in connection with a secondary method (the latter is possible without the application having to cater for these functions).

In the workflow definition a user decision is represented with the symbol .

Prerequisites

The user decision refers to a decision task. In order for an individual text to be displayed in the dialog box for the user decision, you must create your own decision task. You specify the individual text as task description in the task definition. For further information, refer to Creating Decision Tasks.

If you do not think an individual text is necessary, you do not generally need your own decision task. In this case, you use the task generic decision task ( TS00008267 ).

Process Flow

The maintenance of a user decision is spread across several tab pages. You can process its properties here, for example:

Decision options

Responsible agents

Deadline monitoring

The order of the tab pages defines the recommended sequence of processing.

On the tab page Decision, you can make all the entries required to define an executable user decision.

When a user decision is created, the system enters the SAP decision task generic decision task ( TS00008267 ) into the relevant field on the tab page Control as standard. You can change this entry at any time.

You can change this setting for the decision task in the Workflow Builder Customizing.

If you use a decision task you defined in a user decision and have text variables for substitution, you must provide the relevant elements in the task container with values via a binding from the workflow container. For further information, refer to Binding Definition in Decision Tasks.

Secondary methods with user decision

If you use the user decision as a step for approval or release of an object, you can display the object in question as a secondary method, hence supplementing the functions of the user decision. For further information, refer to Maintenance of Tab Page Methods.

Result of user decision

If you want to store the result of a user decision in an element of the workflow container in order to use it again in a later step (for example, loop or condition), you must define a binding from the task container to the workflow container. For further information, refer to Binding Definition in Decision Tasks.

Result

The system inserts a step of the type user decision into the workflow definition. To ensure the consistency of the workflow definition, all active outcomes are inserted with the actual step, whereby every decision alternative is represented by an outcome. For each outcome, the system adds a branch in the workflow definition and puts an undefined step into this branch. To ensure the consistency of the block structure, all branches created are brought together before the next step of the workflow definition.

At runtime, this user decision is represented by a dialog work item in the Business Workplaces of its recipients.

When a recipient chooses the work item created for this step for processing in the Business Workplace, a screen is displayed with the description text and the defined decision texts and one of the alternatives offered can be selected.

The recipient can also display or create attachments and objects on this screen.