Important Properties of Advanced Table

ID (mandatory) – You have to give an id to the advanced table region. This id will uniquely define the advanced table on that page.

View Instance (mandatory) – Enter the instance name of the VO on which your advanced table should be based.

Note: you cannot have two advanced table on the same page based on the same VO, until and unless the advanced tables that you are creating are view only and don’t have the capability of any type of form submission. The reason for this is that once a table action is perform on one table the corresponding VO state will be changed, hence changing the state of the other advanced table based on the same VO.

Text – you can specify any text that will appear on the top of the table.

Additional Text – you can specify any additional text that will appear once the table is rendered on the page.

Records Displayed – Now this is an important property, by default the value of this property is 10. Hence once your table has some, say 15 records to display then it will show only 10 records at once and to see the next 5 records you have to click on the “next” navigation link that comes by default on the top of the table. If you set the value to 15 the all the 15 records will be displayed at once on to the screen.

Width – This is another important property of the advanced table. Using this property you can set the width of the table on the OA Framework page once the page is displayed. Now, you can choose to enter the width of the advanced table in pixels or even in percentage. To enter the width of the table in pixels just enter a numeric value e.g. 500 or 600, once the page is displayed the width of the advanced table will be 500 or 600 pixels as entered by you. In order to enter the width of the table in percentage you just have to enter a value like 70% or 80%, now when the page is rendered the width of the table will be 70% or 80 % of the total page. Once you set the width of the table to 100% the “next” and “previous” navigation links will be displayed on top of the table. These navigation links allow to browse through other rows of the table.

Empty table text – you can define a text message that will appear if the table does not have any records to display. If nothing has been specified and the table has not been queried the “ No Search Conducted” will be displayed, but if a query has been conducted and no records were found then “No Data Exists” will be displayed.

Branding Type – Advanced table branding means that you can give a look to the table. OA Framework proved three options to brand the table.

  1. rowBranding
  2. columnBranding
  3. noBranding

By default “noBranding” option will be active.

Row Branding: Once you set the branding style in the property palette of advancedTable region and run the page, you will note that the alternative rows of the table are in grey bands of color. Even you have the option to choose the branding interval, by default the branding interval is 1 and hence alternative row is displayed in grey brand color, if you choose 2 as branding interval then the grey band row will appear after every 2 rows.

Column Branding: This is similar to row banding except that now rather that rows the columns of your advanced table will be in the grey band branding style.

No Branding: This is the default branding style that’s selected if you don’t choose other styles, in this style neither rows nor columns will be branded and all the rows and tables of the advanced table will be displayed as mentioned in Oracle BLAF.

Banding Interval – As discussed above this is the property to set the interval of the branding. By default the value will be 1.

Controller Class – If you want to have some runtime control on the advanced table then only you need to enter the controller class property for the table.

Admin Personalization – True if you want the admin to be able to personalize the region else false.

User Personalization – True if you want the user to be able to personalize the region else false.

Leave a Reply

Your email address will not be published. Required fields are marked *