- 최신
- 최다 투표
- 가장 많은 댓글
Regarding your date validation question, you mean validate in a business specific logic or validating format?
If your are talking to implemente a business logic when receiving a date, you should use a lambda code hook to invoke in every turn https://docs.aws.amazon.com/lexv2/latest/dg/lambda.html then validate when the date slot has a value.
But if your trying to validate as correct format maybe you should use native slots like Amazon.DATE
Your second question:
Right!, you can use session to set an attribute like {"authenticated": true} in sessionAttributes to check if user already passed the validation steps. If not set you can go to an authentication Intent, but if it is set you can go with the transaction. Good thing that if you use a lambda hook, the session object comes with every invocation (via sessionState)
https://docs.aws.amazon.com/lexv2/latest/dg/using-sessions.html
Switching intents
-
You can use the PutSession operation to switch from one intent to another. You can also use it to switch back to a previous intent. You can use the PutSession operation to set session attributes or slot values for the new intent.
-
Call the PutSession operation. Set the intent name to the name of the new intent and set the dialog action to Delegate. You can also set any slot values or session attributes required for the new intent.
Amazon Lex will start a conversation with the user using the new intent.
관련 콘텐츠
AWS 공식업데이트됨 일 년 전
Actually i am not clear yet. In my scenario I have created an authentication intent . for other intent like transaction related intent if the user directly hit those transaction related intent it should ask first authentication like username , mobile and email. also i want that if the authentication happened for one time then it should not ask for other intent .
what is put session operation?