New record producer, assigned users are not able to edit the case

bigbacon
Giga Guru

I am not sure what I did wrong here. 
We created a new HR service and record producer to go along with it. it all looks setup similar to others that all use the sn_hr_core_workforce_admin table. The problem is with the cases created with this new record producer/service, the users assigned to the case are not able to modify anything, it is as it is all read only. Any other record producer/service that submits to the same table is fine.

What did I miss with this new producer/service that is stopping this from working? The users have roles that are in the ACLs for the workforce table. 

1 ACCEPTED SOLUTION

bigbacon
Giga Guru

I figured it out...it took a while....

 

Center of Excellence security, or in the menu its "COE Security Configuration". There was no security option setup in the COE for the new service to allow write to the table through the case. Once one was created with the appriopriate groups with write access, it worked as it should.

View solution in original post

13 REPLIES 13

Medi C
Giga Sage

Hi @bigbacon,

 

Is it the same for admins? Did you check if any ACL is blocking the write access? Client script or UI Policies?

Could you share some screenshots? 


If you found this helpful, please hit the thumbs-up button and mark as correct. That helps others find their solutions.

No admins like myself can modity the cases. Its as if just cases from this record producer are affected. Others  that all touch the same underlying table and the parent sn_hr_core_case table are fine.

I'm not sure what screen shots to send you. Is there a way to turn on a debugger to see maybe what is missing or causing this while impersonating a user?

 

I would assume if an ACL was blocking write access to the case, it would be across all cases that touch those tables.

Medi C
Giga Sage

@bigbacon,

 

What happens to the cases created directly on the table with the same users?

Please Debug Security Rules and share the results. For a better results, you can clear the logs when debugging impersonate and refresh an affected case.

MediC_0-1742427855897.png

 

 


If you found this helpful, please hit the thumbs-up button and mark as correct. That helps others find their solutions.

The other odd thing is, in our dev and test instance, it is fine.