How to control "ticket.conversation.changed" event listener... | Community
Skip to main content

How to control "ticket.conversation.changed" event listener...

  • August 4, 2023
  • 10 replies
  • 0 views
Abdul15

Hello..

I'm using "client.on("ticket.conversation.changed", func)" in my app, to capture the conversation changes..

But, I'm facing some issues in that..

That function triggers multiple times, when a single message came.. 

(ie), When user sends a message means, that function triggers multiple times (sometimes more than 40 times), so that it captures the conversation data multiple times.. Therefore, It slows down my app functionality..

So, I need to control that triggering event only once, when new message came or any conversation changes happen..

Can you please suggest any ideas to control or off that conversation listener, when function not called.. I just tried with "client.off("ticket.conversation.changed")", But, its not working..

Looking forward for solutions..

Thank you..

    10 replies

    Tipene
    • Tipene
    • August 4, 2023
    Hey, Abdul! 
     
    I've done some testing on my end and I am seeing similar behaviour to what you've described. I'm going to follow this up with the teams responsible and will let you know once I have more information.
     
    Thanks!
     
    Tipene
    Abdul15
    • Abdul15
    • Author
    • August 7, 2023

    Hi @tipene

    Thank you for looking into this and conducting the testing. I appreciate your efforts to address the behavior we observed. Please keep me updated on any findings or developments from your discussions with the teams responsible.

     

    Thank you..

    Abdul15
    • Abdul15
    • Author
    • August 9, 2023

    Hey @tipene

    Just a follow-up for my above query.. :)

     

    Thank you..

    Abdul15
    • Abdul15
    • Author
    • August 18, 2023

    Hello @tipene

    Hope you are doing well.. :)

     

    I'm following up on my above query regarding the 'ticket.conversation.changed' event listener behavior.
    kindly seeking any updates or insights you might have as we're keen to ensure the smooth functionality of our app.
    Thank you for your ongoing support.

    Tipene
    • Tipene
    • August 18, 2023
    Hey, Abdul!
     
    We're still investigating this on our end - I'll let you know as soon as I have an update for you.
     
    Thanks!
     
    Tipene
    Abdul15
    • Abdul15
    • Author
    • August 22, 2023

    Hi @tipene

    Thank you for your support till..  :)

    Please keep me updated on any findings or developments from your discussions with the teams responsible. 

    Abdul15
    • Abdul15
    • Author
    • September 1, 2023

    Hello @tipene

    Hope you are doing well.. :)

     

    Any updates on on my above query regarding the 'ticket.conversation.changed' event listener behavior.

    Just a follow-up.. :)

    Thanks..

    Abdul15
    • Abdul15
    • Author
    • October 20, 2023

    Hello @tipene
    Good day..

    Is there any update for the above issue ("ticket.conversation.changed" property is triggering multiple times).
    We have successfully launched our app in the Marketplace. Still that problem exists in our app, it reduces our app functionality.

    The problem is, we are using 2 different features in our app. And in each feature, we have used "client.on("ticket.conversation.changed", func)" property to find the latest changes in conversation..
    So, when we switch between these features continuously, it is keep on adding this property events. Which makes multiple triggers when any conversation change is happens.. 

    Is there any way to OFF this "ticket.conversation.changed" property, so that, it will not keep on adding the events.
    Or is there any other ways to solve this?

    Thanks

    Abdul15
    • Abdul15
    • Author
    • October 20, 2023

    Hello @tipene

    I have one more query regarding this "ticket.conversation.changed" property..

    We are using "TICKET.CONVERSTION.CHANGED" property in our app, to capture the conversation changes and to pick the latest user message...

    If the Agent is working on more than 1 ticket, and the Agent is currently active on Ticket2.. So, If any new message came in Ticket1, at that time "TICKET.CONVERSTION.CHANGED" property is not triggering..
    And When we make any scroll movements in the chat area of Ticket1, it triggers and finding the latest message..

    Why the "TICKET.CONVERSTION.CHANGED" property is not triggering in Ticket1, when the Agent is currently active on Ticket2?
    Is there any other property, to capture these changes in Ticket1, when the Agent is not active on that?

    Thanks..

    Tipene
    • Tipene
    • October 20, 2023
    Hey Abdul Hameed P,
     
    Just a heads up that I've opened a private ticket so we can look in to this in more detail!
     
    Thanks,
     
    Tipene
    Terms & ConditionsCookie settingsAccessibility statement