A. Name: incident”; Permission: write; Role: itil
B. Name: incident Any, Operation: write, Permission: itil
C. Name: incident.*; Operation: write; Permission: itil
D. Name: incident None, Permission: create: Role: itil
E. Name: incident. None; Operation: create; Role: itil
Explanation:
In ServiceNow, Access Control Rules (ACLs) are used to grant or restrict permissions for performing actions on a table or field.
To allow a user with the itil role to create Incident records, the correct Access Control Rule must:
Apply to the incident table
Grant the "create" operation
Be restricted to users with the "itil" role
Breaking Down the Correct ACL Configuration:
ACL Field Correct Value
Name incident.None (applies to the table-level, not a field)
Operation create (allows creating new records)
Role itil (only users with the itil role can create incidents)
Why is "incident.None" used instead of "incident.*"?
incident.None → Applies to the entire table (for record creation).
incident.* → Applies to all fields in the table (not needed for create operations).
Incorrect Answer Choices Analysis:
A. Name: incident”; Permission: write; Role: itil
❌ Incorrect C The "write" permission allows editing existing records, but does not allow creating new ones.
B. Name: incident Any, Operation: write, Permission: itil
❌ Incorrect C There is no such name format "incident Any" in ACLs. Also, "write" does not allow record creation.
C. Name: incident.*; Operation: write; Permission: itil
❌ Incorrect C "incident.*" applies to all fields in the table, but does not apply to record creation.
D. Name: incident None, Permission: create: Role: itil
❌ Incorrect C The correct format uses "Operation: create", not "Permission: create". Official ServiceNow Documentation
Reference: ServiceNow Docs C Access Control Rules
How ACLs Work
ServiceNow Docs C Configuring ACLs for Tables and Fields Table-Level vs Field-Level ACLs
