Workflow System Elements in the Workflow Container

Use

The workflow container holds some container elements as workflow system elements. You cannot edit these but you can use them. The workflow system assigns values to the workflow system elements as standard. Each work item or associated method can read these values if you have defined an appropriate binding from the workflow container to the task container.

To avoid naming conflicts, the workflow system elements begin with "_".

Container element	Data Type Reference	Meaning, use
_WF_Initiator	WFSYST-INITIATOR	Initiator of the workflow (user name). The user name is a fourteen-character field in the structure US<Name>. If you started the workflow with Runtime Tools Start Workflow, your user name is in this element. If a workflow is started via an event, this container element does not initially have a value. However, the container element can be assigned a value via the binding from the event container of the triggering event. For this, the binding from the container element `_Evt_Creator` in the event container to the container element `_WF_Initiator` in the workflow container must be defined.
_WF_Priority		Priority of the workflow execution
_Attach_Objects		List of attachments for the workflow. Note This element is only used internally by the workflow system.
_Adhoc_Objects		List of objects inserted ad hoc (object references) Note This element is only used internally by the workflow system.
_WI_Group_ID		Object reference as grouping criterion
_Workitem		Object reference to the work item (to the workflow itself here), which represents the multistep task at execution time. All information about the workflow is available as attributes of this object, for example: Name Workflow System Administrator Creation date and time Status
_Predecessor_WI		Object reference to the predecessor work item. The container element _PREDECESSOR_WI is only available when you create the predecessor work item. The workflow container is not persisted. Therefore, you can use it for a binding for the task container, or in the expression for determining the agent. For detailed information about using _PREDECESSOR_WI, see SAP Note 903692.