Question
Capgemini
IN
Last activity: 4 Jan 2016 7:59 EST
Refresh Portal Harness issue
Hi,
As a part of a larger use case, I am trying a couple of simple tests related to refreshing the harness for the pyCaseManager7 portal (OOTB portal - no customization done) and it doesn't seem to be working properly. Here are the details:
Pega version - 7.1.6
Approach 1:
1.I included a button / link in the pyPortalHeader section (which is included in the pyCaseManager7 harness for the pyCaseManager7 portal)
2.On click event of the button is configured as follows, however, when I click on the button, nothing happens (nothing shows in the tracer or fiddler)
Question - Is Refresh current harness not expected to work in this scenario?
Approach 2:
1.I included a button / link in the pyPortalHeader section (which is included in the pyCaseManager7 harness for the pyCaseManager7 portal)
Hi,
As a part of a larger use case, I am trying a couple of simple tests related to refreshing the harness for the pyCaseManager7 portal (OOTB portal - no customization done) and it doesn't seem to be working properly. Here are the details:
Pega version - 7.1.6
Approach 1:
1.I included a button / link in the pyPortalHeader section (which is included in the pyCaseManager7 harness for the pyCaseManager7 portal)
2.On click event of the button is configured as follows, however, when I click on the button, nothing happens (nothing shows in the tracer or fiddler)
Question - Is Refresh current harness not expected to work in this scenario?
Approach 2:
1.I included a button / link in the pyPortalHeader section (which is included in the pyCaseManager7 harness for the pyCaseManager7 portal)
2.On click event of the button is configured as follows. Clicking on the button, reloads the entire portal, however, the wide panel disappears and after the refresh, if I click on any of the navigation options present in the left panel, it opens up the corresponding harness in the designer studio instead of the user portal.
Question -Has anyone encountered this before?
Is there an alternative approach to refreshing the whole portal?
Thanks in advance for any kind of suggestions
Regards
Sudit
Accepted Solution
Capgemini
IN
Hi Pankaj,
The pxReqLocale shows correct value in the tracer when I trace the stream rule.
However, the rule set list in pxThread.pxSecuritySnapshot.pxRulesets does not include the localized version of the rulesets - when the individual streams for the left panel and top panel are getting refreshed.
The reason of this is - after the ruleset stack was getting changed in the pxThread page for the "OpenPortal" thread, "location.reload" was resulting in RedirectAndRun to be invoked, which was purging the thread and recreating it again (without the changed locale and with the original ruleset stack).
So, as a workaround, we have modified ApplicationProfileSetup activity to conditionally change the locale (using the setLocaleName API) for the new thread. This is now working fine.
Thanks for all the help.
Regards
Sudit
Pegasystems Inc.
IN
If you are trying to reload/refresh the entire portal, you could simply use Run Script and provide "location.reload" in function.
Let us know if this helps.
Capgemini
IN
Hi Pankaj,
Thanks for the suggestion. I will try it out and let you know.
Just curious, are the "Refresh current harness" and the "Launch Harness" actions not supposed to work when trying to reload the portal harness?
Thanks
Sudit
Pegasystems Inc.
IN
Unfortunately No in this context. You are right that Refresh Harness is the right action to use for refreshing current harness but since this is a Screen Layout container in harness, No action such as" Reload section" or "Reload Harness" would work which requires form tag which is absent in Screen Layout container.
And Launch Harness action has a different function and will load the pyCaseManager7 harness in the dynamic container area and is not correct for this requirement.
Let us know if this clarifies
Capgemini
IN
Hi Pankaj,
Thanks a lot for the explanation.
So, it seems we are left with no other option, but to try the location.reload script.
I tried this out and it did work properly and the whole harness got refreshed. However, I ran into a different issue.
I actually configured 2 actions for the on-click event:
a. Call Activity - UpdateLocaleSettings (for changing the users language for the current session)
b.Invoke the script - location.reload
After the portal refresh, I noticed that only the wide panel is getting localized (to a different language), whereas the left and the top panel doesn't.
I verified the ruleset stack - which shows the language specific rulesets at the top - and the pxReqLocale value - which is getting set properly.
Can you think of any possible reason why this could happen?
Thanks
Sudit
Pegasystems Inc.
IN
- could you please try configuring the activity (UpdateLocaleSettings) at onClick event of Launch - Harness, Replace current and share your observations, Thank you!
- also could you please share a where the button (to refresh) harness is configured.
- otherwise as Pankaj said - invoke script 'window.location.reload'
Pegasystems Inc.
IN
Strange, If wide panel is getting localized and refresh is happening properly i don't see a reason why it shouldn't work.
Can you try tracing with Stream rules settings ON and let us know if rule-set stack and pxReqLocale value is correct when top and left panel streams are getting rendered ?
Capgemini
IN
Hi Phani,
If I configure the activity - UpdateLocaleSettings - at onclick event of Luanch-Harness, replace current, following is what happens
a.The portal gets refreshed, but the wide panel doesn't show anything
b.The top and left panel gets properly localized in the desired language
c.If I click on any link - e.g. My Worklist - on the left panel, it opens in the designer studio instead of the wide panel in the pyCaseManager7 portal
The button to refresh the harness is placed in a custom section that is included within the pyPortalHeader section.
Regarding the location.reload, as I mentioned, its working fine in terms of reloading the portal, but only the wide panel gets localized and not the left or top panel.
Thanks
Sudit
Accepted Solution
Capgemini
IN
Hi Pankaj,
The pxReqLocale shows correct value in the tracer when I trace the stream rule.
However, the rule set list in pxThread.pxSecuritySnapshot.pxRulesets does not include the localized version of the rulesets - when the individual streams for the left panel and top panel are getting refreshed.
The reason of this is - after the ruleset stack was getting changed in the pxThread page for the "OpenPortal" thread, "location.reload" was resulting in RedirectAndRun to be invoked, which was purging the thread and recreating it again (without the changed locale and with the original ruleset stack).
So, as a workaround, we have modified ApplicationProfileSetup activity to conditionally change the locale (using the setLocaleName API) for the new thread. This is now working fine.
Thanks for all the help.
Regards
Sudit