Let us create result view to show the results of the search.
Go to the UI component and create one more view. Give the view name and in the second step, give node name as result and choose the BTQRSrvCon.
Just keep pressing continue until select view type step. Here choose the view type as TABLE and context node as result. Check the configurable check box.
Complete the wizard and save all entries. (Try to observe how many classes wizard will generate while saving. You can see impl class, ctxt class, cn00 class. )
We have created table view successfully.
When you see a table icon next to any context node, then it is a table type view. We can generated classes (tick marks in the screen shot).
How come Configuration tab available itself?
Well we have chosen configuration check box while creating the view.
There are another two important points we need to keep in mind.
First one is, why we have selected BTQRSrvCon as an entity ?
Answer is, every dynamic search object will give results in the form of result type objects as specified in the MODEL.
See the below screen shot. Here BTQSRVCON will give you BTQRSRVCON as a result. That’s why we choose BTQRSRVCON as an entity for our view.
Second one, why we created Result view as a table type.
Every search will result more number of records of same type. In order to display all those records, table view is the best one.
Now we have developed two views. We need to display it on the web ui. Add the view to the window in the runtime repository (chapter 21).
Make one configuration by choosing certain fields. Go to the configuration tab and create one configuration. Click on Edit and move required fields from available fields section to the displayed fields section using the arrow marks. Save the configuration once you added the fields.
Test the application and see what will happen.
It is showing only one view. Next chapter will deal with this issue
Go to the UI component and create one more view. Give the view name and in the second step, give node name as result and choose the BTQRSrvCon.
Just keep pressing continue until select view type step. Here choose the view type as TABLE and context node as result. Check the configurable check box.
Complete the wizard and save all entries. (Try to observe how many classes wizard will generate while saving. You can see impl class, ctxt class, cn00 class. )
We have created table view successfully.
When you see a table icon next to any context node, then it is a table type view. We can generated classes (tick marks in the screen shot).
How come Configuration tab available itself?
Well we have chosen configuration check box while creating the view.
There are another two important points we need to keep in mind.
First one is, why we have selected BTQRSrvCon as an entity ?
Answer is, every dynamic search object will give results in the form of result type objects as specified in the MODEL.
See the below screen shot. Here BTQSRVCON will give you BTQRSRVCON as a result. That’s why we choose BTQRSRVCON as an entity for our view.
Second one, why we created Result view as a table type.
Every search will result more number of records of same type. In order to display all those records, table view is the best one.
Now we have developed two views. We need to display it on the web ui. Add the view to the window in the runtime repository (chapter 21).
Make one configuration by choosing certain fields. Go to the configuration tab and create one configuration. Click on Edit and move required fields from available fields section to the displayed fields section using the arrow marks. Save the configuration once you added the fields.
Test the application and see what will happen.
It is showing only one view. Next chapter will deal with this issue