Issue with Rule Declare Expression
The R-D-E isn't getting fired by the system automatically after inputs properties are updated. It's an intermittent issue .
The use case is , while creating the new case the data is getting populated on work page from an existing case ,which is similar request.
Here the existing case is being opened on TempPage, and the TempPage data is being mapped to work page of new case by using data transform,, all input properties of R-D-E are available on work page but R-D-E is not fired.
I'm planning to go for "whenever used" ,which is not advisable.
Any idea why it isn't fired for all time ? how can we make R-D-E rule to fire for every time..
Pegasystems
US
One thing that may help is, when it DOES fire, and when it does NOT fire, go into SMA and drill down in the "declarative rules management" screens and see how your declare-expression is represented.
Also, if you go into clipboard viewer and right-click and choose "copy xml" on the page name whose contents you believe should have caused the declare-expression to fire, and do it again on the page contents that DID cause it to fire, and either windiff them or post them here so we can windiff them, that may give clues. Best would be if you BOTH compare the SMA declarative rules management AND windiff the corresponding good and bad pages. /Eric
Skandiabanken
SE
Thanks Eric for response. Definitely I'll check the suggested information above.
As per our analysis , we identified the cause and able to reproduce the issue every time if we follow the below thing.
while we are mapping the data from one page to another page using data transform, if any page property is refers to data page and the data page is being loaded freshly then R-D-E expressions are not getting fired even though input properties of R-D-E's are changed .
if data page instance is found for referenced page property then R-D-E expressions are being fired.
looks like loading the data page is preventing the execution R-D-E's.
Data Page configuration: Scope: Node
source : activity (fetching the results from Report Def).
Pegasystems
US
Hello,
That's excellent investigative work. I suggest you proceed as follows:
1) If you find that the Pega documentation is lacking in a specific area, please point that out so we can make sure it gets corrected.
2) If your understanding of the issue leads you to a sufficient local change, great! (And of course, if you share how you did it, others will be happy too who may run into the same issue.)
3) If you conclude that the issue is a product defect for which you do not find a satisfactory local change, please put in an SR.
Thanks. /Eric