User with specific role can edit the Configuration Item "ci" field on alm_hardware table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Hello Team,
How to implement the above requirement ?
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Akshay Kamble (SD_Akshay)
ServiceNow Developer
LinkedIn: https://www.linkedin.com/in/akshay-kamble-1504/
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Hi @SD_Akshay ,
- You must have the admin role.
- You must elevate your privileges to the security_admin role. To do this, click the user profile icon in the top right, select Elevate Roles, check thesecurity_admin box, and
- click OK.
Navigate to Access Controls: In the Application Navigator, type Access Control and navigate to System Security > Access Control (ACL).
Create a table-level write ACL :
Click New.
Set the Operation to write.
Set the Name to cmdb_ci_computer
In the Requires role list, add the specific role that you want to be able to write to all other fields on the table .
Assign that ACL role to user who will be able to edit the Configuration Item "ci" field on alm_hardware table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
It's simple using field level WRITE ACL
Something like this, it's an easy requirement
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Thank you Ankur, Yes I know it's simple requirement, but even after creating the ACL and impersonating the itil user the field shows non editable.
The field is read only active true at dictionary level that is what I have observed and it's causing the issue. Is there any way to apply logic without making OOB changes.
I even tried to make field editable by making field active false and impersonating ITIL user still it did not worked.
Attaching screenshot for your reference.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Akshay Kamble (SD_Akshay)
ServiceNow Developer
LinkedIn: https://www.linkedin.com/in/akshay-kamble-1504/
****************************************************************************************************************
