Interface IF_WORKFLOW

Use

Interface IF_WORKFLOW is necessary for using an ABAP class in SAP WebFlow Engine. The interface contains methods that create specific prerequisites in order that the object can be used within the SAP WebFlow Engine.

Features

SAP WebFlow Engine handles all objects in the same way. Objects must be saved for a change of context. It is therefore necessary to convert object reference that can be saved persistently. In return, it must be possible to create the corresponding instance of an ABAP class from the persistently saved key.

There is also a series of components of the SAP WebFlow Engine which can display objects, for example, the Workflow Log. The relevant functions for this must be provided by the object.

Interface IF_WORKFLOW places logical brackets around the interfaces BI_PERSISTENT (instance management) and BI_OBJECT (object behavior). The interface IF_WORKFLOW contains the following methods:

BI_PERSISTENT~FIND_BY_LPOR
BI_PERSISTENT~LPOR
BI_PERSISTENT~REFRESH
BI_OBJECT~DEFAULT_ATTRIBUTE_VALUE
BI_OBJECT~EXECUTE_DEFAULT_METHOD
BI_OBJECT~RELEASE

Caution

A class that implements the IF_WORKFLOW interface can be used in any workflow. The class is automatically released for use in workflows when the interface is implemented. A class should therefore only be changed compativly after implementation (do not delete attributes, type changes, or methods). There is no where-used list with which you can determine in which workflows the class is in use.

Internal classes of an application should not implement the interface IF_WORKFLOW as otherwise this would mean every method of the class could be used in the workflow. You should therefore include the workflow functions in a further class that calls the selected methods of the internal class.