UpdateContactTaskTemplate
Updates the task template association on an existing task contact. You can update the task template on a contact before assignment to support tasks that are created without a template (for example Rules or disconnect flows) or change the agent interaction form to represent the latest task data (for example an initial request that was submitted as a refund gets updated to an account cancellation and requires a new template).
This operation can only be used with task contacts that are in progress and not connected to an agent. A task template can be updated a maximum of 5 times per contact.
The task's references must be compatible with the fields of the target task template. If the target template has a required field, the task must have a corresponding reference with a matching name and compatible type. The following task template field types map to reference types:
-
TEXT,TEXT_AREA,BOOLEAN, andSINGLE_SELECTmap to references of typeSTRING. -
NUMBERmaps to references of typeNUMBER. -
DATE_TIMEmaps to references of typeDATE. -
URLmaps to references of typeURL. -
EMAILmaps to references of typeEMAIL.
References corresponding to TEXT fields must be fewer than 512 characters.
TEXT_AREA fields must be fewer than 4,096 characters. BOOLEAN fields must have a value
of true or false.
An InvalidRequestException occurs when UpdateContactTaskTemplate is called on a
connected or terminated task, when it is called on non-task contacts, and when the task contact already uses the
provided task template. A PropertyValidationException occurs when the task's references conflict with
the task template's fields, for example if the task is missing a reference that matches a required field, or if the
task has a reference that matches a required field's name but not its datatype.
Request Syntax
POST /contact/task-template HTTP/1.1
Content-type: application/json
{
"ContactId": "string",
"InstanceId": "string",
"TaskTemplateId": "string"
}
URI Request Parameters
The request does not use any URI parameters.
Request Body
The request accepts the following data in JSON format.
- ContactId
-
The identifier of the contact in this instance of Connect Customer.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 256.
Required: Yes
- InstanceId
-
The identifier of the Connect Customer instance. You can find the instance ID in the Amazon Resource Name (ARN) of the instance.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 100.
Required: Yes
- TaskTemplateId
-
A unique identifier for the task template. For more information about task templates, see Task templates in the Connect Customer Administrator Guide.
Type: String
Length Constraints: Minimum length of 1. Maximum length of 500.
Required: Yes
Response Syntax
HTTP/1.1 200
Response Elements
If the action is successful, the service sends back an HTTP 200 response with an empty HTTP body.
Errors
For information about the errors that are common to all actions, see Common Error Types.
- AccessDeniedException
-
You do not have sufficient permissions to perform this action.
HTTP Status Code: 403
- InternalServiceException
-
Request processing failed because of an error or failure with the service.
- Message
-
The message.
HTTP Status Code: 500
- InvalidRequestException
-
The request is not valid.
- Message
-
The message about the request.
- Reason
-
Reason why the request was invalid.
HTTP Status Code: 400
- LimitExceededException
-
The allowed limit for the resource has been exceeded.
- Message
-
The message about the limit.
HTTP Status Code: 429
- PropertyValidationException
-
The property is not valid.
HTTP Status Code: 400
- ResourceNotFoundException
-
The specified resource was not found.
- Message
-
The message about the resource.
HTTP Status Code: 404
- ServiceQuotaExceededException
-
The service quota has been exceeded.
- Reason
-
The reason for the exception.
HTTP Status Code: 402
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: