Access Control debug information identification whether each element of an Access Control granted of denied access. The elements of an Access Control evaluated?

During ACL evaluation ServiceNow uses a fixed sequence to avoid unnecessary processing.
1) The platform first verifies that the user possesses at least one of the roles listed in the rule.
2) If the role test passes, any Condition specified on the rule is evaluated.
3) Only when both the role and condition checks succeed is the Script block executed. Access-control debugging output is produced in this same order: Roles → Conditions → Script, indicating whether each element allowed or denied access.

A. Lists Conditions before Roles and Script, reversing the documented first step.
B. Places Script first; scripts never run until roles and conditions succeed.
C. Starts with Conditions, not Roles, contradicting the documented sequence.

1. ServiceNow Documentation, “Access Control rules”, sub-heading “Evaluation order” (Utah release): “The system checks required roles first, then evaluates the condition, and finally runs the script.”

2. ServiceNow Documentation, “Debugging Access Controls”, Step 6, sample log lines (Utah): shows output sequence “Role: true/false … Condition: true/false … Script: true/false”.

3. ServiceNow Documentation, “Create an access control” > “Access control components”: roles evaluated before other components.

4. ServiceNow Platform Implementation Courseware (ServiceNow EDU-CAD-PLT-2023), Module 4 “Security”: Slide 27 “ACL Processing Order – Roles → Condition → Script”.