CA Service Management

Expand all | Collapse all

Maileater VS activity log pollution

  • 1.  Maileater VS activity log pollution

    Posted Jul 26, 2016 08:00 AM

    Hi guys,

     

    Do anyone of you know if it is possible to configure the behavior of maileater regarding what it logs?

     

    Currently, when you reply to a SDM notification, it generates 3 entries in the activity log.

     

    1. Log comment : User how replied : text of the reply.
    2. Log comment : Ticket has been updated via text interface.
    3. Add an attachment : Add the reply as an attachment.

     

     

    The problems with these are :

    1. It becomes messy
    2. Here, we send notification to the assignee when someone log a comment or add an attachment. So every time the end user replies to a notification, the assignee receives three notifications ...

     

     

     

    Can we prevent maileater from logging the second one?

    Can we prevent maileater from adding the email as an attachment?

     

    Thank you.



  • 2.  Re: Maileater VS activity log pollution

    Posted Jul 26, 2016 10:24 AM

    Hi Pier-Oliver,

    The trouble with turning off some of the activity associations and activity notifications is that those are things that are at a global level.   Meaning, the "log comment" activity association/notification would have to be turned off, which would affect the notifications that you DO want to occur.  I am not really sure of a way to do this without affecting the other notifications as the type would be "log comment" for a lot of them.  The reason you are getting the attachment notification is because there is an activity notification set up for that, and you have the "attach email as attachment" option turned on in the mailbox - so that is expected.  Not sure of the best way to handle this - maybe other customers out here on the community can share their experience with you.

    Regards,

    Jon I.



  • 3.  Re: Maileater VS activity log pollution

    Posted Jul 26, 2016 10:33 AM

    Thanks for your reply Jon.

     

    This is what i was expecting.

     

    I'll wait, in case someone has a good idea.



  • 4.  Re: Maileater VS activity log pollution

    Broadcom Employee
    Posted Jul 26, 2016 04:12 PM

    Pier-Oliver, take a look at text_api.cfg in the sdm install \site folder. You may have this

    DEFAULT_LOG_CODE=LOG

    if it is, delete this line and then recycle the Text API Daemon...this should remove your second "log comment".

    Thanks _Chi



  • 5.  Re: Maileater VS activity log pollution

    Posted Jul 26, 2016 04:18 PM

    Thanks Chi, i'll give a try tonight.



  • 6.  Re: Maileater VS activity log pollution

    Posted Jul 26, 2016 05:47 PM


  • 7.  Re: Maileater VS activity log pollution

    Posted Jul 27, 2016 09:48 AM

    Thanks J_W, i'll give it a try since Chi's solution does not seems to work!



  • 8.  Re: Maileater VS activity log pollution

    Broadcom Employee
    Posted Jul 27, 2016 10:00 AM

    Pier-Oliver, sorry I didn't have an install handy to test it out...maybe it takes that as default? So can you try

    instead of remove the line totally you modify it to

    DEFAULT_LOG_CODE=ABCD

    Thanks _Chi



  • 9.  Re: Maileater VS activity log pollution

    Posted Jul 27, 2016 10:19 AM

    Changed it, killed pdm_maileater, test. Does not seems to work. I'll wait until the morning reboot tomorrow to see if it changes something.



  • 10.  Re: Maileater VS activity log pollution

    Broadcom Employee
    Posted Jul 27, 2016 10:53 AM

    you recycled maileater? I don't think that will do anything. It should be Text API Daemon not maileater.



  • 11.  Re: Maileater VS activity log pollution

    Posted Jul 27, 2016 10:55 AM

    pdm_text_nxd?



  • 12.  Re: Maileater VS activity log pollution

    Broadcom Employee
    Posted Jul 27, 2016 05:01 PM

    Yes, this one.



  • 13.  Re: Maileater VS activity log pollution

    Posted Jul 28, 2016 08:46 AM

    I was unable to update a request via email this morning with this settings. I'll give a shot to J_W's workaround!

     

    Thanks anyway Chi.



  • 14.  RE: Re: Maileater VS activity log pollution

    Posted Oct 20, 2020 11:50 AM
    Hi

    Does anyone know the new links for the KB : tec556417 
    And I wanted to read more about the Idea: Updated via EMAIL Interface , for that as well, I'm looking for the new link.

    Thanks

    Ben


  • 15.  RE: Re: Maileater VS activity log pollution

    Posted Oct 20, 2020 12:14 PM
    I'm looking to get rid of the log entry "Updated VIA email activity"
    Because when a user replies to an email, the content is already in a specific log activity (as specified in text_api.cfg) and then an email notification is being sent to the defined group in the incident or request.
    Because of two log entries, it sends email twice.
    Thanks


  • 16.  RE: Re: Maileater VS activity log pollution

    Broadcom Employee
    Posted Oct 20, 2020 12:19 PM
    Does the following KB article help

    https://knowledge.broadcom.com/external/article?articleId=117592

    ------------------------------
    Paul Coccimiglio
    Principal Support Engineer
    Broadcom Inc.
    ------------------------------



  • 17.  RE: Re: Maileater VS activity log pollution

    Posted Oct 22, 2020 03:33 PM

    It worked great !

    Actually that's not the type of customization that I really like, because it means modifying files outside of "mod" folder and having to care about it when updating. I tried finding something else for two days but could'nt do better than using what's suggested.

    Two things have to be corrected in the KB:
    1. Modifications to text_api.cfg were done in a copy of the original file. Modified instead : $NX_ROOT\site\mods\text_api.cfg
    2. There is no line like : $LOG_CODE, # This is the default Activity Notification code value in the file, instead it's $DEFAULT_LOG_CODE, # This is the default Activity Notification code value which have been changed to $CUSTOM_LOG_CODE, # This is the default Activity Notification code value

    Thanks