Botpress User Interface - exporting a Bot - node-modules

I am new to using botpress and recently downloaded the botpress community edition.
I have started using the botpress community edition to create bots but they only work in the Admin UI console , how do i export them as modules or packages which can be used ?
The Admin UI isnt creating the index.js files under the data/<> directory and hence i am stuck.

Related

Can't open Bot Framework Composer from Azure Portal on Linux Mint 20.2

I have installed the Bot Framework Composer on Linux Mint 20.2. I have created an Azure Bot in the Azure portal and want to open it with the Composer. When I click on the link Open in Composer in the portal, nothing happens. If I copy the link provided into a browser tab, the browser doesn't know what to do with it. What do I need to do to make this work?

Can I publish a bot, created using bot framework .NET core template, using bot composer

I have created a bot using Template in VS 2019. I Can deploy it using Azure CLI and Directly publishing from Visual Studio to Azure. I just want to know can i deploy it using Bot framework composer or not. As I am trying to open a bot using composer but it is not letting me open it.
If you created the bot using a template from VS, then you cannot publish from Composer. Bots created outside of Composer are not compatible and therefore you will not be able to open it, nor publish it.

The app configuration in App Studio does not exist for the id 4f2c0a7d-6ab9-4594-b2b6-bec7ccd7d0e6 in the organization you are currently logged into

This question is regarding the microsoft team app.
When i try to run the app created by other developers using visual studio microsfot team tool kit,
i get following error.
The app configuration in App Studio does not exist for the id 4f2c0a7d-6ab9-4594-b2b6-bec7ccd7d0e6 in the organization you are currently logged into.
I have logged into the teams and also uploaded the app package and allowed it for all teams.
Interestingly the app id in the admins.teams.microsoft.com is always different then the one in the client.
Regards
Ashish

.BOT file not getting deployed to Azure Bot Service v4

Using Azure Bot Service with C# Bot Builder SDK v4 v4.0.7 (the GA version released September 2018).
I'm using the BOT file to store configuration settings for a GenericService and so have changed the BOT file from the default that was provided with the Azure template.
Changes were made via MSBOT CLI.
When running locally via the emulator, the bot code sees modified local BOT file and all is good.
However, the BOT is never deployed to Azure and therefore the Azure service does not see my changes (it is stuck with the default BOT file). I've deployed via Visual Studio publish and GitHub CI.
I had to manually upload the file using Visual Studio Cloud Explorer and the bot was then able to use the modified version and all is good.
Question is why is the BOT file not deployed with the rest of the bot code and how can I make sure it is deployed. Not sure if this is a bug or not?
I believe this is the fix to deploy the .bot file. In Visual Studio,
Right click on the .bot file
Click Properties
Under file properties, verify that "Copy to Output Directory" option says Copy Always.
Here's a screencap:

Publishing Office365 API app into customer's Active Directory

I have developed an ASP.NET MVC5 app for Office365 using latest update of the Office 365 API Tools for Visual Studio. The app works fine with my own development Office365 site.
I understand that Visual Studio has registered the app in my Active Directory for me.
What I don't understand is how I am supposed to allow my customers to use this app with theirs Office 365 installations.
Somehow they are supposed to register the app in their Active Directory - that is the step I don't know how to explain to them.
Is there an automated way to provision the app registration to a customer's Active Directory?
The same way Visual Studio did it when I started the development? How did it do that? Through what kind of API?
You need to set your app in Azure AD to be multi-tenant. You can do this through the Azure Management portal. (Applications > [Your Directory] > Applications > [Your Application] > Configure).
Once the app is multi-tenant, your customer can navigate to the app and log in to trigger the common consent flow. Assuming that your customer has the permissions necessary to consent and allows the app to access their data, the customer will then be able to use the app with their Office 365 subscription.

Resources