Question
Tata Consultancy Services
IN
Last activity: 18 Nov 2016 6:14 EST
Reloadharness method not holding error message in top level page (pyWorkPage)
we have an button in harness(tabbedscreenflow) level (As an action button)
On button event we are performing two action
1. Calling an activity which will validate few components and set the property error message
2. Calling Refresh this section (This is inturn calling pega ootb reloadharness and this somehow refreshes my current flowaction's section alone )
The problem here is we are validating few properties on pyWorkPage(toplevelpage) and few property are validated at the embedded pages (pyWorkPage.xyzpage) Obj-validate is used. when error message is set on the property of pyWorkPage the message is erased/removed before the first step of reloadharness. whereas if the error message is set on the property of pyWorkPage.xyzpage it carries forward and after section refresh it is reflecting as error in the section property
Accepted Solution
Tata Consultancy Services
IN
For time being I resolved my issue by reloading the section, If i go for reloading the harness the edit input rule creates the problem explained above
Pegasystems Inc.
IN
Hi ,
I tried the same at my end and I see that it works fine. I added the button in a seperate section though.
I have attached screenshots of my implementation. Could you check and see if it helps?
Also, I tried this on Pega 7.2.1.
Regards,
Gisela
Tata Consultancy Services
IN
Thanks Gisel for your update. we are using 7.1.8 version
When we dig further we understand the issues was relatively to one particular property which was a Date property and has one edit Input rule like (DateTime-Calendar) associated with it . If we remove that edit input attribute this works on the scenario I mentioned below.
Some how on harness refresh this edit input removes the error message. This also work if reloadsection is called instead of reloadharness
Accepted Solution
Tata Consultancy Services
IN
For time being I resolved my issue by reloading the section, If i go for reloading the harness the edit input rule creates the problem explained above