Resume conversation after call botConnection.end()

[microsoft]

Resume conversation after call botConnection.end()

[rainmakerho]

@stevkan , Thanks.
My temporary solution is below,
save current conversationId then call botConnection.end() and remove webchat when stop conversation.
re-create webchat when start conversation.
like BotChatUI.ts

[stevkan]

Hi @rainmakerho,

Can you provide your code so I can see how you are using the commands? Also, to verify, are you using the most recent version of the botchat.js?

[rainmakerho]

Hi @stevkan ,
I add 2 button to control stop/resume conversation.

<button onclick="stopConversation()">Stop Conversation</button>
<button onclick="resumeConversation()">Resume Conversation</button>

DirectLine set websocket to false,

const botConnection = new BotChat.DirectLine({
      domain: params['domain'],
      secret: params['s'],
      token: params['t'],
      webSocket: false
    });
function stopConversation() {
      console.log('stopConversation');
      botConnection.end();
    }

    function resumeConversation() {
      console.log('resumeConversation');
      botConnection.connectionStatus$.next(0);
    }

thanks for your help.

[stevkan]

Hi @rainmakerho,

Please see below. The code I have provided is working for me to pause/resume a conversation using BotChat.

The html stop/resume buttons take a value of true/false, respectively.

<button onclick="postButtonStop(true)">Stop Conversation</button>
<button onclick="postButtonResume(false)">Resume Conversation</button>

Clicking the buttons pass the values to the stopConversation and resumeConversation functions which set the states for botConnection.activity$.closed and botConnection.connectionStatus$.isStopped. The two functions also post messages back to the bot using back channel and the conversationMsg function.

<script>
      botConnection.activity$
        .filter(function (activity) {
            return activity.type === 'message' && activity.name === 'conversationMsg';
        })
        .subscribe(function (activity) {
            console.log('"conversationMsg" received with value: ' + activity.text);
            conversationMsg(activity.text);
        });

      function stopConversation(newState) {
        console.log('stopConversation: ' + newState);
        $.when(botConnection.activity$.closed = newState)
          .done(function(){
            botConnection.connectionStatus$.isStopped = newState;
          });
      };
      
      function resumeConversation(newState) {
        console.log('resumeConversation: ' + newState);
        $.when(botConnection.connectionStatus$.isStopped = newState)
          .done(function() {
            botConnection.activity$.closed = newState;
          });
      };
      
      function conversationMsg(msg) {
        console.log(msg);
      };

      function postButtonStop(btnValue) {
        botConnection
          .postActivity({
            from: { id: 'me' },
            name: 'conversationMsg',
            type: 'message',
            text: "Conversation paused"
          })
          .subscribe(function (id) {
            console.log('"conversationMsg" sent');
          });
        stopConversation(btnValue);
      };
      
      function postButtonResume(btnValue) {
        resumeConversation(btnValue);
        botConnection
          .postActivity({
            from: { id: 'me'},
            name: 'conversationMsg',
            type: 'message',
            text: "Conversation resumed"
          })
          .subscribe(function (id) {
            console.log('"conversationMsg" sent');
          });
      }
</script>

The pauseDialog is triggered when the 'Conversation paused' message is posted. The post and trigger happen first followed by the botConnection service being paused. The user is left in the pauseDialog with no usable connection and no secondary function to move them on. The resumeDialog is triggered when the 'Conversation resumed' message is posted. The botConnection is first re-established, then the message is posted. The session.endDialog() is called and the user is returned to the conversation where they left off.

bot.dialog('pauseDialog', [
    function(session) {
        console.log("Conversation paused");
    }
]).triggerAction({
    matches: /Conversation.*paused/i
});

bot.dialog('resumeDialog', [
    function(session) {
       console.log("Conversation resumed");
       session.endDialog();
    }
]).triggerAction({
    matches: /Conversation.*resumed/i
});

I hope this helps. This should be a good starting point for you.
Steve.

[rainmakerho]

@stevkan ,

I try your codes. Bot won't get activity when click postButtonStop's button, but webchat still polling.
Thank you.

[compulim]

Unfortunately, I am not an expert in that area. You will need to look around DirectLineJS to see how to pause the polling.

[stevkan]

@rainmakerho, I apologize for not answering. I somehow missed your response. Let me take a look and see if there is anything on polling.

[rainmakerho]

@stevkan , Thank you.

[compulim]

Worked with @stevkan offline. Looks like DirectLineJS doesn't like the idea to pause the polling. @stevkan will follow up.

[stevkan]

@rainmakerho, I was just revisiting this thread and it looks like a message I posted sometime ago never actually posted. Please accept my apology for the delay in response.

As was mentioned above, DirectLineJS doesn't have an ability to pause polling, at this time. It'm listing it as a bug, but there is no ETA on when a solution might become available.

[compulim]

Transferring this one from Web Chat to DirectLineJS.

[compulim]

Marking as dupe of #124 and resolving it over that uber-bug.