Question
Pegasystems Inc.
JP
Last activity: 26 May 2016 7:28 EDT
7.2 Refresh-Section works for "Report sourced" repeat grid, but doesn't work for "Data page sourced" repeat grid.
I've configured a section containing a repeat grid which displays the search result of a report definition.
There is also a button which "refresh this section" to update search result on the screen.
Initially, the repeat grid is sourced directly by the report definition, and refresh works fine as expected.
However, the refresh button start to behave in a strange way as I changed the source of repeat grid to a data page which is intern sourced by the original report definition.
Interesting thing is the section displays same result at first time no matter it is sourced by a report definition or a data page sourced by the same report.
The tracing result shows that the parameters passed to the report definition is re-posted, however the parameters passed to the data page is not re-posted, when the section reloads.
And the reason is the generated HTML contains hidden inputs to hold params that are passed to the report definition as below HTML shows.
So, is this a known limitation of data page sourced repeat grid? or it is a product defect?
| report sourced | data page sourced |
|---|---|
|
<div class="yui-skin-sam gPercent grid-responsive-default " id="PEGA_GRID_CONTENT" pyfilterhandled="false" pysorthandled="false" |
I've configured a section containing a repeat grid which displays the search result of a report definition.
There is also a button which "refresh this section" to update search result on the screen.
Initially, the repeat grid is sourced directly by the report definition, and refresh works fine as expected.
However, the refresh button start to behave in a strange way as I changed the source of repeat grid to a data page which is intern sourced by the original report definition.
Interesting thing is the section displays same result at first time no matter it is sourced by a report definition or a data page sourced by the same report.
The tracing result shows that the parameters passed to the report definition is re-posted, however the parameters passed to the data page is not re-posted, when the section reloads.
And the reason is the generated HTML contains hidden inputs to hold params that are passed to the report definition as below HTML shows.
So, is this a known limitation of data page sourced repeat grid? or it is a product defect?
| report sourced | data page sourced |
|---|---|
|
<div class="yui-skin-sam gPercent grid-responsive-default " id="PEGA_GRID_CONTENT" pyfilterhandled="false" pysorthandled="false" currentpageindex="1" totalrecords="2" pypagemode="Numeric" pypagesize="50" focusiblegrid="true" showexpandedall="false" brodetails="false" bfiltering="true" threadprocessing="true" pytargetsection="" bhidegridhdrwhennorows="false" sorttype="" sortproperty="" editrowindex="" gpropindex="pgRepPgSubSectionListOfCasesBBPpxResults1" columnlist=".pyID .pxCreateDateTime .pyStatusWork " pydisplayselectedvaluesfirst="false " paritalrefresh="true" pypaginateactivity="" rdparams="Status1,Status2"> <input name="SubSectionListOfCasesBBStatus1" type="hidden" value="Param.Status1"> <input name="Status1" type="hidden" value="Pending-Approval"> <input name="SubSectionListOfCasesBBStatus2" type="hidden" value="Param.Status2"> <input name="Status2" type="hidden" value=""> <table width="100%" class="gridTable repeatReadOnly" id="gridLayoutTable" cellspacing="0" cellpadding="0" summary=""> <tbody> <tr> <td class="mainGridTableCell" valign="top"> <input name="pgRepPgSubSectionListOfCasesBBPpxResults1colWidthGBL" id="pgRepPgSubSectionListOfCasesBBPpxResults1colWidthGBL" type="hidden" value=""> </td> |
<div class="yui-skin-sam gPercent grid-responsive-default " id="PEGA_GRID_CONTENT" pyfilterhandled="false" pysorthandled="false" currentpageindex="1" totalrecords="4" pypagemode="Numeric" pypagesize="50" dpparams="Status1,Status2" focusiblegrid="true" showexpandedall="false" brodetails="false" bfiltering="true" threadprocessing="true" pytargetsection="" bhidegridhdrwhennorows="false" sorttype="" sortproperty="" editrowindex="" gpropindex="D_InvestigationCasesByStatusPpxResults1" columnlist=".pyID .pxCreateDateTime .pyStatusWork " pydisplayselectedvaluesfirst="false " paritalrefresh="true"> <table width="100%" class="gridTable repeatReadOnly" id="gridLayoutTable" cellspacing="0" cellpadding="0" summary=""> <tbody> <tr> <td class="mainGridTableCell" valign="top"> <input name="D_InvestigationCasesByStatusPpxResults1colWidthGBL" id="D_InvestigationCasesByStatusPpxResults1colWidthGBL" type="hidden" value=""> </td> |
Pegasystems Inc.
IN
Hello Chunzhi,
Could you please share the configuration screenshots to elaborate how parameters are being passed to the concerned Data Page?
For the testing purpose, could you please hardcode the param values and retest the scenario?
Thank!!
Pegasystems Inc.
JP
Hi Ajit,
My configuration as below.
| Report sourced repeating grid | DataPage sourced repeating grid |
|---|---|
 |
The reason for passing current parameter page is that Data page doesn't support the parameter reference syntax. I got below error, if I set Status1 to param.Status1 |
Hi Ajit,
My configuration as below.
| Report sourced repeating grid | DataPage sourced repeating grid |
|---|---|
|
The reason for passing current parameter page is that Data page doesn't support the parameter reference syntax. I got below error, if I set Status1 to param.Status1
|
The section contains repeating grid called ListOfCases and it provides two parameter Status1 and Status2.
Other sections need to display list of cases with specific status can include this section and pass the desired status value as parameters.
I've found a work around for the issue as below.
1. To carry on the parameters configure a custom section rule
2. Include the custom section at the beginning of the section ListOfCases.
Chunzhi
Pegasystems Inc.
IN
Hello Chunzhi,
Thanks for sharing the detailed information.
As you have a working solution/workaround at your end, could you please confirm if you expecting any further assistance on this issue?
Thanks!!