What is the advantage of using HIGH ORDER number in Business Rule?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2014 09:45 AM
For Example :
We have the Default Order value is 100.
Then i would like to use the Order value much greater like order value is 1000.
What is the difference between the using 100 and 1000 order?
Thanks in advance,
Dinesh Chinnadurai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2014 10:19 AM
The order <1000 and >=1000 are very important as far as when things are processed.
Execution Order of Scripts and Engines - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-26-2014 12:21 PM
As per wiki,
It is indicating the sequence in which this business rule should run. If there are multiple rules on a particular activity, the rules run in the order specified here, from lowest to highest.
In simple way,
The order value decides the execution of the Business rule.
For ex.
we have 3 BR with the order 100,200,300.So the business rule with lower value will run first(here 100) and then BR with value 200,300.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2014 01:34 AM
Hi Dinesh,
you can follow below link
https://wiki.servicenow.com/index.php?title=Execution_Order_of_Scripts_and_Engines
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2014 05:41 AM
Yup i got it,
As per Wiki,
For Before BR, Order < 1000 executes first
And then Before Engines executes here lots things happens
For example, Below i take one function happen in Before Engines
Role engine - keeps role changes in sync with sys_user_has_role table (for sys_user, sys_user_group, sys_user_grmember, and sys_user_role tables)
ROLE ENGINE done lot of works.
Now, Before BR with order >=1000 executes
Thanks for all,
Dinesh Chinnadurai.