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 ?
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.
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.