I want to release to production an integration using the whatsapp business cloud api, but the business's number has already an integration with amoCRM. Does anyone know if both tools can work together?
Related
I have basic understanding of .net and chatbot.
I wanted to integrate Amazon lex in xamarin(ios, android)app. There seems to be no example or sample. I have created chatbot from AWS platform intent and slots.
Also I wanted to use database to get query return. Any sample to integrate AWS Lex with Xamarin app would be helpful.
As I understand from your question, you already have some implementation of chatbot made with AWS services, but you are having issue on integrating it to your xamarin application to be able to use it in IOS and Android devices.
For that purpose, there is AWS Mobile SDK which happens to support also xamarin.
From their link:
https://docs.aws.amazon.com/mobile/sdkforxamarin/developerguide/Welcome.html
I also did not find a Lex tutorial directly, but a very promising quote:
Supported AWS services currently include, but are not limited to [narrow list of services]
was on the same page. I looked around, found this text:
The AWS Mobile SDK for .NET and Xamarin also allows you to use most of the AWS services supported by the AWS SDK for .NET. The AWS services specific to mobile development are explained in this developer guide. For more information about the AWS SDK for .NET, see [a link]
clicked the link and ended here:
https://docs.aws.amazon.com/sdkfornet/v3/apidocs/Index.html
and under link AmazonLex -> AmazonLexClient there was something, you probably wanted to see:
Version Information
.NET Standard:
Supported in: 1.3
.NET Framework:
Supported in: 4.5, 4.0, 3.5
Portable Class Library:
Supported in: Windows Store Apps
Supported in: Windows Phone 8.1
Supported in: Xamarin Android
Supported in: Xamarin iOS (Unified)
Supported in: Xamarin.Forms
Those 3 last let me understand that whenever you setup Mobile SDK, you get access to AWS services in Xamarin, also Lex.
Steps to install on
https://docs.aws.amazon.com/mobile/sdkforxamarin/developerguide/setup.html
mainly contain steps on how to create xamarin app and get AWS account, most important is to install the AWS Mobile SDK for .NET and Xamarin and configure it. More detailed steps are under that link.
After that the process is to follow the instructions on:
https://aws.amazon.com/getting-started/projects/bots-just-got-better-net-toolkit-lex-lambda-cognito/module-one/
like pointed in comments. I suppose once you have access to any service via Mobile SDK, the wire up of Lex may go in similar steps and no special just xamarin tutorial is not needed anymore.
It seems you are looking for both architecture and sample code for implementing AWS Lex bot with .NET backend that can be integrated with iOS/Android Frontend.
You have multiple choices here to do it
Build both chat user interfaces in iOS and Android and integrate them AWS iOS & Android SDKs to utilize the AWS LEX bot.
Just implement a bot user interface in iOS and Android app and integrate it with a .NET backend that can utilize AWS .NET SDK to integrate with your LEX bot.
I would recommend the second approach as it will save you writing the LEX integration code twice both in Android and in iOS. In the second appraoch you will be able to write a single integration for AWS LEX in .NET and that can give a unified experience across the mobile devices(iOS/Android)
Now for the .NET based backend integration with AWS LEX bot.
If you are an experienced .NET developer and you know how will you host your code then only thing that you need is the .NET API reference for AWS LEX, which can be found here
https://docs.aws.amazon.com/sdkfornet/v3/apidocs/items/Lex/TLexClient.html
But if you are not sure how to write this integration code and also not sure how the deployment will look like then you can follow the below tutorial
Bots Just Got Better with .NET and the AWS Toolkit for Visual Studio
Also, find here the architecture form the above tutorial
there is no direct solution like Amazon Lex is supported by React-native. i confirmed with xamarin team as well as AWS service one of the member. direct integration not possible.
I am in the process of writing a Voice app for Google Home (using DialogFlow) and Amazon Alexa (AWS).
Both voice apps back onto a custom .net WebAPI that serves the answers.
We have written a series of integration tests that test both the Natural Language Processing (Deriving the Intent) and also the backend service. DialogFlow provide API access to their NLP making these integration tests pretty easy to set up.
I am in the process of porting the app to Alexa via AWS and want to perform the same set of integration tests against the AWS NLP but cannot see if this is possible. Most of the testing for Alexa seems to be centered around testing Lambda functions (which we are not using). Does anybody know if it is possible to interact directly with an Alexa skill restfully?
Yes, it is possible, but a little cumbersome.
Alexa Skill Management API (SMAPI) provides RESTful HTTP interfaces for programmatically performing Alexa skill management tasks, such as creating a new skill or updating an interaction model.
You'll need to create a Amazon app to use it and send requests adding Authorization header with all requests.
Docs for implementing this can be found here
how to use AWS RDS in flutter dart code?
I went through - this post
It says -
I work on the AWS SDK team. I am not aware of any plans to support Flutter at this point. I will take this to my team as a feature request and will post back
Should I do as suggested here?
Build your own service layer using HTTP, gRPC that talks to some backend service that provides access to a data store. You can do this with Express, Rails, CloudFunctions, etc.
You can either use dart code to do HTTP/gRPC, or use Platform channel to wrap dart code around native iOS and Android code of AWS official SDK.
On another note, I'm highly concerned when you connect directly from mobile (Flutter) to database (AWS RDS). Please be aware that anything on mobile app can be reversed engineer, and your database connection credential is not safe. It's recommended to have only backend proxy, or at least severless (such as AWS lambda function) connect directly to database (not mobile or web frontend). The only exception is with Firebase Realtime Database because it has seamless integration with Firebase Authentication
I'm currently working on a assay for a school project about Google Services.
The question is not programming related, but I hope you guys could help me out.
I've done some research and a little bit of digging on the Google Cloud Platform and Google Apps for Work, but before I start to make wrong assumptions in my assay, I was hoping if you could say wether I'm right or wrong.
Is Google Apps for Work part of the Google Cloud Platform? Or is it a whole seperate service?
I couldn't find any connections between the two, but shouldn't Google Apps for Work a service of te Google Cloud Platform?
Thanks in advance!
Tristan
Short: No it's not part of Google Cloud platform.
Long: Google Apps for Work contains products such as Gmail, Google Drive, Google Hangouts, Google Calendar, and Google Docs. You will probaby be familiar with at least some of those. These can all be used by individuals at home, but if used in the 'for work'-context they offer some extra features such as custom domains and support. While these are all running in the cloud, they are not technically part of Google Cloud platform.
Google Apps for Work can be seen as a SaaS-product (Software as a service), while Google Cloud platform is more of a PaaS-product (Platform as a Service). While Apps for work lets you use the software written by Google (Gmail, docs,...), Google Cloud Platform allows developers write custom applications which run on the Google cloud.
Applications written on Google Cloud Platform can however be used together with the Apps for Work part. For example you could use your Apps for Work account to log in to a custom application written on GCP, or you could access your emails or from within your custom application stuff like that.
Small note, GCP also contains stuff like Google Compute Engine, which is more of a IaaS (Infrastructure as a service). However this will still be used for custom development by the user, but it gives the developer more freedom.
Background:
I'm building a small application that will be run daily, pulling data from our own in-house databases and sending it over to our corporate Salesforce instance. I've built a custom object (called Marqui_Instance) in our Salesforce instance to house the data. The app will be creating a couple hundred of these, and attaching them to various Account records.
The Problem:
Our Salesforce instance is Professional edition, which means I can't generate the WSDL for our instance, which makes me think I'm not going to be able to develop code that can create/edit/delete Marqui_Instance objects.
Before I start floundering around in the dark, I thought I'd post on here for advice. The only thing I can think of is to create an identical object in a Salesforce developer account, and use the WSDL from there... but then when I go to deploy the code in production, will it work? I'm scared that the WSDL from my dev account will have some guids or something similar, and my code will only work against the dev account.
If you get your application certified by Salesforce they will provide you with a "Partner Application API" token. Using this when establishing the Salesforce API session will allow your application to work with a professional edition org.
Alternatively, you can also obtain API access to a Professional Edition org by paying an additional fee. You will need to contact your salesforce.com sales person.
Update: Apparently the functionality is enabled by Salesforce internally using the informally named "Black Tab".
See also: Re: Use of the API and Salesforce.com Professional Version
Access to the web services API for Salesforce is only available in Developer, Enterprise, and Unlimited Editions.
I believe that you aren't allowed to login to the API, so even if you managed to generate a WSDL it wouldn't work.
See the full edition comparison chart [PDF].