- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2024 05:42 AM
Hi all,
So basically, I have a before BR running on case table where it assigns the incident to the created user i.e, 'Assigned To = Created By'. (it is a part of our requirement).
Now, I already have an assignment rule running on the same table to assign the case to a group 'ServiceDeskforMedia' which assigns the case as soon as a case is created.
Now the issue is because of the BR, my assignment rule is not running (basically it's not assigning to that group) and we can't delete the Assignment rule.
So, is there any alternative for the above?
Thanks & Regards,
Sreesh Surendran
ServiceNow Developer - CSM & Integrations.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2024 05:49 AM - edited 03-05-2024 05:50 AM
Hi
Below is th order of execution of BR and assignment rules, you can align the order of your BR to resolve the conflict you are facing.
- Before business rules operation with an order less than 1000.
- Before engines. The following are not executed in any specific order:
- Approval engine (for task and sys_approval_approver tables)
- Assignment rules engine (for task tables)
- Data policy engine
- Escalation engine
- Field normalization engine
- 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)
- Execution plan engine (for task tables)
- Update version engine - creates version entry when sys_update_xml entry is written (for sys_update_xml table)
- Data lookup engine inserts or updates
- Workflow engine (for default workflows)
- Before business rules: Scripts configured to execute before the database operation with an order greater than or equal to 1000.
Set the order of your Before BR less than 1000 so that your BR runs fiirst followed by Assignment rule.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2024 05:48 AM
I don't see an issue: your requirement is that it is assigned to the created by (let's not get into this requirement itself...) and you have an assignment rule that does something else and doesn't run because of your BR. So it's working as you want it to?
And if for some unclear reason you need it assigned to the created by AND that assignment group (requirement starts to make less sense), you can just add that to the BR, right? The assignment rule isn't running.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2024 05:49 AM - edited 03-05-2024 05:50 AM
Hi
Below is th order of execution of BR and assignment rules, you can align the order of your BR to resolve the conflict you are facing.
- Before business rules operation with an order less than 1000.
- Before engines. The following are not executed in any specific order:
- Approval engine (for task and sys_approval_approver tables)
- Assignment rules engine (for task tables)
- Data policy engine
- Escalation engine
- Field normalization engine
- 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)
- Execution plan engine (for task tables)
- Update version engine - creates version entry when sys_update_xml entry is written (for sys_update_xml table)
- Data lookup engine inserts or updates
- Workflow engine (for default workflows)
- Before business rules: Scripts configured to execute before the database operation with an order greater than or equal to 1000.
Set the order of your Before BR less than 1000 so that your BR runs fiirst followed by Assignment rule.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2024 09:58 PM
