Make HR Services invisible in the drop down picker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2023 06:51 AM
Hello,
I have a requirement that needs to make the following changes to the HR Service drop down picker to make them invisible to specific groups that I've created. I created two groups Tech Lead and Tech Associate, when any person who is a member of those groups logs on and selects the HR Service drop down they should not see any on the following HR Services I've created. "High Visibility Report" and "Unemployment" that I created under the "Employee Relations" COE. The COE Security Figuration does not provide anything to prevent them from seeing and creating the HR Service case. Thank you for any assistance you can provide. Take a look at the screenshot I have.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2023 08:30 AM
@Andre Jones there are current data resources (objects) as well as UX Client Scripts that are being used to filter based on the HR Criteria. I feel what you are trying to accomplish will impact that OOB functionality since the HR Criteria is based on the Subject person and you are basing the HR Service visibility on a group. This is not an easy answer and you will need to investigate to understand how you can maintain the OOB and still meet your requirement. Starting with the OOB UX Client scripts and Data Resources will give a good insight as to how we are filtering OOB. You will want to start by looking at the Case Create page (variant) in UI Builder for Agent Workspace for HR Case management. In addition to this, you can find the UX Client Scripts in sys_ux_client_script.list. Below is an image of some of the OOB UX Client Scripts to take a look at since these will conflict with what you are trying to do. In addition to the caveats I mentioned, do not forget that you will have to do the same for the transferring of a case so that only the HR Services you want are available on a transfer. As you can see, there are a lot of things to consider in addition to increasing the level of technical debt.
Regards,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 05:36 AM
@michaelj_sherid I noticed the UX you have in the screenshot doesn't exist in my Vancouver instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2023 06:50 AM
@Andre Jones Do you have the Agent Workspace for HR Case Management plugin active on your instance?
Regards,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-08-2023 08:44 AM - edited 12-08-2023 08:44 AM
Thanks for mentioning this @michaelj_sherid -- I do forget that some organizations are not embedded in UI form/record/list "back end" work and Workspaces are specific in their configuration.
@Andre Jones -- to be honest, you probably should have both of these solutions (in-platform/back-end/UI16/traditional as well as workspace) in place, as you'll probably have some users that don't use workspace -- that is of course, if you let them. Perhaps your organization's user management (persona management) practices are sufficient to curate the experience in a way that you don't have to worry about that....super jelly if so! 😋