# UCCX scripts and Flow Designer flows

Canonical: https://warmtransfer.net/knowledge/uccx-script-to-flow-redesign

Last verified: 2026-09-22

Cisco Unified CCX Editor scripts and Webex Contact Center Flow Designer flows represent distinct paradigms for call routing and workflow execution[^22][^24].

## UCCX Script Architecture

The Cisco Unified CCX Editor provides a graphical programming environment for creating, modifying, validating, and debugging telephony and multimedia application scripts[^22]. Unified CCX script steps are written in Java, although Cisco states that an author does not need to understand Java programming to build a script[^49]. A script is associated with an application and runs when the application's associated trigger is dialled[^47].

Cisco documents 3 categories of variables available to a Unified CCX script: local script variables, Cisco predefined enterprise call variables, and Expanded Call Context variables[^58]. Local script variables are defined in the Variable pane of the Unified CCX Editor and belong to the individual script[^39]. Exchanging data between a local script variable and an ICME script requires the Set Enterprise Call Info and Get Enterprise Call Info steps[^21].

For modular design, the Call Subflow step invokes another script from within a main script[^7]. Its General tab controls the target script and interruption settings, while the Input Mappings and Output Mappings tabs carry data[^7]. In an input mapping, a main-script variable can map only to a subflow variable of the same type[^54]. Any valid expression can be passed, and Unified CCX evaluates all input expressions before invoking the subflow, storing the results in the named subflow variables[^51].

Direct SQL operations in Unified CCX rely on the Database palette, which provides 4 steps: DB Read, DB Get, DB Write, and DB Release[^12]. These database steps require either a Cisco Unified IP IVR or a Cisco Unified CCX Premium license[^11]. Additionally, the database subsystem and a Data Source Name must be configured before these steps function in a script[^10].

## Flow Designer Architecture

Flow Designer organizes its activity library into 4 groups: Contact Handling, Flow Control, Utilities, and Voice[^24]. Voice flows are managed in Flow Designer, whereas digital channel flows are created in Flow Builder within Webex Connect[^16].

External system integration in Flow Designer is handled through the Utilities group[^37][^45]. The HTTP Request activity acts as the external interface and allows target systems to be configured centrally in Control Hub as custom connectors[^37][^36]. A Parse activity extracts values from structured responses[^45]. To replicate direct database queries, Cisco provides the CiscoDevNet webexcc-dbconnector sample, a Spring Boot REST service that fronts a SQL database so Flow Designer can query it via the HTTP Request activity[^15].

Flow Designer supports multiple variable classes, including custom flow variables, predefined variables, global variables, and JSON variables[^38]. Predefined variables include activity output variables and event output variables, which are populated after an activity executes[^1]. Expressions inside flows use Pebble template syntax, complemented by Cisco-documented custom Pebble filters[^46]. For advanced tasks, Flow Designer includes a managed Functions object that enables data manipulation and automation via scripting languages such as Python[^29][^30].

Global variables are configured centrally under Flows > Global Variables in Control Hub and are accessible across flows[^34]. Digital flows in Flow Builder also support global variables alongside custom flow variables[^16]. Up to 100 global variables can be enabled for reporting simultaneously[^33]. Cisco instructs administrators not to store secure data, such as credit card numbers, personal identification numbers, or social security numbers, in global variables because historical reporting users can view their values[^35]. A global variable can also be presented on the agent Desktop with a custom label, and if Edit on Desktop is configured, an agent can edit the value during the session[^32].

Flow Designer handles modularity through the Subflow and GoTo activities[^40][^50]. The Subflow activity executes reusable logic, accepts inputs, and returns outputs to the main flow[^50]. While developers can map a main flow's global variable to a subflow local variable, global variables cannot be added directly inside a subflow[^52]. Subflows support a "Propagate changes to all flows" setting to push updates out to every flow using that subflow[^53].

## Operational Safeguards and Lifecycle Management

Webex Contact Center enforces loop-prevention safeguards and validation requirements prior to execution[^57][^48]. Flows must be validated and all errors resolved before publishing; the Publish control remains disabled while errors exist[^57]. To guard against runaway execution, Webex Contact Center enforces per-activity self-loop limits:[^48]

| Activity | Self-Loop Limit |
| --- | --- |
| Menu | 100[^48] |
| Collect Digits | 100[^48] |
| Blind Transfer | 10[^48] |
| Virtual Agent | 50[^48] |

Flow Designer includes built-in Copy flow, Export flow, and Import flow actions[^23][^9]. Cisco distributes official flow template samples as JSON files[^55]. Flows themselves are not supported configuration types in Webex Contact Center Bulk Operations, which restricts other configurations to 5000 rows per CSV request, a 5 MB CSV file limit, and a 50 MB limit for audio ZIP archives[^6][^5]. 

Version labels such as Dev, Test, and Live can be assigned to flows to facilitate blue-green promotions at the entry point[^59]. On 29 July 2026, Cisco announced Flow V2 APIs alongside a public Flow schema on the Webex Contact Center Developer Portal[^27]. These APIs allow teams to author flows programmatically, and to search, validate, publish, export, lock, and unlock flows, subflows, and functions[^27][^28].

## Migration Considerations

The Cisco UCCX to Webex Contact Center discovery tool extracts configuration for multimedia profiles, sites, user profiles, work types, auxiliary codes, agent profiles, address books, skill definitions, skill profiles, teams, entry points, outdial entry points, queues, outdial queues, and users, generating bulk import files[^19]. It also extracts UCCX audio prompts as.wav files[^17]. The tool requires Java 8 or above, network access to the Cisco Unified CCX server, and administrator credentials[^20]. Cisco notes that the discovery tool evolves continuously and may not cover all recent features[^56].

Field reports suggest that a UCCX to Webex Contact Center transition can take 3 to 6 months depending on script volume and environment scale[^26]. Field reports suggest that on at least one migration the organization opted to preserve and simplify its existing call flow logic rather than redesigning flows during the migration[^25].

## See also

- See also [The UCCX to Webex Contact Center discovery tool](https://warmtransfer.net/knowledge/uccx-discovery-tool).
- See also [UCCX objects and their Webex Contact Center equivalents](https://warmtransfer.net/knowledge/uccx-to-webex-cc-object-crosswalk).
- See also [Webex Contact Center bulk operations imports and export jobs](https://warmtransfer.net/knowledge/webex-cc-bulk-operations).

## Applicability

Applies to: Cisco Unified Contact Center Express and Cisco Webex Contact Center. Deployments: on-premises and multi-tenant. Sources checked 2026-09-22. The Unified CCX database steps apply specifically to Cisco Unified CCX deployments with IP IVR or Unified CCX Premium licensing[^11]. Field reports suggest that migration timelines of 3 to 6 months and call flow preservation patterns are reported from deployments in the United States region[^26][^25].

## What remains uncertain

Whether the Cisco UCCX discovery tool will support automated conversion or direct translation of Unified CCX Editor scripts into Flow Designer JSON formats is not covered by the sources below.

## Sources

[^1]: Webex Contact Center Flow Designer exposes activity output variables and event output variables as predefined variables that a flow reads after an activity runs. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions > Predefined variables > Event Output Variables; Activity Output Variables. Checked 2026-09-22.
[^2]: Unified CCX scripts are files with the .aef extension, and a subflow is selected by naming its .aef file. Source: [The Call Subflow Step - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/the-call-subflow-step/), The Call Subflow Step > General tab example, which names getNumbersToCall.aef. Checked 2026-09-22.
[^3]: Before the July 2026 Flow V2 announcement there was no public Webex Contact Center API for authoring or managing flows, so bulk or scripted flow work in that period had to go through the Flow Designer user interface (inferred). Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), July 29, 2026 entry, read against the absence of any earlier flow API announcement. Checked 2026-09-22.
[^4]: Webex Contact Center limits an individual audio file to 5,242,880 bytes and total audio storage to 2,097,152,000 bytes. Source: [System limits in Webex Contact Center](https://help.webex.com/en-us/article/n7s6ed7/System-limits-in-Webex-Contact-Center), System limits in Webex Contact Center > Audio file rows. Checked 2026-09-22.
[^5]: Webex Contact Center Bulk Operations accepts at most 5000 rows per CSV request, rejects CSV files larger than 5 MB, and accepts audio-file ZIP archives up to 50 MB. Source: [Bulk Operations in Webex Contact Center](https://help.webex.com/en-us/article/31e39g/Bulk-Operations-in-Webex-Contact-Center), Bulk Operations in Webex Contact Center > file limits. Checked 2026-09-22.
[^6]: Flows are not among the configuration object types that Webex Contact Center Bulk Operations can create, modify, import or export. Source: [Bulk Operations in Webex Contact Center](https://help.webex.com/en-us/article/31e39g/Bulk-Operations-in-Webex-Contact-Center), Bulk Operations in Webex Contact Center > list of supported configuration object types. Checked 2026-09-22.
[^7]: The Unified CCX Call Subflow step invokes another script from within a script, selecting the target script and an interruption setting on its General tab and carrying data on Input Mappings and Output Mappings tabs. Source: [The Call Subflow Step - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/the-call-subflow-step/), The Call Subflow Step > General, Input Mappings and Output Mappings tabs. Checked 2026-09-22.
[^8]: The Webex Connect Set Variable node for Webex Contact Center supports String, Boolean, Integer, Decimal and Date Time variables, and can add or update at most 30 variables per node. Source: [Set Variable - WXCC](https://help.webexconnect.io/docs/wxcc-set-variable), Set Variable - WXCC > supported data types and node limits. Checked 2026-09-22.
[^9]: Copy a flow is a documented Flow Designer operation, distinct from export and import. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage flows > Copy a flow. Checked 2026-09-22.
[^10]: Using Unified CCX database steps requires that the database subsystem and a Data Source Name be configured before the steps will work in a script. Source: [Database Steps - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/database-steps/), Database Steps > prerequisites. Checked 2026-09-22.
[^11]: The Unified CCX database steps require either a Cisco Unified IP IVR or a Cisco Unified CCX Premium license. Source: [Database Steps - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/database-steps/), Database Steps > licensing note. Checked 2026-09-22.
[^12]: The Unified CCX Editor Database palette contains four steps: DB Read, DB Get, DB Write and DB Release. Source: [Database Steps - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/database-steps/), Database Steps > palette contents. Checked 2026-09-22.
[^13]: Unified CCX database steps support varchar fields up to 255 characters and do not support varchar(max). Source: [Database Steps - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/database-steps/), Database Steps > field length restriction. Checked 2026-09-22.
[^14]: The CiscoDevNet webexcc-dbconnector sample is published under the MIT license and its 2.1.1 release is dated 3 March 2026. Source: [CiscoDevNet/webex-contact-center-dbconnector](https://github.com/CiscoDevNet/webex-contact-center-dbconnector), repository root > LICENSE and Releases. Checked 2026-09-22.
[^15]: Cisco's CiscoDevNet webexcc-dbconnector sample is a Spring Boot REST service that fronts a SQL database so that a Webex Contact Center flow can query it through the HTTP Request activity. Source: [CiscoDevNet/webex-contact-center-dbconnector](https://github.com/CiscoDevNet/webex-contact-center-dbconnector), repository README > overview and usage from Flow Designer. Checked 2026-09-22.
[^16]: Webex Contact Center flows for digital channels are built in Flow Builder in Webex Connect rather than in the voice Flow Designer, and support global variables and custom flow variables. Source: [Set up digital channels in Webex Contact Center](https://help.webex.com/en-us/article/n954r0k/Set-up-digital-channels-in-Webex-Contact-Center), Variables support for digital channels. Checked 2026-09-22.
[^17]: The Cisco UCCX to Webex Contact Center discovery tool extracts UCCX audio prompts as .wav files. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Run the discovery tool for migration > audio prompts. Checked 2026-09-22.
[^18]: Output from the UCCX discovery tool must be edited by hand to align the extracted UCCX configuration with the intended Webex Contact Center design before it is loaded through bulk operations. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Run the discovery tool for migration > edit the generated spreadsheet. Checked 2026-09-22.
[^19]: The Cisco UCCX to Webex Contact Center discovery tool extracts configuration for multimedia profiles, sites, user profiles, work types, auxiliary codes, agent profiles, address books, skill definitions, skill profiles, teams, entry points, outdial entry points, queues, outdial queues and users, and generates files for bulk import. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Run the discovery tool for migration > migrated object types. Checked 2026-09-22.
[^20]: The UCCX discovery tool requires Java 8 or above, network access to the Cisco Unified CCX server and administrator credentials. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Prepare for migration > prerequisites. Checked 2026-09-22.
[^21]: Moving data between a Unified CCX local script variable and an ICME script requires the Set Enterprise Call Info and Get Enterprise Call Info steps. Source: [Using Variables - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/using-variables/), Using Variables > Set and Get Enterprise Call Info steps. Checked 2026-09-22.
[^22]: The Cisco Unified CCX Editor is a graphical programming environment for creating, modifying, validating and debugging telephony and multimedia application scripts. Source: [Scripting Overview - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/scripting-overview/), Scripting Overview > description of the Unified CCX Editor. Checked 2026-09-22.
[^23]: Export a flow and Import a flow are documented Flow Designer operations under Create and manage flows in the Webex Contact Center administrator documentation. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage flows > Export a flow; Create and manage flows > Import a flow. Checked 2026-09-22.
[^24]: The Webex Contact Center Flow Designer activity library is organised into four groups: Contact Handling, Flow Control, Utilities and Voice. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Contact Handling / flow control / Utilities / Voice. Checked 2026-09-22.
[^25]: On one reported UCCX to Webex Contact Center engagement the customer chose to keep the existing call flow design and simplify it as much as possible rather than redesign it during the migration (field report). Source: [Challenges of Moving from Cisco UCCX to Webex Contact Center](https://www.telcion.com/blog/challenges-of-converting-from-cisco-uccx-to-webex-contact-center), section describing the client's call flow decision. Checked 2026-09-22.
[^26]: An integrator reporting on a completed UCCX to Webex Contact Center project stated that the transition can take three to six months depending on how many scripts have to be converted and the size of the existing environment (field report). Source: [Challenges of Moving from Cisco UCCX to Webex Contact Center](https://www.telcion.com/blog/challenges-of-converting-from-cisco-uccx-to-webex-contact-center), section on migration timeline. Checked 2026-09-22.
[^27]: On 29 July 2026 Cisco announced that administrators and developers can use a public Flow schema and Flow V2 APIs on the Webex Contact Center Developer Portal to author, validate and manage flows programmatically. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), July 29, 2026 > Programmatic Flow Design with public Flow Schema and new APIs. Checked 2026-09-22.
[^28]: Cisco states that the Flow V2 APIs let teams search, validate, publish, export, lock and unlock flows, subflows and functions while keeping changes deterministic, versioned and reviewable. Source: [What's new for administrators in Webex Contact Center](https://help.webex.com/en-us/article/a1gx3h/What's-New-in-Webex-Contact-Center), July 29, 2026 > Programmatic Flow Design with public Flow Schema and new APIs, second sentence. Checked 2026-09-22.
[^29]: Webex Contact Center Flow Designer treats functions as a first-class managed object, with documented procedures to create a function, manage functions and add a function to a main flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage functions > Important considerations, Create a function, Manage functions, Add a function to a main flow. Checked 2026-09-22.
[^30]: Cisco describes the Flow Designer Functions capability as letting administrators automate complex tasks, manipulate data and extend capabilities using scripting languages including Python. Source: [Flow Designer Enhancements: Transform Customer Interactions with Powerful New Features](https://blog.webex.com/customer-experience/flow-designer-enhancements-supercharge-every-customer-interaction/), Functions section. Checked 2026-09-22.
[^31]: Webex Contact Center documents an active global variable limit of 5000 per tenant. Source: [System limits in Webex Contact Center](https://help.webex.com/en-us/article/n7s6ed7/System-limits-in-Webex-Contact-Center), System limits in Webex Contact Center > Global variables row. Checked 2026-09-22.
[^32]: A Webex Contact Center global variable can be shown on the agent Desktop with a custom label and, if Edit on Desktop is enabled, edited by the agent during the interaction with the change saved within that session. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Manage global variables > Desktop visibility and Edit on Desktop. Checked 2026-09-22.
[^33]: At most 100 Webex Contact Center global variables can be enabled for reporting at any one time. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Manage global variables > Make Reportable. Checked 2026-09-22.
[^34]: Webex Contact Center global variables are defined centrally in Control Hub under Flows > Global Variables and are available across flows. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Manage global variables > where global variables are defined. Checked 2026-09-22.
[^35]: Cisco instructs administrators never to store secure data such as credit card numbers, personal identification numbers or social security numbers in Webex Contact Center global variables, because the values remain visible to users who can see historical records. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Manage global variables > caution on secure data. Checked 2026-09-22.
[^36]: The Webex Contact Center HTTP activity is the point of interface with external systems and lets the target system be configured centrally in Control Hub as a custom connector. Source: [Design Delightful Customer Experiences with Webex Contact Center Flow Designer](https://developer.webex.com/blog/design-delightful-customer-experiences-with-webex-contact-center-flow-designer), section on the HTTP Activity and Custom Connectors. Checked 2026-09-22.
[^37]: Webex Contact Center Flow Designer provides an HTTP Request activity in the Utilities group for calling external systems from a flow. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > HTTP Request. Checked 2026-09-22.
[^38]: Webex Contact Center Flow Designer documents JSON variables as a distinct variable concept alongside custom flow variables, predefined variables and global variables. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions > Custom variables; Predefined variables; Global variables; JSON variables. Checked 2026-09-22.
[^39]: Unified CCX local script variables are defined in the Variable pane of the Unified CCX Editor and belong to the individual script. Source: [Using Variables - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/using-variables/), Using Variables > local variables. Checked 2026-09-22.
[^40]: Webex Contact Center flow local variables can be passed to other flows through the GoTo activity or the Subflow activity. Source: [Design Delightful Customer Experiences with Webex Contact Center Flow Designer](https://developer.webex.com/blog/design-delightful-customer-experiences-with-webex-contact-center-flow-designer), section on variables and subflows. Checked 2026-09-22.
[^41]: Unified CCX has no organisation-wide variable store that all scripts read and write, so values shared across UCCX scripts must be carried in call variables, passed as subflow parameters, or persisted externally (inferred). Source: [Using Variables - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/using-variables/), Using Variables > variable categories (absence of any tenant-wide variable category). Checked 2026-09-22.
[^42]: Webex Contact Center Flow Designer has no native database or SQL activity, so UCCX DB Read, DB Get, DB Write and DB Release logic has to be re-expressed as calls to an HTTP service (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > full activity list across Contact Handling, flow control, Utilities and Voice. Checked 2026-09-22.
[^43]: Cisco publishes no automated converter from a Unified CCX script to a Webex Contact Center flow: the migration documentation's object list covers routing and resource configuration only, so call-handling logic has to be rebuilt in Flow Designer (inferred). Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Run the discovery tool for migration > migrated object types (no script, application, trigger or flow entry). Checked 2026-09-22.
[^44]: Webex Contact Center Flow Designer has no version control feature; the flow version number counts the number of times the flow has been published. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage flows > flow version behaviour. Checked 2026-09-22.
[^45]: Webex Contact Center Flow Designer provides a Parse activity in the Utilities group for extracting values out of a structured response. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Understand activities and events > Activities in Utilities > Parse. Checked 2026-09-22.
[^46]: Webex Contact Center flow expressions are written with Pebble template syntax, and Cisco documents a set of custom Pebble filters for use in flows. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Use variables and expressions > Writing expressions; Pebble template syntax; Custom Pebble filters. Checked 2026-09-22.
[^47]: A Unified CCX script is associated with an application and is invoked when the trigger associated with that application is dialled. Source: [Scripting Overview - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/scripting-overview/), Scripting Overview > relationship between script, application and trigger. Checked 2026-09-22.
[^48]: Webex Contact Center enforces per-activity self-loop limits in flows as a safeguard against unintended loops, with documented values including 100 for Menu, 100 for Collect Digits, 10 for Blind Transfer and 50 for Virtual Agent. Source: [System limits in Webex Contact Center](https://help.webex.com/en-us/article/n7s6ed7/System-limits-in-Webex-Contact-Center), System limits in Webex Contact Center > self-loop limits for Flow Designer activities. Checked 2026-09-22.
[^49]: Unified CCX script steps are themselves written in Java, but Cisco states that a script author does not need to understand Java programming to build a Unified CCX script. Source: [Scripting Overview - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/scripting-overview/), Scripting Overview > steps and the design pane. Checked 2026-09-22.
[^50]: The Webex Contact Center Subflow activity packages reusable functionality for use in any number of flows, passing inputs into the subflow and returning outputs to the main flow. Source: [Design Delightful Customer Experiences with Webex Contact Center Flow Designer](https://developer.webex.com/blog/design-delightful-customer-experiences-with-webex-contact-center-flow-designer), section describing the new Subflow activity. Checked 2026-09-22.
[^51]: A Unified CCX Call Subflow input mapping may pass any valid expression, and Unified CCX evaluates all such expressions before calling the subflow and stores the results in the named subflow variables. Source: [Input Mappings tab (Call Subflow step) - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/input-mappings-tab-call-subflow-step/), Input Mappings tab (Call Subflow step) > expression evaluation. Checked 2026-09-22.
[^52]: A Webex Contact Center flow developer can map a global variable from the main flow to a local variable in a subflow, but cannot add global variables directly inside the subflow. Source: [Manage global variables](https://help.webex.com/en-us/article/ngfdsbi/Manage-global-variables), Manage global variables > global variables in subflows. Checked 2026-09-22.
[^53]: Webex Contact Center subflows offer a Propagate changes to all flows setting, so an edit to a shared subflow can be pushed into every flow that uses it. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Subflows section. Checked 2026-09-22.
[^54]: In a Unified CCX Call Subflow input mapping, a main-script variable can be mapped only to a subflow variable of the same type. Source: [Input Mappings tab (Call Subflow step) - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/input-mappings-tab-call-subflow-step/), Input Mappings tab (Call Subflow step) > mapping rules. Checked 2026-09-22.
[^55]: Cisco's official Webex Contact Center flow template samples are distributed as JSON files intended for use in Flow Designer. Source: [WebexSamples/webex-contact-center-flows](https://github.com/WebexSamples/webex-contact-center-flows), repository README > template contents and file naming. Checked 2026-09-22.
[^56]: Cisco states that the UCCX migration tool is continuously evolving and may not currently support all the latest features. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Run the discovery tool for migration > note on tool coverage. Checked 2026-09-22.
[^57]: A Webex Contact Center flow must be validated and its errors fixed before it can be published, and the Publish button stays disabled until all errors are resolved. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Create and manage flows > Validate a flow and Publish a flow. Checked 2026-09-22.
[^58]: Cisco documents three categories of variable available to a Unified CCX script: local script variables, Cisco predefined enterprise call variables, and Expanded Call Context variables. Source: [Using Variables - Contact Center Express](https://developer.cisco.com/docs/contact-center-express/using-variables/), Using Variables > variable categories. Checked 2026-09-22.
[^59]: Webex Contact Center supports applying version labels such as Dev, Test and Live to a flow and selecting a labelled version at the entry point, enabling blue-green style promotion. Source: [Rapidly Adapt Your CX Workflows With Webex Contact Center Flow Designer](https://developer.webex.com/blog/rapidly-adapt-your-cx-workflows-with-webex-contact-center-flow-designer), Flow Versioning section. Checked 2026-09-22.