AWS connect documentation change
Summary
Updated terminology from 'call' to 'contact' throughout document, removed .wav file simulation capability from actions block, and restructured permissions/testing sections
Security assessment
The change adds documentation about required permissions for simulation features, which relates to security access controls. The removal of .wav file simulation capability could indicate security hardening against potential audio file vulnerabilities, but no explicit security advisory is provided. The new permissions documentation improves security awareness but doesn't address a specific disclosed vulnerability.
Diff
diff --git a/connect/latest/adminguide/testing-simulation-concepts.md b/connect/latest/adminguide/testing-simulation-concepts.md index e5e85b3c6..5118b77fc 100644 --- a//connect/latest/adminguide/testing-simulation-concepts.md +++ b//connect/latest/adminguide/testing-simulation-concepts.md @@ -7 +7 @@ Interaction groups -# Call simulation concepts +# Simulation concepts @@ -9 +9 @@ Interaction groups -The traditional contact center testing and simulation approaches rely on technical step IDs and transitions that are inconsistent with natural human interaction patterns, creating a disconnect in validation processes. Connect's call simulation capabilities use an event-driven trigger response model that mirrors natural cause-and-effect reasoning patterns used by QA engineers and business testers. This approach removes the need to know every interaction that are programmed in order to test and validate the experience. Each test case is constructed as a sequence of observations paired with actions. Dependencies between observations are handled as transitions, creating a logical flow that matches human reasoning while maintaining technical precision. The following terms are used in the test case configuration: +The traditional contact center simulation approaches rely on technical step IDs and transitions that are inconsistent with natural human interaction patterns, creating a disconnect in validation processes. Connect's simulation capabilities use an event-driven trigger response model that mirrors natural cause-and-effect reasoning patterns used by QA engineers and business testers. This approach removes the need to know every interaction that are programmed in order to test and validate the experience. Each test case is constructed as a sequence of observations paired with actions. Dependencies between observations are handled as transitions, creating a logical flow that matches human reasoning while maintaining technical precision. The following terms are used in the test case configuration: @@ -29 +29 @@ Actors -Actors represent roles to be played in the testing framework. When observing events, actors can be the system or agent, such as a play prompt coming from the system or an agent accepting the call. When simulating actions, actors can be the customer, system, or agent, such as simulating a customer input DTMF or utterance, or simulating a system response from a Lambda function. +Actors represent roles to be played in the testing framework. When observing events, actors can be the system or agent, such as a play prompt coming from the system or an agent accepting the contact. When simulating actions, actors can be the customer, system, or agent, such as simulating a customer input DTMF or utterance, or simulating a system response from a Lambda function. @@ -33 +33 @@ Actors represent roles to be played in the testing framework. When observing eve -Use interaction groups to create simulated interactions with the call center. Each interaction group has three defined steps, described as the following blocks: +Use interaction groups to create simulated interactions with the contact center. Each interaction group has three defined steps, described as the following blocks: @@ -56 +56 @@ Actions -This block is optional and is used to override actions, override resources, send instructions, or test control actions. You can use override resources such as Lambda, Lex, Queue, or Hours of Operation with alternative resources or override actions with response values from related actions. You can validate the contact experience without invoking external resources to speed up test execution and prevent real data manipulation, such as preventing replaying a Lambda block that charges a credit card in production environment. You can use send instructions to simulate input to be sent to the contact center experience, such as text/utterance, DTMF tone, or .wav file for pre-recorded audio. Additionally, you can use test control action types to log data and end the test case execution at any point. +This block is optional and is used to override actions, override resources, send instructions, or test control actions. You can use override resources such as Lambda, Lex, Queue, or Hours of Operation with alternative resources or override actions with response values from related actions. You can validate the contact experience without invoking external resources to speed up test execution and prevent real data manipulation, such as preventing replaying a Lambda block that charges a credit card in production environment. You can use send instructions to simulate input to be sent to the contact center experience, such as text/utterance or DTMF tone. Additionally, you can use test control action types to log data and end the test case execution at any point. @@ -66 +66 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Call simulation +Required permissions @@ -68 +68 @@ Call simulation -Create and run test cases +Create test cases