
By defining the basic parameters of an action, you create an inactive object that does not yet implement any specific logic. To make the action functional, you must attach at least one callable object to it. The system calls and executes the callable object when the action starts at process runtime.
Callable object design requires certain knowledge of the services and applications that are exposed. Typically, it is a task for users with technical background; therefore, it is covered in Exposing Applications as Callable Objects .
The action's design time opens.
You must attach a callable object for execution. It can be either a callable object with a visible part, such as a Web Dynpro or BSP callable object, or one for background execution.
Attaching an object for execution is mandatory.
If the first callable object is for background execution or for a composite form, you can add an alternative callable object for execution. The requirements for this object are as follows:
At runtime, the action processor can access and complete the action in GP runtime using this callable object if the action is not completed in the background due to an error, for example. This prevents a deadlock in the process flow, as the execution continues even if the first callable object cannot be executed.
Optionally, you can attach a callable object for display. It is required to have a visible part - for example, you cannot select a callable object for background execution.
At runtime, this object is displayed if the processor wants to open the process step after it has been completed, or if a process contributor has view permissions on the action. For more information, see Granting View Permissions .
You have implemented a functional action.
Before you can activate it, you can also consolidate its parameters.
More information: Consolidating Parameters