Put Slot Type
| lexmodelbuildingservice_put_slot_type | R Documentation |
Creates a custom slot type or replaces an existing custom slot type¶
Description¶
Creates a custom slot type or replaces an existing custom slot type.
To create a custom slot type, specify a name for the slot type and a set of enumeration values, which are the values that a slot of this type can assume. For more information, see how-it-works.
If you specify the name of an existing slot type, the fields in the
request replace the existing values in the $LATEST version of the slot
type. Amazon Lex removes the fields that you don't provide in the
request. If you don't specify required fields, Amazon Lex throws an
exception. When you update the $LATEST version of a slot type, if a
bot uses the $LATEST version of an intent that contains the slot type,
the bot's status field is set to NOT_BUILT.
This operation requires permissions for the lex:PutSlotType action.
Usage¶
lexmodelbuildingservice_put_slot_type(name, description,
enumerationValues, checksum, valueSelectionStrategy, createVersion,
parentSlotTypeSignature, slotTypeConfigurations)
Arguments¶
name[required] The name of the slot type. The name is not case sensitive.
The name can't match a built-in slot type name, or a built-in slot type name with "AMAZON." removed. For example, because there is a built-in slot type called
AMAZON.DATE, you can't create a custom slot type calledDATE.For a list of built-in slot types, see Slot Type Reference in the Alexa Skills Kit.
descriptionA description of the slot type.
enumerationValuesA list of
EnumerationValueobjects that defines the values that the slot type can take. Each value can have a list ofsynonyms, which are additional values that help train the machine learning model about the values that it resolves for a slot.A regular expression slot type doesn't require enumeration values. All other slot types require a list of enumeration values.
When Amazon Lex resolves a slot value, it generates a resolution list that contains up to five possible values for the slot. If you are using a Lambda function, this resolution list is passed to the function. If you are not using a Lambda function you can choose to return the value that the user entered or the first value in the resolution list as the slot value. The
valueSelectionStrategyfield indicates the option to use.checksumIdentifies a specific revision of the
$LATESTversion.When you create a new slot type, leave the
checksumfield blank. If you specify a checksum you get aBadRequestExceptionexception.When you want to update a slot type, set the
checksumfield to the checksum of the most recent revision of the$LATESTversion. If you don't specify thechecksumfield, or if the checksum does not match the$LATESTversion, you get aPreconditionFailedExceptionexception.valueSelectionStrategyDetermines the slot resolution strategy that Amazon Lex uses to return slot type values. The field can be set to one of the following values:
ORIGINAL_VALUE- Returns the value entered by the user, if the user value is similar to the slot value.TOP_RESOLUTION- If there is a resolution list for the slot, return the first value in the resolution list as the slot type value. If there is no resolution list, null is returned.
If you don't specify the
valueSelectionStrategy, the default isORIGINAL_VALUE.createVersionWhen set to
truea new numbered version of the slot type is created. This is the same as calling thecreate_slot_type_versionoperation. If you do not specifycreateVersion, the default isfalse.parentSlotTypeSignatureThe built-in slot type used as the parent of the slot type. When you define a parent slot type, the new slot type has all of the same configuration as the parent.
Only
AMAZON.AlphaNumericis supported.slotTypeConfigurationsConfiguration information that extends the parent built-in slot type. The configuration is added to the settings for the parent slot type.
Value¶
A list with the following syntax:
list(
name = "string",
description = "string",
enumerationValues = list(
list(
value = "string",
synonyms = list(
"string"
)
)
),
lastUpdatedDate = as.POSIXct(
"2015-01-01"
),
createdDate = as.POSIXct(
"2015-01-01"
),
version = "string",
checksum = "string",
valueSelectionStrategy = "ORIGINAL_VALUE"|"TOP_RESOLUTION",
createVersion = TRUE|FALSE,
parentSlotTypeSignature = "string",
slotTypeConfigurations = list(
list(
regexConfiguration = list(
pattern = "string"
)
)
)
)
Request syntax¶
svc$put_slot_type(
name = "string",
description = "string",
enumerationValues = list(
list(
value = "string",
synonyms = list(
"string"
)
)
),
checksum = "string",
valueSelectionStrategy = "ORIGINAL_VALUE"|"TOP_RESOLUTION",
createVersion = TRUE|FALSE,
parentSlotTypeSignature = "string",
slotTypeConfigurations = list(
list(
regexConfiguration = list(
pattern = "string"
)
)
)
)