On hold state and reason awaiting caller not firing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi,
I need assistance, for some reason when an incident is placed on hold with reason awaiting caller. Nothing happens at all. The business rule is there OOB no changes have been made. I created another business rule to make sure, see below screenshot. Anyone experienced the same issue how did you resolve it?
and then the OOB
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
As far as i know, when State Onhold, sub reason awaiting caller, the customer visible become mandatory.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0789158
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0564465
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
@CarolMa6 Could you please check if there is any custom BR on the incident table which uses current.setWorkflow(false); this can prevent other BRs from triggering.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
@Sandeep Rajput I checked no business rule with current.setWorkflow(false);