I have a Dialogflow agent that I would like to import into the Alexa console and ultimately deployed on the Echo. Referencing Dialogflow's documentation, it says
You will get some files in the zip archive: IntentSchema.json, SampleUtterances.baf and number of .txt files according to used entities...
(I have no entities so I wouldn't expect any.) However, my zip file did not contain the two files mentioned but rather an 'agent.json' file , a 'package.json' file and the intents folder with all my intents.
Looking at the contents and the number of intent files exported, the import of these into Alexa appears to be a lengthy process. Is this correct? Thank you in advance.
From your description, it sounds like you Exported the Dialogflow project by going to the Settings, selecting the "Export/Import" tab, and then exporting it. This does not create files that can be used for Alexa - this creates a project that you can re-import into Dialogflow.
To export for Alexa:
Select "Integrations" on the left.
Scroll down and select the "Amazon Alexa" integration.
Select the "Export for Alexa" button.
Amazon Alexa importer and exporter are no longer supported in Dialogflow from the July 23, 2020
Here is release link https://cloud.google.com/dialogflow/docs/release-notes#July_23_2020
Related
I want to use text-based integrations, which works only on default language.I want to change the default language of agent from de to EN.
My problem was solved. For those who might face the same problem, Below are steps.
Export the project as a Zip. (settings-> export/import )
Create a new Agent with the required default language.
Import the downloaded project from zip
(settings-> export/import ).
Note: there's another option of restore from zip, which will not change the default language, so don't do that.
Also, you have to change service account dependencies as we do for a new project. Thanks (solution got from try and fail, didn't have any documentation which tells the solution).
I am trying to automate a download from Azure using AzCopy(v8). In a blob we have few .zip files with prefix "BuildTools" and following with the time been modified. Currently what we do is hard-coded the /pattern to match the name of the file(newest modified time) in AzCopy command so we can download the latest version.
But I would like the script to automate sort all files with prefix "BuildTools" then only download the file with newest "Last Modified" time.
I have read the document from AzCopy(v8) and know there are flags(/MT, /XN, /XO) which related to "Modified Time" but they are not what I want.
Just wonder if anyone have any ideas on this. Thanks in advance.
if you are open to try preview capabilities i would suggest to enable Blob Verisoning and download the latest. This way you manage the logic or lifecycle on the server side. less code on your end.
Preview Blog on Blob Versioning -
https://learn.microsoft.com/en-us/azure/storage/blobs/versioning-overview?tabs=powershell
(at the moment available in few regions but i guess worth waiting)
Otherwise you can try the file or object properties via the API call which has the last modified date in there. Link below:
https://learn.microsoft.com/en-us/rest/api/storageservices/get-file-properties
User can give the input command to create a folder and chatbot automatically build folder in the PC?
You'll need to use a webhook with fulfillment that has access to your file system.
First detect the intent to build a folder as you normally would.
Enable fulfillment on the intent so that your webhook can be triggered.
The triggered function can then generate a folder (assuming it has access to your file system)
I am trying to archive my MonoTouch app and to supply it to our testers using Apple's/Xcode's organizer.
Can somebody tell me how to do that? In ObjC projects I can archive an application. But how can I achieve the same in MT/MonoDevelop?
My starting point was this documentation:
http://developer.apple.com/library/ios/#documentation/Xcode/Conceptual/iphone_development/145-Distributing_Applications/distributing_applications.html
René
The archive that Xcode provides is in the form of an .ipa file. This is a glorified zip file with a certain expected file structure.
The .ipa is made up of the following components:
A folder named "Payload", which contains the compiled
(release/iPhone) .app
a 57x57 .png icon file (which is displayed while the app is being
downloaded)
a 512x512 .png file of the icon once again - however this has to
renamed itunesartwork with no extension
iTunesMetadata.plist - this contains information about the app,
such as copyright name, genre, itemname, softwareIconNeedsShine (you
can google what information this needs).
The way I package up our .ipa, is I have a folder called "App Packaging" which has all of these components already in, and I simply update the .app file whenever we do an upload, "Compress..." then rename the file to x.ipa (OS X will ask if you want to use this extension, make sure you select ("use .ipa" !).
You can then send the file to the testers to install via itunes. If the testers are all testing on devices that are iOS 4.0+ then it is possible to distribute this over the air as well but I can go into that only if you would like me to?
EDIT - Over the air distribution
It is possible to do over the air distribution of apps as well. We use it for distribution of an enterprise app we develop but it is possible to use it for testing purposes as well. It should be noted here that in order for the app to installed, the device needs to be included in the provisioning profile you signed the app with (but you knew that already!).
In order to do over the air, you need 3 things:
the .ipa file we created earlier.
a 57x57 .png icon file (same as the one included in the .ipa preferably)
a file called "Manifest.plist"
The Manifest plist contains the following structure/information:
You'll then want to upload all of these files to your website/intranet etc. In order to download the app, you'll need to create a page that points to the Manifest.plist file and then then iOS takes care of the rest and downloads the app from the location specified in the manifest.
There is now a much much easier way. On the Project menu in MonoDevelop, choose Publish to TestFlight.
You'll need a free TestFlightApp.com account, but it works great!
Our firm has begun building MonoTouch iPad/iPhone apps for enterprise deployment.
How do I take the app and create a *.ipa file for upload to our MDM server?
An .ipa file is basically a glorified .zip file. There are a couple of routes you can go down:
Export the project to xcode and under "Build" click "Build and Archive" - fill in the appropriate details and the project should create the .ipa for you as expected.
If this isn't an option, (which it isnt for us, so this is the method I've used, to great success) you can simply create all the components that go into the .ipa and right-click, "Compress..." in Finder.
The .ipa is made up of the following components:
A folder named "Payload", which contains the compiled (release/iPhone) .app
a 57x57 .png icon file (which is displayed while the app is being downloaded)
a 512x512 .png file of the icon once again - however this has to renamed itunesartwork with no extension
iTunesMetadata.plist - this contains information about the app, such as copyright name, genre, itemname, softwareIconNeedsShine (you can google what information this needs).
The way I package up our .ipa, is I have a folder called "App Packaging" which has all of these components already in, and I simply update the .app file whenever we do an upload, "Compress..." then rename the file to x.ipa (OS X will ask if you want to use this extension, make sure you select ("use .ipa" !).
With the current Monodevelop (2.8.6.5) and Monotouch (5.2.5) it is as easy as right clicking on your project -> options -> iPhone IPA Options -> check Build ad-hoc/enterprise package (IPA) for the desired configuration.
We created a special configuration called Distribution which builds using the Distribution Certificate and In House Distribution Profile.
Luke, I like your answer and have given you the credit. I am adding some more details for my own, and others, notes.
Use SpotLight to find one of your own MonoTouch apps. Search on ".ipa".
Rename it to SomeThing.Zip
Unzip it.
You can then use the structure of the unzipped folder to edit then rezip.
Just another way to get an IPA that made it easy for me, drag your .app file onto your itunes library and sync your device. ITunes then creates a copy of the app as an .ipa file in the user/music/itunes/itunes media/mobile applications. This can then be distributed much easier than the .app file.