Posted: 13 Oct 2015 19:00 EDT Last activity: 16 Oct 2015 12:57 EDT
Problem upgrading from 7.1.5 to 7.1.9
After upgrading Pega Academy from 7.1.5 to 7.1.9 the pyCaseManger7 harness in the Data-Portal class is not rendering properly. This harness has a standard screen layout with a header section across the top, a navigation section on the left and a content section on the right. Individually, each section previews correctly. However when trying to display them all together, the header appears on the top, the nav section on the left, then it's as if someone added a bunch of newline/carriage returns and forced the content section to appear way down at the bottom of the page, far from the header or nav sections.
I have confirmed that the harness rule is correct in the portal rule, and that the harness and sections match up correctly with a known good 7.1.5 environment. I have checked all settings on each form to ensure they match with the comparable rules in the 7.1.5 environment. There are messages about updated ways to do things in Pega7, and although these will be updated soon, the harness should display without this large blank space and incorrect section rendering as it does now.
If anyone has seen this or has an idea, please let me know.
You can certainly leave this post open in the case there is another community participant who can provide more insight. But the Upgrade Center is being monitored to better respond to questions just like this.
Posted: 5 years ago
Updated: 5 years ago
Posted: 14 Oct 2015 12:04 EDT Updated: 14 Oct 2015 12:14 EDT
Could you please check your application rule form, whether UI-Kit-7:03-01-01 is added in the bottom of your application ruleset?. If the UI-Kit-7:03-01-01 is added to the application ruleset, could you please remove the UI-kit-7 rule set from your application rulesets and save the application rule form and try accessing the portal.
I believe in 7.1.5 UI-kit-7 ruleset was not there, in 7.1.9 the UI-kit-7 ruleset is introduced. I think this may also be causing you the issues.
Please let me know if this helps.
Posted: 5 years ago
Updated: 5 years ago
Posted: 14 Oct 2015 12:14 EDT Updated: 14 Oct 2015 12:41 EDT
I checked the app rule form as you stated as well as the RuleSet stack - there is no UI-Kit-7:03-01-01 RS in either.
Let me add a bit more information. When I launch the Pega Academy portal, the header and nav sections render correctly at first (except for a slight left justification issue on the nav section), and there is a pause when the content section is rendering. Then when the content section finally appears it is rendered at the bottom of the screen forcing the nav and header sections to move too far up, which causes the header to disappear and the bottom of the nav section only to appear. So you are left with a huge blank space with only part of the nav section in the upper left and the top of content section along the bottom of the screen.
I inserted a few images. The first one shows what Pega Academy looks like in 7.1.5:
The second one shows what it looks like in 7.1.9. The header and nav sections are completely missing from the screen while the content section is on the bottom. The blue section is the "carriage return/newline" blank space area. The data on the right is from the developer tools (F12):
The third image is a closeup of the developer tools data:
I have removed UI-Kit-7:03-01-01 RS from my application rule set list. Now i have launched the portal, the portal is not rendered properly as shown in the below screenshot. Team Members details is pushed towards right hand side. Later i added the UI-Kit-7 rule set to my application, then it worked fine.
Could you please try adding the UI-Kit-7:03-01-01 Ruleset to your application rule set and try?. In the mean time I will also try importing the 7.1.5 application to 7.1.9 and check whether i also get the same issue.
Thanks Gowrishankar, but the problem turned out to be JS that was in a non-auto generated section that was a part of this harness. We embedded this JS section in a dynamic layout (instead of using a section include) and this work around resolved the issue.