- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-22-2018 08:14 AM
Hello,
I have a quick question about ACL on table extending TASK:
I created a scoped application for which a have a table extending TASK to use some existing fields.
For testing purpose, I gave a user the default role created for my custom table.
Initially in the form, the field 'Work notes' was not visible.
I created a write ACL fo it as customTable.work_notes
After a refreash, 'Work notes' was still not visible.
I activated the ACL debugger and saw that a read ACL task.work_notes was failing.
So I created a read ACL for the field for my custom table and it worked.
Is this the correct way to go? I thought only creating a write ACL meant you could also read the field?
Thank you
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-22-2018 08:44 AM
HI,
What you did is right: And write, read and create ACL is different. If you just have the read permission you cannot edit the field. And without Read permission, you cannot write.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-22-2018 08:25 AM
Hi Sergio,
First of all user should have read access to see the field then only user can write. That is the thumb rule.
Mark Correct if this solves your issue and also mark Helpful if you find my response worthy based on the impact.
Thanks
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
‎08-22-2018 08:44 AM
HI,
What you did is right: And write, read and create ACL is different. If you just have the read permission you cannot edit the field. And without Read permission, you cannot write.