AWS connect documentation change
Summary
Expanded support for contact flow modules to all flow types (previously only inbound flows) and added support for nested modules (up to 5 levels), with notes on specific block limitations.
Security assessment
The changes are feature enhancements for Amazon Connect contact flow modules, allowing broader usage and nesting. There is no mention of security vulnerabilities, incidents, or security features. The notes about potential interruptions in specific flow types are functional limitations, not security-related.
Diff
diff --git a/connect/latest/adminguide/contact-flow-modules.md b/connect/latest/adminguide/contact-flow-modules.md index b3c5270f9..075d90398 100644 --- a//connect/latest/adminguide/contact-flow-modules.md +++ b//connect/latest/adminguide/contact-flow-modules.md @@ -7 +7 @@ -Where you can use modulesLimitationsSecurity profile permissions for modulesCreate basic moduleAdd a module to a flowExample moduleModule versioning and aliasingCreate custom block moduleCreate module as tools +Where you can use modulesLimitationsUse module within moduleSecurity profile permissions for modulesCreate basic moduleAdd a module to a flowExample moduleModule versioning and aliasingCreate custom block moduleCreate module as tools @@ -37 +37,9 @@ Following are the benefits of using modules: -You can use modules in any flow that is [type](./create-contact-flow.html#contact-flow-types) **Inbound flow**. +You can use modules across all [flow types](./create-contact-flow.html#contact-flow-types). + +###### Note + + * Whisper flows that use a **TransferToQueue** block within a module might cause interruption during the flow execution. + + * **CustomerQueue** flow with a **LoopPrompt** block invoking a module using an **EndFlow** block might cause interruption during the flow execution. + + @@ -39 +46,0 @@ You can use modules in any flow that is [type](./create-contact-flow.html#contac -The following types of flows do not support modules: **Customer queue** , **Customer hold** , **Customer whisper** , **Outbound whisper** , **Agent hold** , **Agent whisper** , **Transfer to agent** , **Transfer to queue**. @@ -57 +64,3 @@ The following types of flows do not support modules: **Customer queue** , **Cust - * Modules do not allow invoking another module. + * When using one module to invoke other modules: A module being used as a tool can only invoke other modules used as tools. + + * If your module contains blocks that are not supported by the specific flow type, this incompatibility may lead the blocks to take the error branch. @@ -65,0 +75,16 @@ For example, you want data that is written from Lambda (an External attribute) a +## Use module within module + +You can invoke modules within other modules, supporting up to five levels of nesting with a stack limit to prevent recursive invocations. This feature promotes code reuse, supports complex modular designs, and improves the organization of large-scale solutions, leading to more efficient and maintainable workflows. + +### Example of nested modules + +This module shows how to check call back number from customers and allows them to update the call back number by invoking a sub module. Flows that invoke this module can set and update customer call back number. + +Following is an image of the customer call back module that invokes the sub module for setting the call back number: + + + +Following is an image of the set call back number sub module:: + + +