ITSM

[CherukuA]

importance of order number in ui policy

[Sohail Khilji]

Hi @CherukuA,

To keep it simple for explonation...

Every servicenow execution record has order field were you genereally updated a number. lets say you have 5 ui policy in incident table ,each UI policy is going to have a number like below.

UI Policy 1 -- Order 100

UI Policy 2 -- Order 200

UI Policy 3 -- Order 300

UI Policy 4 -- Order 400

UI Policy 5 -- Order 500

so here the UI policy 1 will execute 1st reason being the order value is 100 (least number will execute first, so based on the order each UI policy will execute one after the other 100 , 200, 300 and so on...)

[Runjay Patel]

Hi @CherukuA ,

Order number in a UI Policy determines the sequence in which multiple UI Policies are executed. This is crucial when multiple policies act on the same fields or elements. Lower order numbers are executed first, and the results can affect subsequent policies.

For example:
- UI Policy A (order 100) disables a field.
- UI Policy B (order 200) makes the same field mandatory.

The execution order ensures predictable behavior and avoids conflicts. Properly configuring order numbers is important for maintaining logic and functionality in complex UI customizations.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------