Tab browsing inside a single application
Hello,
Inside the designer studio one can open multiple objects / activities / etc.... inside the same browser tab. But Inside all the OOTB pega application, the end user can open only one single object. if end user open a different browser tab, the different tabs sync between each other leading sometimes to a loss of work.
Thus how can we implement the In App tab browser safely without breaking the architecture and allowing for future upgrade compatible Application.
If this is not feasible in te OOTB app? why do we still have it in the designer studio? and why do we still have it in the support portal of pega itself, msp.pega.com ?
Hello,
Inside the designer studio one can open multiple objects / activities / etc.... inside the same browser tab. But Inside all the OOTB pega application, the end user can open only one single object. if end user open a different browser tab, the different tabs sync between each other leading sometimes to a loss of work.
Thus how can we implement the In App tab browser safely without breaking the architecture and allowing for future upgrade compatible Application.
If this is not feasible in te OOTB app? why do we still have it in the designer studio? and why do we still have it in the support portal of pega itself, msp.pega.com ?
Siemens
IN
Hi,
You can use a tab group layout in your implementation. Make the first tab as home and use the second tab as a dynamic container.
So everytime you try to open a new item, it will open as a new tab.
Hope that helps.
Murex
LB
Hello,
Thank you for your reply,
Do you think this is something that is recommended to customize this way? especially for mobile usage and will it break any upgrades if you are building on top of an OOTB Pega application?
Previously we were warned by LSA advisor in another implementation from customizing this as it will break the default pega behavior and put at risk any further upgrades
Thank you
Elie
Siemens
IN
Hi Elie,
Recommendation is always to go OOTB way, but this is a flexible design option and a lot of customers use it this way, including us in our mySupportPortal.
However We do support this design and user customization to portals using OOTB rules, thats why case manager harness is an open rule.
When upgrading to 8.1 tab group has been deprecated and tagged as legacy, So as tab repeating layout, but the functionality remains the same. It is recommended to use the newer dynamic layout group. However you can still use the legacy components such as tab group in your implementation.
You can learn about all the layouts and recommendations in more detail using the UI Gallery feature.
Hope that helps.
Murex
LB
Thank you Faizan,
One question though, the recent section is a potential multitab thing. espeically that the previously opened objects are not closed automatically by Pega.
Don;t you think that Pega should provide the recent tabs as an horizontal layout where the devs can use it as a previously opened tabs?
Thank you
elie
Pegasystems Inc.
IN
Hi,
Use the Dynamic container in multi doc mode instead of the single . It will not relpace the current screen and will open it in a new tab. Aslo The maximum number of tabs too , can be configured in the Dymanic container setting.
Murex
LB
Hello,
Thank you for your reply,
Do you think this is something that is recommended to customize this way? especially for mobile usage and will it break any upgrades if you are building on top of an OOTB Pega application?
Previously we were warned by LSA advisor in another implementation from customizing this as it will break the default pega behavior and put at risk any further upgrades
Thank you
Elie