How to querying records on HR Cases under a CoE if the user is not part of the security policy?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi All,
We have a record producer that creates specific HR Cases under a specific HR Service. The record producer has a script that calls a subflow queries the HR Case table to find out if another case with the same HR Service is open for the same subject person selected and they will be stopped from submitting a duplicate.
We did it this way so that we can set the subflow to run with the sn_hr_core.basic role so that it can query the HR Case table and return if there is already a case that has the same subject person and HR Service or not.
However, we are currently in the process of adding COE Security policies to this HR Service and due to this, unless the user who opens the first ticket is the same as the one who is trying to submit a duplicate, the subflow is not able to query records that are opened by others even though it has the same HR Service and Subject Person as the duplicate that will be submitted.
How should we go about making the check of whether there is already a case opened for the specific subject person and HR Service once the COE Security policies are in place? We won't be able to create a group and add it to the COE Security policy as well and we would like to keep it so that the people can only see the cases they raised themselves.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
41m ago
How are you querying the records? GlideRecord won't consider the security rules, but GlideRecordSecure will. Additional, breaking functionality into further sub flows can allow you to change the context from user to system, if you need to elevate for a specific use case