/* * Copyright 2018-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved. * * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with * the License. A copy of the License is located at * * http://aws.amazon.com/apache2.0 * * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions * and limitations under the License. */ package com.amazonaws.services.lexruntime.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.AmazonWebServiceRequest; /** * * @see AWS API * Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class PostTextRequest extends com.amazonaws.AmazonWebServiceRequest implements Serializable, Cloneable { /** *
* The name of the Amazon Lex bot. *
*/ private String botName; /** ** The alias of the Amazon Lex bot. *
*/ private String botAlias; /** *
* The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot. At
* runtime, each request must contain the userID
field.
*
* To decide the user ID to use for your application, consider the following factors. *
*
* The userID
field must not contain any personally identifiable information of the user, for example,
* name, personal identification numbers, or other end user personal information.
*
* If you want a user to start a conversation on one device and continue on another device, use a user-specific * identifier. *
** If you want the same user to be able to have two independent conversations on two different devices, choose a * device-specific identifier. *
** A user can't have two independent conversations with two different versions of the same bot. For example, a user * can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will * need to have conversation with two different versions, for example, while testing, include the bot alias in the * user ID to separate the two conversations. *
** Application-specific information passed between Amazon Lex and a client application. *
** For more information, see Setting Session * Attributes. *
*/ private java.util.Map* Request-specific information passed between Amazon Lex and a client application. *
*
* The namespace x-amz-lex:
is reserved for special attributes. Don't create any request attributes
* with the prefix x-amz-lex:
.
*
* For more information, see Setting Request * Attributes. *
*/ private java.util.Map* The text that the user entered (Amazon Lex interprets this text). *
*/ private String inputText; /** ** A list of contexts active for the request. A context can be activated when a previous intent is fulfilled, or by * including the context in the request, *
** If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session. If you * specify an empty list, all contexts for the session are cleared. *
*/ private java.util.List* The name of the Amazon Lex bot. *
* * @param botName * The name of the Amazon Lex bot. */ public void setBotName(String botName) { this.botName = botName; } /** ** The name of the Amazon Lex bot. *
* * @return The name of the Amazon Lex bot. */ public String getBotName() { return this.botName; } /** ** The name of the Amazon Lex bot. *
* * @param botName * The name of the Amazon Lex bot. * @return Returns a reference to this object so that method calls can be chained together. */ public PostTextRequest withBotName(String botName) { setBotName(botName); return this; } /** ** The alias of the Amazon Lex bot. *
* * @param botAlias * The alias of the Amazon Lex bot. */ public void setBotAlias(String botAlias) { this.botAlias = botAlias; } /** ** The alias of the Amazon Lex bot. *
* * @return The alias of the Amazon Lex bot. */ public String getBotAlias() { return this.botAlias; } /** ** The alias of the Amazon Lex bot. *
* * @param botAlias * The alias of the Amazon Lex bot. * @return Returns a reference to this object so that method calls can be chained together. */ public PostTextRequest withBotAlias(String botAlias) { setBotAlias(botAlias); return this; } /** *
* The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot. At
* runtime, each request must contain the userID
field.
*
* To decide the user ID to use for your application, consider the following factors. *
*
* The userID
field must not contain any personally identifiable information of the user, for example,
* name, personal identification numbers, or other end user personal information.
*
* If you want a user to start a conversation on one device and continue on another device, use a user-specific * identifier. *
** If you want the same user to be able to have two independent conversations on two different devices, choose a * device-specific identifier. *
** A user can't have two independent conversations with two different versions of the same bot. For example, a user * can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will * need to have conversation with two different versions, for example, while testing, include the bot alias in the * user ID to separate the two conversations. *
*userID
field.
* * To decide the user ID to use for your application, consider the following factors. *
*
* The userID
field must not contain any personally identifiable information of the user, for
* example, name, personal identification numbers, or other end user personal information.
*
* If you want a user to start a conversation on one device and continue on another device, use a * user-specific identifier. *
** If you want the same user to be able to have two independent conversations on two different devices, * choose a device-specific identifier. *
** A user can't have two independent conversations with two different versions of the same bot. For example, * a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a * user will need to have conversation with two different versions, for example, while testing, include the * bot alias in the user ID to separate the two conversations. *
*
* The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot. At
* runtime, each request must contain the userID
field.
*
* To decide the user ID to use for your application, consider the following factors. *
*
* The userID
field must not contain any personally identifiable information of the user, for example,
* name, personal identification numbers, or other end user personal information.
*
* If you want a user to start a conversation on one device and continue on another device, use a user-specific * identifier. *
** If you want the same user to be able to have two independent conversations on two different devices, choose a * device-specific identifier. *
** A user can't have two independent conversations with two different versions of the same bot. For example, a user * can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will * need to have conversation with two different versions, for example, while testing, include the bot alias in the * user ID to separate the two conversations. *
*userID
field.
* * To decide the user ID to use for your application, consider the following factors. *
*
* The userID
field must not contain any personally identifiable information of the user, for
* example, name, personal identification numbers, or other end user personal information.
*
* If you want a user to start a conversation on one device and continue on another device, use a * user-specific identifier. *
** If you want the same user to be able to have two independent conversations on two different devices, * choose a device-specific identifier. *
** A user can't have two independent conversations with two different versions of the same bot. For example, * a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that * a user will need to have conversation with two different versions, for example, while testing, include * the bot alias in the user ID to separate the two conversations. *
*
* The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot. At
* runtime, each request must contain the userID
field.
*
* To decide the user ID to use for your application, consider the following factors. *
*
* The userID
field must not contain any personally identifiable information of the user, for example,
* name, personal identification numbers, or other end user personal information.
*
* If you want a user to start a conversation on one device and continue on another device, use a user-specific * identifier. *
** If you want the same user to be able to have two independent conversations on two different devices, choose a * device-specific identifier. *
** A user can't have two independent conversations with two different versions of the same bot. For example, a user * can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will * need to have conversation with two different versions, for example, while testing, include the bot alias in the * user ID to separate the two conversations. *
*userID
field.
* * To decide the user ID to use for your application, consider the following factors. *
*
* The userID
field must not contain any personally identifiable information of the user, for
* example, name, personal identification numbers, or other end user personal information.
*
* If you want a user to start a conversation on one device and continue on another device, use a * user-specific identifier. *
** If you want the same user to be able to have two independent conversations on two different devices, * choose a device-specific identifier. *
** A user can't have two independent conversations with two different versions of the same bot. For example, * a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a * user will need to have conversation with two different versions, for example, while testing, include the * bot alias in the user ID to separate the two conversations. *
** Application-specific information passed between Amazon Lex and a client application. *
** For more information, see Setting Session * Attributes. *
* * @return Application-specific information passed between Amazon Lex and a client application. *
* For more information, see Setting
* Session Attributes.
*/
public java.util.Map
* Application-specific information passed between Amazon Lex and a client application.
*
* For more information, see Setting Session
* Attributes.
*
* For more information, see Setting
* Session Attributes.
*/
public void setSessionAttributes(java.util.Map
* Application-specific information passed between Amazon Lex and a client application.
*
* For more information, see Setting Session
* Attributes.
*
* For more information, see Setting
* Session Attributes.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public PostTextRequest withSessionAttributes(java.util.Map
* Request-specific information passed between Amazon Lex and a client application.
*
* The namespace
* For more information, see Setting Request
* Attributes.
* x-amz-lex:
is reserved for special attributes. Don't create any request attributes
* with the prefix x-amz-lex:
.
*
* The namespace x-amz-lex:
is reserved for special attributes. Don't create any request
* attributes with the prefix x-amz-lex:
.
*
* For more information, see Setting
* Request Attributes.
*/
public java.util.Map
* Request-specific information passed between Amazon Lex and a client application.
*
* The namespace
* For more information, see Setting Request
* Attributes.
* x-amz-lex:
is reserved for special attributes. Don't create any request attributes
* with the prefix x-amz-lex:
.
*
* The namespace x-amz-lex:
is reserved for special attributes. Don't create any request
* attributes with the prefix x-amz-lex:
.
*
* For more information, see Setting
* Request Attributes.
*/
public void setRequestAttributes(java.util.Map
* Request-specific information passed between Amazon Lex and a client application.
*
* The namespace
* For more information, see Setting Request
* Attributes.
* x-amz-lex:
is reserved for special attributes. Don't create any request attributes
* with the prefix x-amz-lex:
.
*
* The namespace x-amz-lex:
is reserved for special attributes. Don't create any request
* attributes with the prefix x-amz-lex:
.
*
* For more information, see Setting
* Request Attributes.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public PostTextRequest withRequestAttributes(java.util.Map
* The text that the user entered (Amazon Lex interprets this text).
*
* The text that the user entered (Amazon Lex interprets this text).
*
* The text that the user entered (Amazon Lex interprets this text).
*
* A list of contexts active for the request. A context can be activated when a previous intent is fulfilled, or by
* including the context in the request,
*
* If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session. If you
* specify an empty list, all contexts for the session are cleared.
*
* If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the
* session. If you specify an empty list, all contexts for the session are cleared.
*/
public java.util.List
* A list of contexts active for the request. A context can be activated when a previous intent is fulfilled, or by
* including the context in the request,
*
* If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session. If you
* specify an empty list, all contexts for the session are cleared.
*
* If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session.
* If you specify an empty list, all contexts for the session are cleared.
*/
public void setActiveContexts(java.util.Collection
* A list of contexts active for the request. A context can be activated when a previous intent is fulfilled, or by
* including the context in the request,
*
* If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session. If you
* specify an empty list, all contexts for the session are cleared.
*
* NOTE: This method appends the values to the existing list (if any). Use
* {@link #setActiveContexts(java.util.Collection)} or {@link #withActiveContexts(java.util.Collection)} if you want
* to override the existing values.
*
* If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session.
* If you specify an empty list, all contexts for the session are cleared.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public PostTextRequest withActiveContexts(ActiveContext... activeContexts) {
if (this.activeContexts == null) {
setActiveContexts(new java.util.ArrayList
* A list of contexts active for the request. A context can be activated when a previous intent is fulfilled, or by
* including the context in the request,
*
* If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session. If you
* specify an empty list, all contexts for the session are cleared.
*
* If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session.
* If you specify an empty list, all contexts for the session are cleared.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public PostTextRequest withActiveContexts(java.util.Collection