You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…hannel support (#27)
### Summary & Motivation
This PR focuses on decoupling the AI Agent from the Microsoft Teams
integration to enable multi-channel support. Previously, the AI Agent
was tightly coupled with Microsoft Teams, which limited its ability to
interact on other platforms. By splitting the integration, the AI Agent
can now respond to users on additional channels like Slack or the
website.
The primary enhancement introduced in this PR is the use of an
`IAIChannelResponder`. A resolver has been implemented to determine
which channel a user is interacting with, based on the incoming API
request. The AI Agent can now respond via the appropriate
`IAIChannelResponder` for platforms such as Microsoft Teams, Slack, or
other channels.
### Atomic Changes
- Move Microsoft Teams integration from Core to Api project
- Use ConversationState of Bot Framework for maintaining DialogState
- Split State and StateStorage to decouple AI Agent and Microsoft Teams
Integration
- Use AIChannelResponder to allow AI Agent to respond on multiple
channels
- Add dedicated project for Microsoft Teams integration
- Change calendar-assistant conversations endpoint to microsoft-teams
- Remove EventCreationConfirmations after event has been created
### Checklist
- [x] I have added a Label to the pull-request
- [x] I have added tests, and done manual regression tests
- [x] I have updated the documentation, if necessary
---------
Co-authored-by: Thomas Jespersen <[email protected]>
Tasks
https://www.treblle.com/features/api-analytics
https://youtu.be/c4AJlZeX2fE?si=kND5nK3uoo74JU-z
The text was updated successfully, but these errors were encountered: