Friday, 24 May 2013

42.TABLE VIEW v/s FORM VIEW



Let us have a small discussion about form view and table view. 

TABLE VIEW:

We use table view, to show multiple objects which are of same type.
For ex: one service contract has many line items. 


Here to show the line items, we use table view. We bring important fields of line item together and display it. As we know that even a single line item will have its own information. So we make one particular field as a hyperlink and provide ability for user to navigate to other pages where he can see detailed information of line item. 

This provides readability for user. Just imagine if we decide to show each line item as form view on service contract page. 10 line items will easily take up entire space on page. 

If there are two objects A and B. if the relation cardinality is 1….n, then A will be shown as a form view and table view will be used to show B. This is just a hint.

FORM VIEW:
It is used to display the most important information of an object by taking information from various related entities. 

For ex: if you look at service contract details, there we can see service contract id, its description, its main partners, its status, created date and end date…etc .

It will give you just an over view about service contract. 

TABLE VIEW

FORM VIEW
It can have more than one context node. However only one context node will be base for table view.

It can have many context nodes.
Context node class has ‘CL_BSP_WD_CONTEXT_NODE_TV ’ as its super class.

Context node class has ‘CL_BSP_WD_CONTEXT_NODE’ as its super class
Chtmlb: configCellerator or chtmlb:configTable tag is used for its configuration.

Chtmlb:config tag is used for its configuration in the .htm page.
New attribute should be added to the existing context node which is base for table view.
New attribute can added to existing context node or a new context can be created with the new attribute




No comments:

Post a Comment