Use PDIs? Take our 5-minute survey to help shape the PDI roadmap.

I have a BR which is high risk should i modify it?

NeethuB
Tera Contributor

We have an OOB before query Business Rule (Order: 100) on the sys_user table that restricts access to inactive users. Currently, only admin and specific privileged users can view inactive user records. As a result, tickets (such as RITMs/Incidents) raised by inactive users display "Security constraints prevent access" for other users because the requester record is inaccessible.

Our requirement is to allow IT fulfillers to view tickets raised by inactive users while maintaining appropriate security.

Would you recommend:

  • Modifying the existing OOB Business Rule to include the required IT roles, or
  • Creating a custom Business Rule that overrides or supplements the OOB logic?

What would be the recommended approach to achieve this while following ServiceNow best practices?


Business rule code:
Condition: gs.getSession().isInteractive() && !(gs.hasRole("admin") || gs.hasRole("user_admin") )
Code: 

current.addActiveQuery();



1 ACCEPTED SOLUTION

Ankur Bawiskar
Tera Patron

@NeethuB 

1st question how inactive users are raising the Request?

share complete details

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

5 REPLIES 5

@NeethuB 

then are you saying there is 1 user variable which refers to sys_user and the user is unable to select inactive users in that variable?

you want them to select inactive users there?

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader