The figure above shows the internals of the EmpowerID Bot. The EmpowerID Bot is available on different platforms or channels, where you can interact with it for self-service identity and access management. Azure Bot Service handles the interaction of the messages from EmpowerID to the channels. Bot Service is a microservice that provides the rest endpoint or interface between the EmpowerID and the Azure Bot Service. The Bot microservice comprises of the BotFlow and ApiFlow; BotFlows are those operations in Bot that trigger a workflow in EmpowerID, whereas the ApiFlows will invoke API endpoints.
E.g., the Bot allows you to Change a Password, and this change password feature in the Bot is possible because of a BotFlow. If you are using the ask to see command “Which management roles are I a member of?“ this Bot feature will consume the API endpoints of Bot Microservice. You can develop BotFlow and ApiFlow using EmpowerID Workflow Studio like any other EmpowerID workflow and API.
...
...
One significant differentiation with EmpowerID bot is that the bot operations are not built upon Azure Bot SDK, and developers use EmpowerID libraries/components called activity to develop bot capabilities. These components get transformed into Microsoft bot elements by the Bot Microservice. E.g., We don't create an Adaptive Card. Instead, we develop BotAdaptive Card Activity, which will be transformed into an Adaptive card and vice versa by the Bot Microservice.
...
...
...
...
...
...
...
...