Skip to main content

Case management: add a new 're-opened' state

Technical approach  implemented as follows:

-Added a new sys choice on State field of Case table labelled as 'Re-Opened' and with value of '2'.

-Created a new Customer Service Case Flow called 'Re-Open Case', which is responsible for the transition of state from 'Resolved' to 'Re-Opened'.

-De-activated OOB button called: 'Open Case'.

-Created a new button called: 'Re-Open Case', which will carry out the state transition specified in the new Customer Service Case Flow, as mentioned in step no. 2 above.

-Updated the existing flow formatter [sys_process_flow] called: 'Assigned' by modifying the condition field to cater for the 'Re-Opened' state as well as the 'Assigned' one, i.e. State=Assigned OR State=Re-Opened.

-Finally, updated the client script called: 'Hide Options From State Field' to hide the 'Re-Opened' state value from the drop-down list when the current state is NOT Re-Opened.

reopened correlates to 'assigned' in the flow formatter:



Comments

Post a Comment

Popular posts from this blog

ServiceNow timeout settings for virtual agent chat

  After connecting to live agent User is connected to live agent and not responding to live agent chat or distracted. The below properties controls the timeout settings, the OOB settings for reminder is [180 sec] and for cancelling the chat is [360 sec]. The job is default configured to 2 min so I believe no tweaking is required here.  Property -   com.glide.cs.idle_chat_reminder_timeout                  com.glide.cs.idle_chat_cancel_timeout Scheduled job   - Idle Chat Timer Task   https://community.servicenow.com/community?id=community_article&sys_id=1453b03bdbaad0109e691ea668961929   (ServiceNow ) 
Post a Comment
Read more

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