AWS connect documentation change
Summary
Clarified requirements for RoutingStepExpressions filter: now allows arbitrary JSON key order/whitespace while preserving array order
Security assessment
This is a documentation clarification about filter syntax requirements. No security context is present in the change.
Diff
diff --git a/connect/latest/adminguide/metric-primitive-definitions.md b/connect/latest/adminguide/metric-primitive-definitions.md index cc7c47d2f..d7d0a3479 100644 --- a//connect/latest/adminguide/metric-primitive-definitions.md +++ b//connect/latest/adminguide/metric-primitive-definitions.md @@ -597 +597 @@ Queues | Queue | Valid input to this key is Queue ARNs or QueueId's -RoutingStepExpressions | Routing step expression | ROUTING_STEP_EXPRESSION is a valid filter key with a filter value up to 3000 length. This filter is case and order sensitive. JSON string fields must be sorted in ascending order and JSON array order should be kept as is. Please read the below references for more info: +RoutingStepExpressions | Routing step expression | Accepts a filter value up to 3,000 characters in length. Filter values are case-sensitive. JSON object key order and whitespace may be arbitrary; array order and tree structure must be preserved. Please read the below references for more info: