Some PDIs are currently unavailable, and PDI actions are paused. View the latest updates here. Read More

How to restrict metric type on metric result table

Balakrishna_ABK
Kilo Sage

mt.png

I want to hide NPS Metric type from asmt_metric_table and make visible only to specific role so that survey viewer should only see all other metric results and not NPS metric type 
Note: even in reporting they shouldn't access this NPS Metric type

1.If acl is solution which type of acl is preferable ?
2.What if we store these results in separate custom table ?

1 ACCEPTED SOLUTION

Tanushree Maiti
Tera Patron

Hi @Balakrishna_ABK 

 

Try this :

 

  1. Create the Custom Role
  • Navigate to User Administration > Roles > click New.
  • Name the role (like  nps_viewer).
  • Click Submit.

 

2.Configure a Read ACL on the Metric

  • Navigate to System Security > Access Control (ACL)>Click New.
  • Operation: read
  • Name: Select the Assessment Metric table.
  • Condition: Set a condition to isolate the NPS metric (e.g., Metric type is NPS or Name is your NPS metric name).
  • Roles: In the "Requires role" related list, add the specific role you just created (like nps_viewer) and any admin roles.
  • Click Submit.

Note: Users without the nps_viewer role will no longer see the NPS metric when viewing surveys.

 

3.Configure a report_view ACL for Reporting

To prevent users from selecting the NPS metric in reports and dashboards, add a Report View ACL.

  • Navigate to System Security > Access Control.
  • Click New.
  • Operation: report_view.
  • Name: Select the Assessment Metric table.
  • Roles: In the "Requires role" related list, add the nps_viewer role.
  • Click Submit.

Note: This prevents unauthorized users from using the NPS metric as grouping or filtering criteria in their reports.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

View solution in original post

5 REPLIES 5

Hi @Balakrishna_ABK 

 

If Query BR is working fine for your use case , that is fine.

ACLs are secure, consistent, and platform-standard.

 

Here you can go through these post to check the difference between two:

When do we use Before Query BR over ACLs? 

Query Business Rules vs. ACL - comparison

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti