Unable to hide the modules in Page blueprint without getting Error 401 - Unauthorized access
search cancel

Unable to hide the modules in Page blueprint without getting Error 401 - Unauthorized access

book

Article ID: 421704

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

In Classic UI we can just display the portlet to which user has access on a dashboard. When these portlets are configured via Channles in New UI, it gives Error 401 - Unauthorized if user does not have access.

For example, in a scenario where there are channels C1, C2, C3, C4 configured on Page module.

  • If user is part of T1 GROUP, then he needs to see T1 page and only C1,C2 channels.
  • If user is part of T2 GROUP, then he needs to see T1 page and only C1,C2,C3 channels.

A business rule can be used to hide channels configured as module using 'Access Groups' condition to overcome 401 error. However, the access management doesn't work as it is in Classic.

  • Rule1: Access Group= T1, Hide Modules C3 and C4
  • Rule2: Access Group = T2, Hide Modules C4

If a user is part of both the groups (T1 and T2) this is how the behavior is:

  • In classic UI, C1, C2 and C3 channels are displayed is user is part of both the groups.
  • In New UI, the system will do a union and hide both C3 and C4 modules.

 

 

Resolution

We suggest transitioning to reporting in the New UI rather than continuing with the Classic Portlet via channels. The new reporting workspace offers a more efficient and scalable alternative for presenting user-specific data and modules, mitigating the need for intricate business rules to control channel visibility.