hi i am working on amazon lex and want to get NluIntentConfidence value in Contact flow CheckAttribute block.
I have tried using like this
but IVR is not checking this value So, anyone can help me with this how i can get this value?
have a look at the contact flow design.
Connect only allows you to use key/values returned inside "sessionAttributes" or slot values. As you can see from the response, nluIntentConfidence is not a session attribute, you cannot use it in connect.
https://docs.aws.amazon.com/connect/latest/adminguide/types-of-contact-attributes.html
To get this value in connect, I suggest you use a codehook, either validation or fulfillment codehook in lex to take his value and store it in lex session. You can then use it in connect contact flow. If you have not used it already, you can refer to below documentation
https://docs.aws.amazon.com/lex/latest/dg/using-lambda.html
https://docs.aws.amazon.com/lex/latest/dg/ex-book-trip-create-integrate.html
Related
I have a Basic API connection from Recurly. I want to use that API to get data about my Data Base using Azure Data Factory. I created ls_RestAPI, created ds_RestAPI and created 1 pippeline to proceed to get the data. But there are some problems. My API has Basic Auth as username and no password (Postman Image), header is Accept and Authorization.
When I start connecting it using ADF, it throws an error due to incorrect syntax. I have provided pictures for you to understand easily.
I tried to remove or edit Accept and Authorization but it still doesn't work:
How can I reconfigure it properly to be able to get data from the above API?
My aim is that after running, Rest API can call all Next Page of API in 1 run. So I use:
"paginationRules": {
"AbsoluteUrl": "$.next"
but now I have the problem that I can't connect to the API.
ADF Rest connector only expects a Json response. This is mentioned as a warning in one of your screenshots.
As a result, this is overriding what you have entered for Accept Header.
Could you try firing this API call from some other service like Logic apps?
I'm trying to use the 'client_iden' target parameter to send pushes to multiple users at once. I've successfully created the client, but I'm unable to find the 'client_iden' parameter on the client creation page.
Does anyone know where this parameter can be found?
Sorry about that! I think that used to be there but we must have accidentally removed it. You should create a Push object with an access token for your Client. Then check the client_iden on that Push. Unfortunately that's probably the easiest way to find this information right now.
https://api.pushbullet.com/v2/devices
Username = your API key, password = blank
You can find all your device_idens in the returned json
I am using soapUI open source version to test an API. am using a token to access the test step.
I need to send the token with the API request.I have transferred the token value to the test step using property transfer but the transferred value is embedded in the body of the next request.
I want to send the value as a query parameter along with API request/
API Structure : Post method
api/v1/delete/token
the transferred value should be sent in place of token.
Kindly assist me.
You need to set up your second request as a correct resource, and parametrize the token variable. Official documentation is available.
After that, you do not need to use a transfer step for something this simple. You can just use property expansion, as per official documentation. Something like: ${previous_step_name#ResponseAsXml#//*:token}
I have an API that provides an Account resource based on the authentication (login) that is supplied. As a user can only have one account, and can only see it's own account and not those of others, this API will basically be a single resource API in all cases.
So to keep things simple, I have this resource under the url accounts/ and when you access accounts/?username=dude&password=veryhard you'll get your account data (if you dohn't supply authentication you'll get a 403).
Now I wonder if this is RESTful. Also, you should be able to update your account info, and I wonder if PUT would be appropriate. In my knowledge, PUT should be done on a unique URI for the resource. Well, is this a unique URI for the resource? Generally a URI for an account would look like accounts/3515/ where 3515 is the account id. However, users don't know their account id. Also, there should be more ways to log in, instead of a username + password you should also be able to use a token (like accounts/?token=d3r90jfhda139hg). So then we got 2 URL's that point to the same resource, which also isn't really beautiful for a RESTful URI, is it?
So, what would be the most RESTful solution? Or should I not do this RESTful?
REST purists will consider that use of /accounts/ to obtain a single account is bad practice as it should specify a collection. Instead consider a key which cannot be mistaken for an ID, for example if your IDs are UUIDs then use a token such as 'me' so your URL is /accounts/me. This has the advantage that if later on you wish to obtain different account information, say for example you need to list users or you have an administration system using the same API, then you can expand it easily.
Putting username and password in the URL is also not pure REST. The query parameters should be directly related to the resource you are obtaining; commonly filtering and limiting the resources returned. Instead you should seriously consider using something like HTTP Basic authentication over an encrypted (HTTPS) connection so that you separate out your authentication/authorisation and resource systems. If you prefer to use a token system then take a look at oauth or hawk.
Finally, yes if you use PUT you should supply a full resource identifier. Given that it is very common for systems to read data before updating it the lack of ID won't be a problem as that will come back as part of the prior GET.
Yes accounts/?username=dude&password=veryhard is a correct REST URL.
PUT is used with an id if it used to update a resource, if you use it to create you must supply an ID. otherwise you use post to create a resource without id
In my Java web application,when a user gets logged in,i store the user name and other details in session as follows,
session.setAttribute("userName",username);
I am using ExtJs4 for UI.How to get the session variables in extJs?
Thanks
I can second #Geronimo approach. You need to get user Id and/or permissions when you authenticate the user. However...
You can't rely just on the username/permissions that you store somewhere in your JS code because it can't be easily spoofed. If you present user with some information that can be different for different levels of access you still need to do server side validation of the user identity.
You can't get session variables off the server web container using javascript only.
I do the same thing (storing userId as a session variable in java). I use Ext.Request to perform an Ajax request to a java servlet to get it (along with other data about the user like permission settings for the webapp to enable or disable features they wouldn't be able to use).
EDIT:
I second sha's answer also, the only reason I pass the authentication information back to the client is for cosmetic reasons - so that user doesn't think he can use a feature in javascript that would be denied by my server side authentication. If he were to spoof the userId or permissions and try to use the feature, the real authentication on the server side would stop him.
I understand that the question has been asked for a long time ago, but despite the large number of views and the absence of an plain answer, I decided to offer this answer:
Assume that the session variable is registered like /index.php?PHPSESSID=9ebca8bd62c830d3e79272b4f585ff8f
In this case, you can get the variable PHPSESSID through JS object "location" and transform it through Ext.Object.fromQueryString()
So:
console.log( Ext.Object.fromQueryString( location.search ) );
will prepare PHPSESSID variable for your needs.