bobpskier

The Lex runtime in past versions required title as property of a GenericAttachment. Returning a ResponseCard without title caused a runtime error. Hence the Content Designer required this attribute when...

I believe version 4.1.0 will also address this issue.

The default embedded client included in QnABot is really meant to be example. It can be used however its extensibility is really limited. The companion [aws-lex-web-ui](https://github.com/aws-samples/aws-lex-web-ui) project offers significant css...

This error is from lex-web-ui and is related to that project instead of qnabot. That said, RecognizeText is an api on Lex V2. The V1 role by definition would not...

Can you fill us in on the details? What page are you trying to access when the error is generated? Access Denied in this context might indicate the designer UI...

@yashpungaliya The initial question only enables bot routing for subsequent input to qnabot. The answer to this initial question is provided as the response and the session attributes are set...

Sometimes you might want to route to the specialty bot on the first invocation and sometimes you might not want to route on the first invocation and instead provide hints...

I'm curious as to the client being used for the workflow. If using aws-lex-web-ui (also project on github) as the client, there is an api provided on the Iframe loader...

Another way to inspect the content is using Kibana to query the elasticsearch cluster directly. You could use the kibana UI to the elasticsearch cluster and find the offending questions...

Pull request would be great and I can merge it in. Thanks!