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

Comments

  1. Dhanunjay18 August 2021 at 09:44

    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 dhanunjay.snow@gmail.com

    ReplyDelete

Post a Comment

Popular posts from this blog

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){...
Post a Comment
Read more

Code a pause/wait - gs.sleep or gs.wait alternative, pause script for specified seconds (timer)

Code a pause/wait - gs.sleep / gs.wait alternative, pause script for specified seconds (timer)  e.g. 10 seconds: do_sleep ( 10000 ); function do_sleep ( milliseconds ) { var start = new Date (). getTime (); for ( var i = 0 ; i < 1e7 ; i ++) { if (( new Date (). getTime () - start ) > milliseconds ){ gs . print ( 'waking up!' ); break ; } } }
Post a Comment
Read more