sharepoint/bot-powered-ace-preview

Public preview has ended and program is not currently active.

bot-powered-ace-preview's Issues

Bot-powered ACES are a MS Teams based solution; SPFx not involved, correct?

From earlier discussions about this feature, it was implied that this would be a new option within an SPFx ACE project, but looking at the labs, it looks like it isn't related to SPFx at all... is that correct?

Instead, it looks like it's more of a Microsoft Teams app defined within the new dashboardCards array within the Teams app's manifest.json file.

Do I have this correct, or am I missing something?

If I'm correct, makes sense as a bot-powered solution requires a web service and since SPFx is 100% client-side, it wouldn't make sense to have it defined using SPFx.

Action required: migrate or opt-out of migration to GitHub inside Microsoft

Migrate non-Open Source or non-External Collaboration repositories to GitHub inside Microsoft

In order to protect and secure Microsoft, private or internal repositories in GitHub for Open Source, which are not related to open source projects or requiring collaboration with 3rd parties (customer, partners, etc.) must be migrated to GitHub inside Microsoft a.k.a GitHub Enterprise Cloud with Enterprise Managed User (GHEC EMU).

Action

✍️ Please RSVP to opt-in or opt-out of the migration to GitHub inside Microsoft.

❗Only users with admin permission in the repository are allowed to respond. Failure to provide a response will result to your repository getting automatically archived.🔒

Instructions

Reply with a comment on this issue containing one of the following optin or optout command options below.

✅ Opt-in to migrate

@gimsvc optin --date <target_migration_date in mm-dd-yyyy format>

Example: @gimsvc optin --date 03-15-2023

OR

❌ Opt-out of migration

@gimsvc optout --reason <staging|collaboration|delete|other>

Example: @gimsvc optout --reason staging

Options:

• staging : My project will ship as Open Source
• collaboration : Used for external or 3rd party collaboration with customers, partners, suppliers, etc.
• delete : This repository will be deleted because it is no longer needed.
• other : Other reasons not specified

Need more help? 🖐️

• Email [email protected]. ✉️
• Post your questions in GitHub inside Microsoft Team in Microsoft Teams. 🗨️

General feedback on this approach

If I understand correctly, this feature is for an audience who already have a Teams app/Bot and now want to add an ACE to Viva connections.  However, they do not want to go down the path of using SPFx tool chain. I noticed you still need to add a package to the Tenant app catalog. So some knowledge of SPFx is still needed.

However, I myself have not come across this scenario yet. In every customer I have worked with who want to do custom development with either Viva Connections or Teams, they have probably had better knowledge of SPFx and are more comfortable with it. They also understand SharePoint custom development better compared to Teams or Bot development. As Viva connections is built on SharePoint, extending Viva connections via SharePoint extensibility seems easier to wrap my head around.

Also in my experience most customers or ISVs who do custom development already have products dealing with multiple services within M365. So it would be very rare that they are doing Bot Framework related things but not wanting to get their hands on SPFx dev.

I also heard in the MVP summit a few times that there won't be much investment in the Bot Framework going forward and it will only remain in a supported state. If that is the case, then I would also not recommend extending it this way to build ACEs.

So overall I personally do not see myself using the Bot Framework to create ACEs. I would much rather prefer using SPFx and the surrounding toolchain. 

Sorry for the negative words. Just wanted to provide some honest feedback and thoughts.

Bot-Driven ACEs not working on Teams

Bot-Driven ACEs not working on either Teams desktop app or Teams rich client in the browser.

Question: Update to align with Bot Builder latest 4.20.0

Hi

Just curious, was looking to bring a Teams Toolkit bot with Teams AI Library (for experimentation/learning/geeking out) into Viva Connections ACEs, just wondering if there any plans to update to align the versions? Just noticed that the later ones have security updates etc.

Also, are the any plans to continue investing here? This repo was pretty hard to find, only via a single blog post.

ACE not rendering

In the workbench/edit mode I can see the card rendering:

However when I preview/publish it it doesn't render anymore:

I see that my NGROK tunnel receive calls which look OK but I cannot view the card and interact with it accordingly.
Anything I am missing here? I followed Handson Lab 1 from https://github.com/SharePoint/BotPoweredACEPreview/wiki/Hands-on-lab-1:--Build-a-new-bot-to-power-a-card-in-Viva-Connections-dashboard from start to end

Mobile Support for Bot-Driven ACEs

Bot-driven ACEs is not supported on mobile at the moment