Posted: 13 Oct 2015 2:55 EDT Last activity: 6 Jul 2017 4:59 EDT
Is there a way to render Page lists in to tables dynamically without using Grid Repeat Layouts ?
As part of custom requirement, we are triggering dynamic SELECT query (as per the user conditions) to external table to get respective properties/fields in the response.
For Example :
If Option A is selected in dropdown and clicked Submit ==> application triggers SELECT CaseID, CustomerName, ApplicationName from TABLE_A
If Option B is selected in dropdown and clicked Submit ==> application triggers SELECT CustomerEmail, CustomerPhoneNumber, ApplicationName from TABLE_B
These fields are stored in the form of Pagelist. We have tried below approaches to display the fields dynamically, but each one has its own limitations of reusability.
Create a HTML Fragment and use JSP tags to render the properties in the form of table.
Able to loop PageList using <pega:forEach> tag, but unable to display the properties in each page dynamically without valid property reference.
$This-value argument in <p:r> is displaying the values of the properties without property reference, but the order in which these fields are getting displayed is not constant.
Unable to use $This-value for PageList, as this is working fine only for a Page but not Pagelist.
If referring the property in the form, we need to create the property in the class. This is not allowing to create a reusable HTML fragment , as we need to create set of properties for each SELECT query.
Create GridRepeatingLayout and refer the pagelist to display.
Need to create all the properties that we receive from response and associate them to the property fields. No reusability, as we need to create individual layouts for each response.
Can any one suggest if there is any way to render the response fields (Readonly) in to a table (as shown below) without creating property references. Therefore making that reusable for all the responses we recieve.
Like for Option A :
Like for Option B:
Customer Phone Number
Hope I am clear with my above description. Please let me know if you need any details.
Would it be possible for you to create two separate layouts (or sections), one each for option A and B and add visibility conditions based on whichever is clicked (assuming that the selected option value is available in the clipboard)?
We have evaluated this option as well, but for each layout or section , we may need to create the gridrepeatinglayout with appropriate property references and visible when conditions.So, we need to create all the properties and sections for each options. These sections may grow with number of Options user requests.
Please let me know if my explanation of scenario is different from the idea you shared.
Select this check box to create a dynamic column in the grid, sourced from the Report Definition. At runtime, the grid generates the columns contained in the specified Report Definition. The grid columns display as they are defined in the Report Definition; for example, the column name, heading, width, format values, and show/hide settings, display as defined in the Report Definition source.
The runtime display automatically updates when the Report Definition changes; there is no need to update the section containing the grid.
A dynamic column is added in the section at design time. You can add static columns before or after the dynamic column in the grid.
If you want to specify a virtual Report Definition page, a clipboard page of typeRULE-OBJ-REPORT-DEFINITION, select this check box. The Virtual Report Definition Page field displays.
Specify virtual report definition
Displays when the Source of the grid is a Report Definition and the Create grid dynamically check box is selected. There are two options.
Select By Name to use the pagination format as configured in the report definition.
Select By property reference to specify the name of a clipboard page of type RULE-OBJ-REPORT-DEFINITION. When specified, the grid uses the report definition specification in this clipboard page, rather than the one specified in the Report definition bound as the grid source.
Using this technique, you can display columns that are hidden in the report definition, hide columns that are visible, and make subtle changes to the presentation.
my requirement is to convert a section in to PDF. i have some tables in it, which im getting values from a pagelist, in section im able to create tables using GridRepeatingLayout, but while converting it into PDF im not able get the table structure, only values r coming in PDF not the table. plz help me with it.
This comment has been branched out as a new node and the new thread can be followed here