Question
Strategy giving no results
The top level wrapper strategy at the Data-Decision-Customer-Request class doesn't seem to give out any results. I have tested the sub strategy that is available at the customer class, which seems to behave as expected. This means that the issue is either in the way I am testing the top level strategy or in the way the top level strategy calls the sub strategy.
1) I am using a data transform to test the top level strategy in the "Test run" panel. In the data transform, I load a pre-defined customer in the .Customer property in the Data-Decision-Customer-Request class.
2) I have attached the context by which the top level strategy calls the sub strategy.
What am I missing here?
Many thanks in advance.
Accepted Solution
Areteans Technology Solutions
AU
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC.
Could you please provide the snapshot of the substrategy for which you are getting result and the strategy for which you are not.
Is the info provided in the Data transform correct ? Could you cross verify ?
Regards
Sibani
Pegasystems Inc.
GB
Hi Ratan,
Even better if you can record your test. and post It looks like you have one strategy with an embedded substrategy. Does every component give no results? As Sibani says, check the data transform to ensure you have set it up correctly.
Cheers, ALex
Accepted Solution
Areteans Technology Solutions
AU
Hello People,
Thanks for the quick response. I resolved the issue. I had configured it wrongly to refer to "Customer" page instead of "CustomerData" page as shown in the screenshot.
Although, another question is that why the Embedded Strategy Properties section says that the strategy can "iterate over" a "page" property? Is it to convey the meaning that one can configure a "list" type property, although when a "Page" type property is configured, Pega would still iterate over that "one" page and use that as a context to the sub-strategy?
Thanks in advance.
Hello People,
Thanks for the quick response. I resolved the issue. I had configured it wrongly to refer to "Customer" page instead of "CustomerData" page as shown in the screenshot.
Although, another question is that why the Embedded Strategy Properties section says that the strategy can "iterate over" a "page" property? Is it to convey the meaning that one can configure a "list" type property, although when a "Page" type property is configured, Pega would still iterate over that "one" page and use that as a context to the sub-strategy?
Thanks in advance.