BREAKING CHANGE NOTICE
This update will be implemented in the next release and requires action from all teams using CX as Code Accelerators.
Division Parameters are Now Mandatory
Starting with the next release, division parameters will be required for most accelerator modules. Teams must update their accelerator pipelines and Terraform configurations to include division values.
Action Required
Please update your pipelines before the next release to avoid deployment failures.
Overview
We've completed a comprehensive audit and update of all CX as Code Accelerator modules to improve consistency, fix division handling, and resolve file content hash issues. This update affects 29 out of 37 accelerator modules across the repository.
Key Changes
Fixed and standardized division handling across all modules to ensure proper resource isolation:
-
- ✅ Added missing division_id parameters to resources that support divisions
- ✅ Standardized division variable naming conventions
- ✅ Fixed division data source references
- ✅ Converted hardcoded home division to configurable variables
- ⚠️ Division parameters are now mandatory for 29 out of 37 modules
Modules Requiring Division Input - NO DEFAULT (12 modules):
-
- agent_rewards_external_metrics
- agent_timeoff
- ani_blacklist
- auto_offer_callback
- automated_callback_using_campaign
- dx_sample_spec
- example_accelerator_metadata
- gc_presence_update_from_ms_teams
- guide_accelerator
- send_message_transcript_by_email
- servicenow_unified_experience
- simple-ivr-deploy
- sms-followup-on-missed-callback
- terminate_voice_calls_with_no_queue_no_pbx
- terminate_voice_calls_with_no_queue_pbx
- web_messaging_triage_bot
- workitems_accelerator
Modules with Division Input - WITH DEFAULT VALUES (4 modules):
-
- create_direct_routing_queue (defaults to empty string, falls back to home division)
- initiate_direct_routing (defaults to empty string, falls back to home division)
- send_email_notification_when_outbound_message_fails (defaults to "Home")
- update-gc-presence-on-communicate-call (defaults to "Home")
Modules with Division Support Added (8 modules - previously hardcoded or missing):
-
- adjust_schedule_start_time ✨ NEW
- design_architect_flow_data_actions_for_resiliency ✨ NEW
- external_metrics ✨ NEW
- gcnow_new_org_init ✨ NEW
- public_api_data_action_install ✨ NEW
- schedule_callback_via_script ✨ NEW
- survey_sms_delivery ✨ NEW
- wem_support ✨ NEW
Modules NOT Using Division (8 out of 37 modules):
-
- create_external_contact_data_action
- get_data_table_row_data_action
- get_user_queues_data_action
- journey_view_template_accelerator
- salesforce_data_action_accelerator
- servicenow_data_action
- set_user_state_data_action
- zendesk_data_action_install
Required Actions for Teams
BEFORE the Next Release:
1. Update Your Pipeline Configurations
Add division parameters to your Terraform variable files or pipeline configurations:
# Example: terraform.tfvars or pipeline variables
division_name = "YourDivisionName"
2. Test in Development Environment
-
- Division parameter usage are in DCA environment
- Deploy accelerators in your dev environment with division parameters
- Verify resources are created in the correct division
- Confirm flows and integrations work as expected
3. Update CI/CD Pipelines
Ensure your automated deployment pipelines include division variables
Impact Assessment
Breaking Changes: ⚠️ HIGH IMPACT
What Will Break:
-
- Pipelines that don't provide division parameters will fail for 17 modules (those without defaults)
- Existing deployments may need to be updated to include division references
- Terraform plans will show changes if division wasn't previously specified
What Won't Break:
-
- Modules with default division values will continue to work (4 modules)
- Modules that don't use divisions are unaffected (8 modules)
- Existing resources won't be destroyed, but may show as modified
Benefits:
-
- Proper resource isolation in multi-division environments
- Consistent division handling across all accelerators
- More flexible deployment options
Timeline
- DCA/TCA - Build #556, January 22, 2026
- PROD - Mid March 2026
For questions or issues, contact the CX as Code team.
#CXasCode------------------------------
Catherine Agnes Corpuz
Software Development Engineering Manager
------------------------------