CA Service Management

 View Only
  • 1.  Restrict Internal Comments in Notifications

    Posted Jan 25, 2016 01:00 AM

    Hi Team,

     

    we have a requirement to restrict to send if the activity in a ticket is internal in notifications.

     

    id there any way to put if condition in message templates

     

    Regards,

     

    Anjaneya Raju E



  • 2.  Re: Restrict Internal Comments in Notifications

    Posted Jan 25, 2016 02:35 AM

    The condition cannot be put in the message template, but you can use it in a Notification Rule - it should accomplish what you need.



  • 3.  Re: Restrict Internal Comments in Notifications

    Posted Jan 26, 2016 02:04 AM

    thank you for the reply but our requirement was to not send activity logs in in email notifications if the log is mentioned as internal.



  • 4.  Re: Restrict Internal Comments in Notifications

    Posted Jan 26, 2016 04:37 AM

    Are you referring to the 'Internal' checkbox available on the default activity types (update/log comment/etc.) or you have defined a new 'Internal' field on the ticket ?



  • 5.  Re: Restrict Internal Comments in Notifications

    Posted Jan 26, 2016 04:39 AM

    yes the default internal check box.



  • 6.  Re: Restrict Internal Comments in Notifications

    Posted Jan 26, 2016 02:51 PM

    We had a similar requirement and were unable to use the Internal check box as we would have liked. The problem was the value of Internal was not available to use in an notification rule. The primary purpose of Internal is to prevent an Activity Log entry from being displayed in the Employee interface when the AEU views their ticket. To meet this requirement we use the Log Comment Activity and notification rules. If an Analyst uses Activities->Log Comment to log a comment in the ticket, then we do not send a notification. If they want that comment to be hidden from the AEU in the Employee interface, then they must check Internal. If the AEU logs a comment in the Employee interface, then we send a notification to the assigned analyst or group. If an analyst wants to correspond with the AEU, then they must use Activities->Update Status. As you would expect we rely on education to make sure this process is followed.



  • 7.  Re: Restrict Internal Comments in Notifications

    Posted Jan 26, 2016 10:36 PM

    our requirement is different..currently we are sending recent 5 activity logs in email notification. we wanted not send the activities which are mentioned as internal.

     

    is there any way to do that?



  • 8.  Re: Restrict Internal Comments in Notifications

    Posted Jan 27, 2016 03:44 AM

    Hi, you may try to use condition macro like this:

     

    object pointer; 
    send_wait(0,top_object(),"call_attr","alg","sync_fetch","MLIST_STATIC", format("call_req_id = '%s' AND type = 'LOG'", persistent_id),-1,0); 
    if (msg_error()) 
    { 
    logf(ERROR,"Error in sync_fetch '%s'", msg[0]); 
    return (-4); 
    } 
    else 
    { 
    send_wait(0, msg[0], "dob_by_index", "DEFAULT", msg[1]-1, msg[1]-1); 
      if (msg_error()) 
      { 
      logf(ERROR,"Error in dob_by_index '%s'", msg[0]); 
      return (-4); 
      } 
      else 
      { 
      pointer = msg[0]; 
      logf(TRACE,"Evaluated log entry id is %d description: '%s'", pointer.id, pointer.description); 
      if (pointer.internal == 1) 
      { 
        logf(TRACE,"Evaluated to True"); 
        set_return_data(TRUE); 
      } 
      else 
      { 
        logf(TRACE,"Evaluated to False"); 
        set_return_data(FALSE); 
      } 
    
      } 
    }
    


  • 9.  Re: Restrict Internal Comments in Notifications

    Posted Apr 27, 2016 06:49 AM

    Hello ,

    I have one question is it possible and if it is what will be the syntax for putting more than one type of activity in macro.

    Something like AND type = 'LOG' ; 'TR' ;'CL' etc............ if this is possible?

     

    Thanks in advance



  • 10.  Re: Restrict Internal Comments in Notifications

    Posted Apr 29, 2016 05:05 AM

    You can change the search for activity log to:

     

    send_wait(0,top_object(),"call_attr","alg","sync_fetch","MLIST_STATIC", format("call_req_id = '%s' AND type in ( 'LOG', 'TR', 'CL') ", persistent_id),-1,0);