Creating a Query with the Dialog Code Hook is not working with KendraSearchIntent

[SandeepPasula898]

Hello, I am trying to add kendraQueryFilterString and kendraQueryRequestPayload parameters to my delegate function. None of them are getting applied when testing.

• I am using LexV2 bot with KendraSearchIntent in it.
• In associated lambda function of dialogcodehook, I am returning delegate response as below

  response = {
      'sessionState': {
          'sessionAttributes': session_attributes,
          'dialogAction': {
              'type': 'Delegate',
              'kendraQueryRequestPayload': kendraQueryRequestPayload,
              'kendraQueryFilterString': kendraQueryFilterString
          },
          'intent': intent
      }
  }

  Reference doc - https://docs.aws.amazon.com/lex/latest/dg/built-in-intent-kendra-search.html

[tim-finnigan]

Hi @SandeepPasula898 thanks for reaching out. Could you please provide the full steps to reproduce this?

[SandeepPasula898]

Hi @tim-finnigan, I am trying to do something similar to this blog- https://medium.com/@info.shwetagupta/query-filter-for-kendrasearchintent-in-amazon-lex-40c8b93ca8c1

1. Created a bot in lex V2 with kendrasearchintent in it.
2. Created a lambda function for dialogcodehook and fulfillment codehook of kendrasearchintent.
3. I am trying to use kendraQueryFilterString in dialog lambda instead of using attribute filter in lexv2 console by sending kendraQueryFilterString as parameter in dialog lambda response using delegate dialogaction type.

I wanted to know whether kendraQueryFilterString and kendraQueryRequestPayload are still in use or deprecated, because the lexV2 documentations did not mention anything on this like lexV1 does.

https://docs.aws.amazon.com/lex/latest/dg/lambda-input-response-format.html#using-lambda-response-format - In this lex V1 document in 'Delegate' dialogaction type they mentioned about this. It is not working for LexV2 bots, also lexV2 documentation does discuss much on this.

[tim-finnigan]

In the Lex V2 Developer Guide: https://docs.aws.amazon.com/lexv2/latest/dg/built-in-intent-kendra-search.html it mentions kendraQueryFilterString and kendraQueryRequestPayload so I would assume they are still supported. If you provide a full code snippet and debug logs I could look into the issue further.

[SandeepPasula898]

Hi @tim-finnigan, For reproducing this behavior, I will provide sample configuration of LexV2, Kendra FAQ sample and lambda function in couple of days by creating them since I am working on client's data. Thanks.

[tim-finnigan]

Hi @SandeepPasula898 since we haven't heard back in over a month I'm going to close this but please let us know if you're still encountering this issue.

[github-actions[bot]]

This issue is now closed.

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.