Executor

If a standard task is executable, an user interface specific handler (see SAP Gui Handler) for the action is required. In addition, an user interface independent component is needed which builds the bridge between the user interface and the ProProcess task object. This object is called Executor. ProProcess provides the abstract class /PCH/CLA_BPF_TASK_EXEC that must be extended for each standard task. The abstract implementation contains several methods for accessing and setting data within the task.

The executor provides public methods to access customizing information and different protected methods to manipulate the status of the task including protocol, digital signature and container data.

Setup and cleanup

The executor has a very loose coupling to the runtime task business object. Therefore, before any access to the task, a connection has to be created using the method SETUP and released again using the method CLEANUP. The golden rule is to call these methods before and after any access to the runtime task business object (MO_BO_RTASK). The methods make sure, that the data of the task is invalidated only once.

Enqueueing and dequeueing

The runtime task should only be enqueued as long as necessary. When manipulating the runtime task data (see Setting data), the enqueueing and dequeueing is done automatically. In some cases, it might be useful to enqueue before the setter methods are called, because some action do not have to be performed if enqueueing fails.

Protocol and digital signature

For every single task, a protocol and digital signature is either not available, optional or even mandatory. If the status is set to "completed" or "rejected" it validates if the required information is provided. Depending on the used user interface technology and handler, the protocol and/or digital signature must not be validated when the status is set, because the user interface automatically asks the user for the required information outside of the standard task. Therefore, the handler (see SAP Gui Handler) must disable these checks by calling the methods SET_PROTOCOL/SIGNATURE_IS_REQUIRED.

Currently only SAP Gui automatically asks for the protocol and/or the digital signature.

Setting data

Data can be set by using various methods. They all have in common that they are protected and are not directly accessible from within the handler class. The standard task specific executor class must provide a public interface for setting data in the executor and internally call the various setter methods.