Botbuilder 1.0.0

[siyaod]

Objective:

Bot builder of the existing version is compatible with v4 already, but it cannot forward activities to another skill. This pull request aims to extend the bot's ability to call one or more skills, and enable root-to-skill communication.

Modifications:

1. Added new fields "Bot type", "Require an input to start bot", "Skill host endpoint", "Allowed Callers" to the configuration of bot builder.

• Bot type: indicates that a bot can be of type "root bot", "skill bot", or "none".
• Require an input to start bot: delays the start of bot builder til an input is received. It is necessary to get this option checked when some configurations need to be calculated before starting bot.
• Skill host endpoint: the skill host endpoint of root bot, for receiving activities from a skill.
• Allowed Callers: defines a set of active caller bots, from which a bot can accept activities.

If bot type is chosen to be "None":

If bot type is chosen to be "Root bot":

If bot type is chosen to be "Skill bot":

2. Added a new module "send-message-to-skill", in order to forward message from root to skill bot.

• Inside msbot-connect.js & actions.js

  Initiate claims validation Init authentication config Initiate Activity Handler Initiate skill client and skill handler Handle turn error Initiate bot adapter to receive input message

• Inside allowedCallersClaimsValidator.js and skillsConfiguration.js

  Authorize skills (to whom the activities can be sent)

• Inside skillConversationIdFactory.js

  Dependency of the skill client

• Inside botVBM.js:

  Declaration of Activity Handler logic Remember conversation state Remember the authorized skills info (appID, endpoint) Remember skill host endpoint (${HOST}/api/skills/) Remember the skill client Forward activities to an indicated skill (a method inside class)

• Inside send-message-to-skill.js:

  Call botVBM method to forward activities to an indicated skill

MS Document to refer to : https://docs.microsoft.com/en-us/azure/bot-service/skill-implement-consumer?view=azure-bot-service-4.0&tabs=js https://docs.microsoft.com/en-us/azure/bot-service/skills-conceptual?view=azure-bot-service-4.0

---

FYI retours de Johan: je t'ai listé tout ce qui doit être modifié selon moi avant le merge :

• msbot-connect.html :
• enlever l'espace inutile
• fixer le camelcase startDelayedByInput
• (optionel, si ça ne prend pas trop de temps) voir si c'est possible de mettre input à 1 si startDelayed = true
• msbot-connect.js :
• déplacer la variable server au niveau fonction plutôt que globale
• enlever node.status({}) / rajoute commentaire pourquoi node.status({})
• fixer le commentaire messaing par messaging
• enlever server.post("/api/skills/v3/conversations/:conversationId/activities/:activityId");
• msbot/actions.js :
• simplifier botbuilderConfig avec un objet contenant déjà appId et appPassword
• régler le problème de fonction sendWelcomeMessage manquante
• vérifier que allowed callers est non vide uniquement si type != none
• msbot/botVBM.js :
• supprimer console.log
• package.json:
• pourquoi v2 pour node-red-contrib-viseo-botbuilder ? la dernière version publiée = 1.0.0-alpha.6, passer à une 1.0.0 plutôt
• send-message-to-skill.html :
• utiliser skill name partout