Skip to main content

Custom Table to log agent activity

for reporting on all the updates a service desk member has made during the working day
note: may be license implication of using a custom table

2 system properties
- logging enabled property (true/false)
- list of ticket types property (string ; delimited, e.g. incident;sc_task)

new table with following fields:
  ticket (reference to task)
  user (reference to sys_user)
  info (string)

business rule on TASK table, fires after insert/update
- exclude users without itil role and isInteractive=true condition, also exclude internal_integration_user=true users (condition can be amended as needed)

condition:
gs.getProperty('ticket.logging.enable')=='true' && gs.isInteractive() && gs.getUser().hasRole('itil')
script:
(function executeRule(current, previous /*null when async*/ ) {

    //--exclude technical users
    var bProceed = false;
    var currentUser = gs.getUserID();
    var ticketTypes = gs.getProperty('ticket.logging.tickettypes');
    var ticketArr = ticketTypes.split(';');
    ticketArr.forEach(function(ticketT) {
        if (ticketT == current.getTableName()) {
            bProceed = true;
        }
    });
    if (bProceed) {
        var grUser = new GlideRecord('sys_user');
        if (grUser.get('sys_id', currentUser)) {
            if (!grUser.internal_integration_user) {
                //--log the user activity
                var grLogs = new GlideRecord('u_cu_ticket_log');
                grLogs.newRecord();
                grLogs.u_ticket = current.sys_id;
                grLogs.u_user = currentUser;
                grLogs.u_info = current.operation();
                grLogs.insert();
            }
        }
    }
})(current, previous);

Comments

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 ) 

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 )){...