Close popover
Parthasarathi Roychowdhury (PARTHA209552)
Cognizant Technology Solutions

Cognizant Technology Solutions
PARTHA209552 Member since 2011 8 posts
Cognizant Technology Solutions
Posted: October 24, 2016
Last activity: January 20, 2017

when condition not working properly for Action set of an event

If in the action set, any property (say x) is set from 'Run Activity' action and x is used in conditions of the next actions in the same action set, then the conditionss are not working properly. Whether x is used in 'Other Property' condition or in when rule, nothing is working. It can be seen from tracer / clipboard that value of x is getting set properly (in pyDisplayHarness page) from 'Run Activity' action.

It is only working if 'Set value' action is used to set x into another property y and y is used in the conditions for next actions. So one extra property needs to be there with no reason.

For example in the section @baseclass!pySearchFieldWorkResponsive (Ruleset - UI-Kit-7 :03-01-01). There is one Action set added on .pySearchText property. In the first action 'Run Activity', .pyWorkIDSearchHandle property is getting set from pyWorkIDSearch activity. and from the second action 'Set value', .pyWorkIDSearchHandle is set to .pySkipOpenWorkItem property and that is in use for condition. Now instead of 'Set value', if .pySkipOpenWorkItem is set from a 'Run Activity', same conditions which are there for succeeding actions will not work.

The above testing was done in Pega 7.1.8. Just wanted to know whether this is a product bug or there is any specific reason for this.

Low-Code App Development User Experience
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.