Binding Definition for Decision Tasks 

Use

In the binding definition you enter elements of the workflow container, which are to either pass values to the task container or receive values from the task container after processing.

For a user decision, a binding definition is only necessary from the workflow container to the task container of the user decision under the following circumstances:

A binding definition from the task container to the workflow container is only required for a user decision if you want to store the result or the current agent of the user decision in an element in the workflow container in order to access it again in a subsequent step.

Features

The following container elements in the task container are particularly significant for this binding:

_WI_Result (result)

The result of the user decision is available in this element as a text field after processing. Depending on the number and sequence of possible decision options, these are the values 0001 , 0002 up to nnnn .

A binding definition is only required for this element if you need this value in the remainder of the workflow definition. This may be the case, for example, if you need the value again as a indicator in a decision. To implement this, you define an appropriate element (ABAP Dictionary reference SWD_LINES-RETURNCODE ) in the workflow container to hold this user decision result.

_WI_Actual_Agent (actual agent)

If you want to transfer the agent for the user decision to the workflow container for further use, you define an element with the ABAP Dictionary reference WFSYST-AGENT there to hold this information.

Note_Reference (template for notes)

If you assign a workflow container element containing a template (business object reference SOFM ) to this container element, the agent can enter a document as an attachment at runtime, which is based on this template.

Activities

For further information, refer to Operation of the Binding Editor.