Looping through DataPage D_pyWorkHistory using For Each Embedded Page
I need to log the pyMemo Property of a WO and for this I am looping through the DataPage D_pyWorkHistory and am trying to retrieve the pyMemo property for each of the pxResults. My clipboard is shown below.
.
For this, I am calling the 'For Each Embedded Page' in an activity as shown below and my step page is "D_pyWorkHistory.pxResults".
I am unable to access properties on the pxResults page and my tracer is showing the following for the above step.
I need to log the pyMemo Property of a WO and for this I am looping through the DataPage D_pyWorkHistory and am trying to retrieve the pyMemo property for each of the pxResults. My clipboard is shown below.
.
For this, I am calling the 'For Each Embedded Page' in an activity as shown below and my step page is "D_pyWorkHistory.pxResults".
I am unable to access properties on the pxResults page and my tracer is showing the following for the above step.
Not sure why Tracer is showing the following
| Note | RDB operation returned result set with 0 rows |
Q1.) As my results are already present on DataPage "D_pyWorkHistory" and I have "pxResults" page, why is my activity calling the SQL statement again?
Q2.) More importantly why is my result count zero, when I do have results on my D_pyWorkHistory Datapage for the WO.
Q3.) How do I access any property on the "D_pyWorkHistory.pxResults" page.
Any help in this regard would be appreciated.
Accepted Solution
Bank Of America
US
First Declare your Pages as shown below
Add a child to your looping step as shown below by right clicking on Loop.
This will create an inner step for the Loop. Since the StepPage is empty for this inner loop, it takes the context of the outer loop i.e D_pyWorkHistory[CaseInstanceKey:param.CaseKey].pxResults which is of type History-xxxxxx-Work.
When you hit the down arrow inside your Log Message, the History Property '.pxLatitude' should be available.
First Declare your Pages as shown below
Add a child to your looping step as shown below by right clicking on Loop.
This will create an inner step for the Loop. Since the StepPage is empty for this inner loop, it takes the context of the outer loop i.e D_pyWorkHistory[CaseInstanceKey:param.CaseKey].pxResults which is of type History-xxxxxx-Work.
When you hit the down arrow inside your Log Message, the History Property '.pxLatitude' should be available.
Intellativ Inc
US
The page in the clipboard has a parameter and so the datapage returns a finite set of results.
The page in the activity doesn't have a parameter which will be trying to pull the entire table and can timeout not returning any.
Try passing the parameter to the datapage in the step page of the activity. This should pull the data as shown in the clipboard.
Bank Of America
US
For Q3.) D_pyWorkHistory Please note that D_pyWorkHistory is of Type Code-Pega-List.
Declare this page in the Pages and Classes of your Activity
For Looping through the DataPage pass the instance as follows
D_pyWorkHistory[CaseInstanceKey:param.CaseKey].pxResults
Accenture
US
Thanks for providing the screen shots which are very helpful. I am now able to run my Activity and it is bringing back the results and the count of the pxResults ResultSet as shown in your code. However I am unable to access the properties on pxResults Page. 
HOW can I use access an embedded property as I am looping through the D_pyWorkHistory[CaseInstanceKey:param.CaseKey].pxResults (within the clipboard structure that I have)?
Can you please provide with code how I can get the embedded property pxLatitude contained in the pxResults which is under D_pyWorkHistory?
Accepted Solution
Bank Of America
US
First Declare your Pages as shown below
Add a child to your looping step as shown below by right clicking on Loop.
This will create an inner step for the Loop. Since the StepPage is empty for this inner loop, it takes the context of the outer loop i.e D_pyWorkHistory[CaseInstanceKey:param.CaseKey].pxResults which is of type History-xxxxxx-Work.
When you hit the down arrow inside your Log Message, the History Property '.pxLatitude' should be available.
First Declare your Pages as shown below
Add a child to your looping step as shown below by right clicking on Loop.
This will create an inner step for the Loop. Since the StepPage is empty for this inner loop, it takes the context of the outer loop i.e D_pyWorkHistory[CaseInstanceKey:param.CaseKey].pxResults which is of type History-xxxxxx-Work.
When you hit the down arrow inside your Log Message, the History Property '.pxLatitude' should be available.