New COE Added for HRSD and now non-hr_admins can't see any hr cases for any hr services.

[Scott Megargee]

We created a new HRSD COE for a specific HR set of services. We kept this pretty out of box - extended sn_hr_core_case table, aligned acls to match other out of box COEs (e.g. benefits, payroll). For some reason non-hr_admins are now unable to see any hr case (even though they have the requisite roles). Employees are also unable to see any of the cases they submit (even though we can validate the case was successfully submitted). They are getting a portal response of "Sorry, either the data doesn't exist or you don't have access."  Any thoughts as to what could have caused this issue? We are on Yokohama.

[Scott Megargee]

ok good news is i figured out the issue impacting access to all of the other hr services and that's been fixed. It had nothing to do with the addition of the new COE. So the new COE access remains where non-admin users can't see the records they submit after submitting on the portal and receive the "Sorry, either the data doesn't exist or you don't have access" message. 

[abirakundu23]

Hi @Scott Megargee ,

Have you mapped the new COE table to Record Producer table ?Please check.

Please mark helpful & correct answer if it's worthy for you.

[Scott Megargee]

Yes, Topic detail and topic category are created, HR criteria set, template is assigned, record producer is mapped to COE table, COE table acls updated to align with other hr services in core scope for create, delete, write, and read - sn_hr_core.case_writer, snc_internal, hr_admin, etc.  I just don't get it.

[Scott Megargee]

What's strange is our end users are able to submit the case successfully. They just can't see the portal response after submission. The message "Sorry, either the data doesn't exist, or you don't have access" is being returned. But if a user has HR admin they are able to see the case from the fulfiller/agent side.