V5.5 Portal to V7 Portal Conversion
Hi
We recently converted our application from V5.5 to V7, but because of time constraint continued to use 5.5 Portal. Now we are planning to use V7 Portal. The challenge we face is in 5.5 there were lot of options provided to users like reports, utilities to update tables etc on the portals using gadgets which is a HTML code that triggers activity which calls List view for reports or harness for Case updates etc.
For our V7 conversion, Reports can be created using report definition. how will the utilities be converted? In short how are gadgets converted in V7 portal? Whats the best approach?
Attaching some screens for reference from V5.5 portal and gadget.
Pegasystems Inc.
IN
Hello
Most of the out of the box gadgets that we used to work with in V 5 ( e.g : getReportsByName or AssignmentMonitoringReports ) are all now available in OOTB way in form of short cuts . So you need to open the pyCaseManager portal and see how the report tabs are configured and check how many of them can be reused for your application.
If you have done any customization ( customized gadget ) then i dont think we have any way to automatically convert them . It is better to redesign them so that your end user can enjoy the latest features of UI .
@Dhev any thoughts ?
BNYMellon Technology
IN
Thanks Santanu.
We create a category and when we create a report definition, we add to that category. This way we create all reports.
Can you explain in steps how to re-design of a customized gadget? Cant we use the existing Data-Gadget rule in Pega 7 portal?
BNYMellon Technology
IN
Saw this in PDN. "Fixed portals enhanced for IE10 and IE11" - An enhancement has been added to the system to ensure portals will render accurately in IE10 and IE11.
https://collaborate.pega.com/question/prsysupdatescache-not-updating-prpc72
Can any one throw light on this? will fixed portal work fine in IE 11 if we upgrade Pega 7.1.6 to 7.1.7?