Defining a loop over page list in pyWorkPage
Pegasystems Inc.
US
You almost never would use “For each page”. In most situations you would use “For each embedded page”. When using this looping option, within the “step page” field you are required to specify a Page-type List Property. A Page-type List Property is either a PageGroup, such as .pyWorkParty, or in your case a PageList such as .Assets.
Your Activity runs in the context of a pre-existing step page – for example “pyWorkPage” – so you do not need to say “Primary.Assets”. And you should avoid hard-coding a page name such as “pyWorkPage” – it is unnecessary. This is the same concept as Object-oriented Programming where methods are executed in the context of the Object’s “this” reference.
In your screenshot you configured a loop but did not enter anything in the “step page” field so you either used “For each page” or a “for 1-to-N” counted loop. If you want to call an Activity inside the loop and want the called Activity’s step page to remain “Primary” you would use “for 1-to-N” but then would need to pass the loop index to that Activity to tell it what data to process, e.g., .Assets(param.LoopIndex). When looping, the loop counter is param.pyForEachCount. Be very careful not to define a look within a loop as param.pyForEachCount will overwrite itself.
To test whether a List is empty you would all a Function such as @SizeOfPropertyList(). The argument to the Function can be any List Property such as .Assets, D_AssetsList.pxResults, .pyWorkParty, or even a ValueList Property.
Hope that helps.