Suggestion: Enabling two-way messaging for large-scale-notifcation Teams sample

[AmirHamzahR]

Reference

Based on this Large Scale Notification GitHub repository

What I've done so far

I was using this sample for disaster communication in Teams. Currently, I have added a way for the admin to tailor the HTTP message payload. In addition, the user can also respond towards the given notification message on the Teams chat.

Problem

However, the current architecture specializes in sending one-way messages to a large number of users. The incoming messages by users will be blocked in the process when trying to do two-way communications. I was having issues with decoupling it to front-end and back-end.

From my research, it seems that the blocking is caused by this section of the code:

// enqueueTasksForInstallationsActivity.ts

// this is dependent on the bot, what should I replace it with?
import { notificationApp } from "../internal/initialize";

const installationResult =
      await notificationApp.notification.getPagedInstallations(
        maxPageSize,
        token,
        false
      );
    installations = installationResult.data;
    token = installationResult.continuationToken;
 
    if (installations.length === 0) {
      break;
    }

Has anyone tried on this issue?

Thank you.

[AmirHamzahR]

Any update on it?

[nliu-ms]

Hey @AmirHamzahR , sorry for the late reply, I will investigate on this sample and get back to you.

[nliu-ms]

Hey @AmirHamzahR , all you need to do is to listen user's message, customize your own logic and send the activity back. You can reference to this PR: #1446 Please let me know if it resolves your issue, thanks!

[AmirHamzahR]

Hello, thank you for the suggested solution on this. I have checked your new commit, and it seems to be using AgentApplications class for it.

Previously, I have implemented a similar way to get the user's response using TeamsAcitivityHandler from botbuilder. However, the user cannot respond to the adaptive card while the bot is still sending the messages through bus queue. The only can only respond back to the adaptive card provided by the bot when all messages has been sent or when there are pauses between batches of message.

I have yet to test with your new commit. Do you think the behaviour will work differently this time since it is using AgentApplications?

[nliu-ms]

Hi @AmirHamzahR , yes I think the behaviour would be the same with Agents SDK.

[AmirHamzahR]

Hey @nliu-ms, thank you for the reply.

Do you might know what causes this and if there is a mitigation to overcome this? We had some POCs trying out by changing the waitSendActivity function and enqueueTasksForInstallation, but none of them works.

Seems like there is a precedence at play. Our guess is due to the bus queue still running. Looking forward to your insights on this.