Form Enhancements
Several widgets are based on the ProNovia Custom View Engine (CVE). The CVE decouples the complete layout of a widget content into an editable XML file.
To make custom specific adjustments ProNovia custom views (ProFramework Forms) have to be copied in the Z-namespace. Also widgets have to be adjusted by parameters to use these definitions. Currently, the following widgets are using the CVE.
Document data widget
Material Data Widgets
Simple data widget
If you plan to extend a custom view by new elements, a new ABAP OO class has to be created, which is responsible to provide and handle the required data. This class has to implement the interface /PCH/IF_CFW_CVE_FEEDER. It is recommended to inherit the new class from the abstract CVE feeder class /PCH/CLA_CFW_CVE_FEEDER. The following methods must be implemented to make your extensions work:
Method | Description |
---|---|
/PCH/IF_CFW_CVE_FEEDER~GET_TYPE | Returns the (technical) name of the feeder, which is used to address the Feeder. The name should be meaningful and have an obvious relation to the data, which is provided in the Feeder (e.g. MARA). You are required to use customer name space when naming customer specific feeders. |
RETRIEVE | Has to return a list of all custom view objects (input fields, checkboxes, labels,...) provided and handled by your class |
BIND_CUSTOM_VIEW_OBJECT | For every custom view object used in a layout this method is called to provide data and attributes at runtime |
IS_CONTEXT_RELEVANT | Due to the fact that multiple different objects can be displayed within one single CVE form, a data context (Business Object) is passed into the feeder. You should check and store the business object here in case the Business Object is relevant for your Feeder. E.g. if you plan to build a feeder providing customer data related to the Material Master (MARA), you need to check if you can cast the business object to BO-MARA. |
The following methods should be implemented:
Method | Description |
---|---|
INIT_CUSTOM_VIEW | This method is called once before the layout binding is evaluated. It should read the necessary data and store in global data areas. |
REFRESH | This method is called, whenever an explicit data refresh is request. It should be implemented to invalidate the above defined global values. |
Expert concepts also allow updating data, actions (link clicks, buttons), context menus and also iterative and conditional data block, which are not described here due to their complexity.
If you plan to adjust an existing custom view or if you plan to enhance view by adding new elements we highly recommend to contact ProNovia for further assistance.
© ProNovia AG | Imprint | Data Protection