Skip to main content

Implement a 3 strike rule on incident using Flow Designer

this flow is triggered when the incident is placed on hold with on hold reason awaiting customer
this workflow runs 2 sub-flows in parallel:
- wait for condition to end the flow if the state is changed to a value other than on hold or the on hold reason changes to any value other than awaiting customer
- 3 strike flow which generates 2 sequential events:
       wait for a defined period of time according to business hours schedule, then create an event to         generate a chase up email

       wait a further defined period of time then create an event to inform the customer the incident is closed cancelled and then auto-resolve the incident

the events will need to be added to the event registry, these can then fire notifications as desired

Configurable steps


·       The above contains test values in the wait for steps; these should be updated to the correct values once moved to production


·       The final update step can be updated to reflect correct wording to add to the resolution notes


·       The notifications included in the update set should be updated to suit customer requirements (subject, body text)


·       The above schedule (8-5 weekdays) can be updated to suit

how to queue the event step


  1. Hi admin, thanks for the article.
    Recently we have implemented 3strike rule, but we are facing few issues, may i request your help in resolving the issue.
    Please reach me at


Post a Comment

Popular posts from this blog

Get URL Parameter - server side script (portal or classic UI)

Classic UI : var sURL_editparam = gs . action . getGlideURI (). getMap (). get ( ' sysparm_aparameter ' ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); } Portal : var sURL_editparam = $sp . getParameter ( " sysparm_aparameter " ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); }

ServiceNow - script include: build up the results as a JSON object (array) - example 2

function call var sCurrentGroupMembers = new <script_include> (). getGroupMembers ( group_sysid ); gs . print ( 'sCurrentGroupMembers:' + sCurrentGroupMembers ); var oGroupMembers = JSON . parse ( sCurrentGroupMembers ); gs . print ( JSON . stringify ( oGroupMembers . users )); oNewGroupMember = JSON . parse ( group_members ); var oGroupConfig = getGroupDeltas ( oGroupMembers . users , oNewGroupMember ); gs . print ( JSON . stringify ( oGroupConfig . remove )); gs . print ( JSON . stringify ( oGroupConfig . add )) output : *** Script: sCurrentGroupMembers: {"manager":"3b2649efdb0f8c10cc0652f3f39xxxxx", "email":"", "type":"33a2226edb99c340edfc7cbdae96xxxx", "description":"Created for xyz", "users":[{"user":"3b2649efdb0f8c10cc0652f3f396xxxx"},{"user":"856a8f71db3d73041b4ffc45ae96196a"},{"user":"3752771