In previous releases, an action box transaction was tied to its presentation layer (tab page control) and could only be called from the pushbuttons in the action box. It was not possible to call action box transactions from other components. Therefore, a new approach has been implemented which splits the action box into two parts, a visible action box and a hidden action box. The communication between these layers is handled via events in the program.
De-coupled action box functionality makes it possible to execute action box transactions without the action box tab page visible component. action box transactions can be called from other custom developed visible components or from the new application area component (see release information New Application Area Component).
It is also now possible to define a transaction in the action box as an HTML session.
Visible Action Box Customizing:
The action box customizing (transaction EWFC0) has been extended to allow HTML transactions. The five ways for defining a call are Business Object Repository Method, Workflow Task, CATT session, BDC Session and HTML Session.
New Hidden Component for Action Box:
A hidden action box component is now a required hidden component in all frameworks with a visible action box.
When creating a new framework, the user will need to add a hidden action box component if a visible action box component is assigned to the framework. There is no customizing required for the hidden action box component.
This hidden component will be automatically added to all existing frameworks with an action box during the upgrade process.