put_slot_type
¶
put_slot_type(
name: SlotTypeName,
*,
config_overrides: Optional[LexModelBuildingServiceClientConfig] = None,
description: Optional[Description] = None,
enumeration_values: Optional[EnumerationValues] = None,
checksum: Optional[String] = None,
value_selection_strategy: Optional[SlotValueSelectionStrategy] = None,
create_version: Optional[Boolean] = None,
parent_slot_type_signature: Optional[CustomOrBuiltinSlotTypeName] = None,
slot_type_configurations: Optional[SlotTypeConfigurations] = None,
) -> PutSlotTypeResponse
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.
Parameters:
-
name(SlotTypeName) –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.
-
description(Optional[Description], default:None) –A description of the slot type.
-
enumeration_values(Optional[EnumerationValues], default:None) –A 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. -
checksum(Optional[String], default:None) –Identifies 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. -
value_selection_strategy(Optional[SlotValueSelectionStrategy], default:None) –Determines 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. -
-
create_version(Optional[Boolean], default:None) –When set to
truea new numbered version of the slot type is created. This is the same as calling theCreateSlotTypeVersionoperation. If you do not specifycreateVersion, the default isfalse. -
parent_slot_type_signature(Optional[CustomOrBuiltinSlotTypeName], default:None) –The 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. -
slot_type_configurations(Optional[SlotTypeConfigurations], default:None) –Configuration information that extends the parent built-in slot type. The configuration is added to the settings for the parent slot type.
Raises:
-
BadRequestException–The request is not well formed. For example, a value is invalid or a required field is missing. Check the field values, and try again.
-
ConflictException–There was a conflict processing the request. Try your request again.
-
InternalFailureException–An internal Amazon Lex error occurred. Try your request again.
-
LimitExceededException–The request exceeded a limit. Try your request again.
-
PreconditionFailedException–The checksum of the resource that you are trying to change does not match the checksum in the request. Check the resource's checksum and try again.
-
UnknownServiceError–The service returned an error code this client does not model.
Examples:
To Create a Slot Type This example shows how to create a slot type that describes pizza sauces.
>>> client.put_slot_type(name='PizzaSauceType', description='Available pizza sauces', enumeration_values=[{'value': 'red'}, {'value': 'white'}])
Source code in docs_src/capo_lex_model_building_service/_services/lex_model_building_service.py
2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 | |