Assigning work page name causes issues
Hi everyone,
We are seeing an issue in production where a copy of the page name is causing many Rule-Declare-Expression fired up. The code is trying to copy the page name so that it can be used by another activity . The step is using Property-Set and the code looks like as shown below.
Param.PageName = pyWorkPage
What is happening that this code is causing many RDE rules fired up (all OOTB RDE rules) as well as one of our Thread level data page rule.
I am not sure why somebody has written this kind of code to access work page properties as there are better way to access it. However I am not sure why this code is causing so many rules to get fired including loading of Thread level data page.
Any explanation would be very helpful.
Thanks.
Pegasystems Inc.
US
Hello Vivek,
I'm not sure I follow. Are you saying setting a parameter named "PageName" to the value "pyWorkPage" causes all this? I don't know off the top of my head if PageName is a reserved parameter, but if it is, that could account for why it has additional related code. If you set a parameter param.foo = "pyWorkPage" does the same sort of declarative activity happen? If so, then it is probably because pyWorkPage is definitely an internal page with special handling. I would expect that you could use that string without triggering declaratives, which is my I expect the problem is probably PageName and that you would see a similar behavior if you set param.PageName = "foo" and the page "foo" was created with associated declaratives.
Thanks,
Mike
Pegasystems
US
What is the parameter type for the parameter called "PageName" on the parameters tab of your activity? What does the java generation look like for that property-set line? These may help understand what's happening. /Eric
Pegasystems Inc.
US
Can you elaborate your use case? is pyWorkPage not available for use in the target activity? I mean we can directly refer pyWorkPage rt.