Binding Definitions from Task Container 

Use

You can define bindings from the task container to the following containers:

You can allocate an expression to the elements of the target container, which refers to an element of the task container.

Features

Binding definition to workflow container

The binding is applied after execution of the work item. The binding can be defined in step type definitions that refer to a task. It is necessary if you require information for the workflow, which is available after execution of the underlying object method.

Special information on object reference

If an object is created (for example, with the method Create ) or established (for example, with the method Find ) in task processing, you must define the binding from the element _WI_Object_ID in the task container to the element in the workflow container, which can contain the object reference. Only then is this information available in the workflow and therefore for the subsequent steps.

If the workflow container contains an element which is defined with a data type reference to the same object type that is created in the referenced single-step task, this binding definition is proposed automatically when an activity is defined.

If no element with an appropriate data type reference is available in the workflow container, a suitable element is added to the workflow container and the binding entered.

Current agent: Element _WI_Actual_Agent in task container

If you want to transfer the current agent, available under the element ID _WI_Actual_Agent in the task container, to the workflow container for further use, you define an appropriate element in the workflow container to contain this information.

You create this element with a reference to the ABAP Dictionary field WFSYST-AGENT .

Result of the object method: Element _WI_Result in the task container

The result of the object method is available under the element ID result ( _WI_Result ) in the task container. You must define an appropriate element in the workflow container, if you want to transfer the result into the workflow container. When defining the container element, use the same data type reference that the element _WI_Result has in the task container.

You require the result of this activity in a subsequent step of the type loop (UNTIL) in order to formulate the loop condition.

Binding definition to role container

You define this binding in the definition of a single-step task if you enter roles on the tab page Default roles.

You must add the elements required to resolve the role to the task container in order to define a binding between these new elements and the appropriate elements of the role container.

Note that you must create a binding from the workflow container to the task container in the step definition, via which these "new" container elements are given their values.

Binding definition to method container

You define this binding in the definition of a single-step task. It is only necessary if import parameters are defined for the object type method.

The workflow system proposes this binding definition if you have specified an object method with parameters during definition of the single-step task. If new elements are required in the task container, proposals are also made for these. You can edit and confirm these proposals or reject them. For further information, refer to Rule-Based Proposal for Binding Definitions.

You can modify this binding definition. But this will usually only be necessary in exceptional situations.

Catering for the container elements _WI_Object_ID

The container element _WI_Object_ID in the task container is not incorporated into the binding definition to the method container. At runtime, the workflow system ensures that the object reference from the element _WI_Object_ID is available in the key fields in the program of the object type.

Activities

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