Subject Person field is not coming up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2022 12:20 AM
Hello, Subject Person field is not coming up on Employee Relations case form. Can anyone help me with the same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2022 12:30 AM
Hi,
share screenshot and more details
Regards
Ankur
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2022 12:33 AM
It worked now Ankur. There is a policy written for specific HR service to hide the subject person on the HR case form. Thank you!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2022 12:53 AM
However, there is an another issue that Subject Person is now visible on the form after disabling the UI policy for Employee Relations case (Report Misconduct HR Service) but for HR agent this field is non editable even if er case writer and core case writer role is provided. This is happening because of the ACL written for subject person field . Attached is the snapshot. It should work though as ACL conditions are met.
Need to know if this is happening because of cross application access? Do we need to create a new ACL from Employee Relations Application?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2022 12:55 AM
However, there is an another issue that Subject Person is now visible on the form after disabling the UI policy for Employee Relations case (Report Misconduct HR Service) but for HR agent this field is non editable even if er case writer and core case writer role is provided. This is happening because of the ACL written for subject person field . Attached is the snapshot. It should work though as ACL conditions are met.
Need to know if this is happening because of cross application access? Do we need to create a new ACL from Employee Relations Application?
