5.12.0 5.11.0 5.10.0 5.9.0 5.8.0 5.7.0 5.6.0 5.5.0 5.4.0 5.3.0 5.2.0 5.1.0 5.0 4.10 4.9 4.8 4.7 4.6 4.5.3 4.5.2 4.5.1 4.5 4.4 4.3
5.12.0 5.11.0 5.10.0 5.9.0 5.8.0 5.7.0 5.6.0 5.5.0 5.4.0 5.3.0 5.2.0 5.1.0 5.0 4.10 4.9 4.8 4.7 4.6 4.5.3 4.5.2 4.5.1 4.5 4.4 4.3

Upgrade Guide CX5.11.0 to CX5.12.0

Before upgrading, ensure that the system is idle, i.e, all agents are logged out of the AgentDesk.
Flush Redis before upgrading

Custom Configuration Strategy

For detailed guidelines on applying environment-specific configurations using custom values.yaml layering,

Refer to the CX Helm Chart Custom Configuration Strategy guide.

  1. Update Helm repo

    helm repo update expertflow
    
  2. Clone the CX repository on the target server

    Bash
    # Create CX-5.12.0 directory from root
    mkdir CX-5.12.0
    # Navigate to CX-5.12.0
    cd CX-5.12.0
    # Clone the CX-5.12.0 branch of the cim-solution repository
    git clone -b CX-5.12.0 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/cim-solution.git $HOME/CX-5.12.0
    # Navigate to the current release /kubernetes
    cd <current-release>/kubernetes
    

APISIX Authorization is enabled by default in 5.12.0 and onwards;
APISIX enable/disable guide and Integration & Token Refresh guide

  1. Update Application Gateway (APISIX)

    # Update the apisix-custom-values.yaml file 
    # Make sure to save any customisation and add it once the apisix-custom-values.yaml is updated.
      helm show values expertflow/apisix --version 5.12.0 > helm-values/apisix-custom-values.yaml
      helm upgrade --install --namespace ef-external --values helm-values/apisix-custom-values.yaml apisix expertflow/apisix --version 5.12.0
    

APISIX Authorization is enabled by default in 5.12.0 and onwards; you can disable it by updating the parameter below in apisix-custom-values.yaml

oidc: enabled: false

  1. Deploy the AgentDesk Helm chart

    SQL
    # Copy the unified agent translation directory to the current release
      Copy from 5.12.0/kubernetes/pre-deployment/app-translations/unified-agent/i18n/   To ./pre-deployment/app-translations/unified-agent
    # Run script from <kubernetes> diectory, to update the translations
      chmod +x scripts/upload_agent_desk_translations.sh
      ./scripts/upload_agent_desk_translations.sh
    # Deploy the new chart version using the helm-values/cx-agent-desk-custom-values.yaml 
      helm upgrade --install --namespace expertflow --set global.efCxReleaseName="ef-cx" cx-agent-desk --debug --values helm-values/cx-agent-desk-custom-values.yaml expertflow/agent-desk --version 5.12.0
    
  2. Deploy the Campaigns Helm chart

    # Deploy the new chart version using the helm-values/cx-campaigns-custom-values.yaml
      helm upgrade --install --namespace expertflow   --set global.efCxReleaseName="ef-cx"  cx-campaigns --debug --values helm-values/cx-campaigns-custom-values.yaml expertflow/campaigns --version 5.12.0
    
  3. Deploy the Channels Helm chart

    # Deploy the new chart version using the helm-values/cx-channels-custom-values.yaml 
      helm upgrade --install --namespace expertflow --set global.efCxReleaseName="ef-cx" --debug cx-channels --values helm-values/cx-channels-custom-values.yaml expertflow/channels --version 5.12.0
    
  4. Deploy the Core Helm chart

    # Deploy the new chart version using the helm-values/ef-cx-custom-values.yaml  
    
      helm upgrade --install --namespace expertflow --create-namespace ef-cx --debug --values helm-values/ef-cx-custom-values.yaml expertflow/cx --version 5.12.0
    
  5. Deploy the MTT Helm chart

    # Deploy the new chart version using the helm-values/mtt-single-custom-values.yaml 
      helm upgrade --install --namespace <tenant-ns> --debug  <tenant-id> --values helm-values/mtt-single-custom-values.yaml  expertflow/MTT-single --version 5.12.0
    
  6. Deploy QM <optional>

    # Deploy the new chart version using the helm-values/cx-qm-custom-values.yaml
    
      helm upgrade --install --namespace=expertflow --set global.efCxReleaseName="ef-cx" qm  --debug --values=helm-values/cx-qm-custom-values.yaml expertflow/qm --version 5.12.0
    
  7. Deploy the CX Reporting Helm Chart

    # Deploy the new chart version using the helm-values/cx-reporting-scheduler-custom-values.yaml
    
    helm upgrade --install --namespace <tenant-namespace> --set global.efCxReleaseName="ef-cx"   cx-reporting --debug --values helm-values/cx-reporting-scheduler-custom-values.yaml  expertflow/reporting  --version 5.12.0
    
  1. Deploy the Transflux Helm Chart

    git clone -b 5.12.0 https://efcx:RecRpsuH34yqp56YRFUb@gitlab.expertflow.com/cim/transflux.git 5.12.0
    
    # Copy the following files to your current directory
      config/bulk_upload_config_template.yaml to <transflux-current-dir>/config/
      config/qm_cisco_team_sync_config.yaml to <transflux-current-dir>/config/
      
    # Delete the existing configmaps ‘ef-transflux-config-cm' using the commands:
      kubectl -n expertflow delete configmap ef-transflux-config-cm
    # Now re-create the configmap using the following commands from the transflux directory:
      kubectl -n expertflow create configmap ef-transflux-config-cm --from-file=config
      
    # Re-deploy CX-Transflux
      helm upgrade --install --namespace expertflow   --set global.efCxReleaseName="ef-cx"  cx-transflux --debug --values helm-values/cx-transflux-custom-values.yaml  expertflow/transflux --version 5.12.0
    
  2. Voice upgrade guide

Configurations:

  1. OAuth2 Token Lifespan Configuration
    Update the token configurations for all the tenants by using the following guide

  2. Update Keycloak Permissions
    Update Client Authorization Permissions in Keycloak for all tenants by using the following guide.

  3. Update Compliance DNC permissions
    KeyCloak : Use Tenant → Clients → cim → Authorization → Import keycloak-compliance-dnc-auth.json

  4. Add a new Realm role for the Queue Flush API
    Steps to create and assign a user with the client-admin role per tenant:

    1. Go to Keycloak > Realm Roles Tab

    2. Create a role: client-admin

    3. Go to the Users tab and assign this role to the admin user/ user generating the token

  5. Expose nodePorts for CX services (required only if CX VOICE is deployed)
    Use the following guide to expose the nodePorts for CX services.