AWS connect documentation change
Summary
Restructured documentation sections, updated cross-references, and improved formatting for routing criteria configuration. Changed section headers from 'Using the flow block' to 'How to set routing criteria', added proper markdown formatting for UI elements, and updated Lambda function block references with hyperlinks.
Security assessment
The changes appear to be documentation restructuring and clarification without any mention of security vulnerabilities, access controls, or authentication mechanisms. Updates focus on improving user guidance for routing configuration rather than addressing security concerns.
Diff
diff --git a/connect/latest/adminguide/set-routing-criteria.md b/connect/latest/adminguide/set-routing-criteria.md index d876e460e..cbb5a7a61 100644 --- a//connect/latest/adminguide/set-routing-criteria.md +++ b//connect/latest/adminguide/set-routing-criteria.md @@ -5 +5 @@ -Prerequisites for setting routing criteria using predefined attributesWhen to use this blockHow routing criteria worksUsing the flow blockSet routing criteria manuallySet routing criteria dynamicallySample Lambda function for setting routing criteriaWhat are the statuses of a routing step and why are they needed?Use routing criteria to target a specific preferred agentScenarios +Prerequisites for setting routing criteria using predefined attributesWhen to use this blockHow routing criteria worksHow to set routing criteriaWhat are the statuses of a routing step and why are they needed?Use routing criteria to target a specific preferred agentScenarios @@ -105 +105 @@ If an expiration duration is not specified on the routing step, the routing step - * You can only use OR when setting attributes dynamically. For more information, see For more information, see Using the flow block. + * You can only use OR when setting attributes dynamically. For more information, see How to set routing criteria. @@ -107 +107 @@ If an expiration duration is not specified on the routing step, the routing step - * NOT operator to exclude a proficiency by chosen levels. You can only use NOT when setting attributes dynamically. For more information, see Using the flow block. + * NOT operator to exclude a proficiency by chosen levels. You can only use NOT when setting attributes dynamically. For more information, see How to set routing criteria. @@ -129 +129 @@ In addition, attributes and routing criteria must have the following; -## Using the flow block +## How to set routing criteria @@ -131 +131 @@ In addition, attributes and routing criteria must have the following; -You can set the desired routing criteria either manually in the flow block UI or dynamically based on the output from the Invoke AWS Lambda Function block. +You can set the desired routing criteria either manually in the flow block UI or dynamically based on the output from the [Invoke AWS Lambda function](./invoke-lambda-function-block.html) block. @@ -133 +133 @@ You can set the desired routing criteria either manually in the flow block UI or - + @@ -135 +135 @@ You can set the desired routing criteria either manually in the flow block UI or -## Set routing criteria manually +### Set routing criteria manually @@ -137 +137 @@ You can set the desired routing criteria either manually in the flow block UI or -Using this option, you can set routing criteria on contacts as specified in the `Set routing criteria` block manually. See the example of a flow below to where the predefined attribute is added to a routing step manually by picking the attribute and value from a dropdown list. +Using this option, you can set routing criteria on contacts as specified in the **Set routing criteria** block manually. See the example of a flow below to where the predefined attribute is added to a routing step manually by picking the attribute and value from a dropdown list. @@ -141 +141 @@ Using this option, you can set routing criteria on contacts as specified in the -As needed, you can configure predefined attribute value dynamically using JSONPath reference even in this option. For example, you can specify ``$.External.language`` JSONPath reference instead of hard coding a `AWS DynamoDB` value on the ``Technology`` requirement of all of the contacts. For more information on JSONPath reference, see [List of available contact attributes in Amazon Connect and their JSONPath references](./connect-attrib-list.html). +As needed, you can configure predefined attribute value dynamically using JSONPath reference even in this option. For example, you can specify ``$.External.language`` JSONPath reference instead of hard coding a `AWS DynamoDB` value on the ``Technology`` requirement of all of the contacts. For more information about JSONPath reference, see [List of available contact attributes in Amazon Connect and their JSONPath references](./connect-attrib-list.html). @@ -143 +143 @@ As needed, you can configure predefined attribute value dynamically using JSONPa -## Set routing criteria dynamically +### Set routing criteria dynamically @@ -147 +147 @@ You can set routing criteria on a contact dynamically based on the output from t - * In the **Invoke AWS Lambda function** block, configure the Lambda function to return the routing criteria in JSON format and set the response validation as JSON. For more information on using the **Invoke AWS Lambda function** , see the [Grant Amazon Connect access to your AWS Lambda functions](./connect-lambda-functions.html) documentation. + * In the [Invoke AWS Lambda function](./invoke-lambda-function-block.html) block, configure the Lambda function to return the routing criteria in JSON format and set the response validation as JSON. For more information about using the **Invoke AWS Lambda function** , see the [Grant Amazon Connect access to your AWS Lambda functions](./connect-lambda-functions.html) documentation. @@ -154 +154 @@ You can set routing criteria on a contact dynamically based on the output from t -## Sample Lambda function for setting routing criteria +### Sample Lambda function for setting routing criteria @@ -300 +300 @@ Amazon Connect Customer Profiles provides seven out-of-the box default attribute -You can then use the **Set manually** option in the `Set routing criteria` Flow block UI to specify that each contact should be routed to `$.Customer.CalculatedAttributes._last_agent_id` (a JSONPath reference) instead of hard coding a specific user ID, and set an expiration timer for how long to restrict each contact to route to the last agent. For more information on JSONPath reference, see [List of available contact attributes in Amazon Connect and their JSONPath references](./connect-attrib-list.html). For more information on the default attributes available through Amazon Connect Customer Profiles, see [Default calculated attributes in Amazon Connect Customer Profiles](./customerprofiles-default-calculated-attributes.html). +You can then use the **Set manually** option in the **Set routing criteria** block to specify that each contact should be routed to `$.Customer.CalculatedAttributes._last_agent_id` (a JSONPath reference) instead of hard coding a specific user ID, and set an expiration timer for how long to restrict each contact to route to the last agent. For more information on JSONPath reference, see [List of available contact attributes in Amazon Connect and their JSONPath references](./connect-attrib-list.html). For more information about the default attributes available through Amazon Connect Customer Profiles, see [Default calculated attributes in Amazon Connect Customer Profiles](./customerprofiles-default-calculated-attributes.html). @@ -306 +306 @@ If you have a routing step set targeting a specific preferred agent, the contact - 1. Agent is online or not. + 1. Agent is online or not