Upgrade Guide CX5.13.0 to CX5.13.1 | Expertflow CX

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.

Add and Update Helm repo

helm repo add cim-solution https://gitlab.expertflow.com/api/v4/projects/471/packages/helm/stable --username efcx --password w4eYTsMuHqLbq5lkFLDI4G86MQp1OjU0CA.01.0y023xsty
helm repo update cim-solution

Clone the CX repository on the target server

Bash

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

Deploy the AgentDesk Helm chart

SQL

# 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 cim-solution/agent-desk --version 5.13.1

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 cim-solution/channels --version 5.13.1

“Participant Role Changed” Flow Modified in Conversation Studio
Note: Please take backup/export of your existing flow from conversation studio before any change

In participant role change flow, we have handled the case of the chats for the channels eg facebook, instagram and email, if agent ends the chat (primary), by default we should close the conversation.

If you are using custom flows for Conversation Studio:

Please add the flow changes manually. After deploying the Core helm chart, refer to the Conversation Studio default flows documentation and update your customized flow accordingly.

If you are using default flows for Conversation Studio (This will remove all existing flows, please only follow the below in case you are using default flows):

Execute the commands below before deploying the Core Helm chart.

a. Delete the Conversation Studio StatefulSet:

kubectl delete -n <tenant-namespace> statefulset ef-cx-conversation-studio

b. Delete the existing Persistent Volume Claim (PVC) for Conversation Studio:

kubectl delete -n <tenant-namespace> pvc conversation-studio-flow-vol-ef-cx-conversation-studio-0

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 cim-solution/cx --version 5.13.1

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  cim-solution/MTT-single --version 5.13.1

Deploy the Survey and Mysql Reports

Clone the Repo

# Clone the repo
  git clone -b 5.13.1 https://efcx:w4eYTsMuHqLbq5lkFLDI4G86MQp1OjU0CA.01.0y023xsty@gitlab.expertflow.com/cim/cim-solution.git 5.13.1

Survey Reports

Bash

# Copy 5.13.1/kubernetes/external/metabase-reports/metabase_reporting_update_tool/survey/
 To <current-active-directory>/external/metabase-reports/metabase_reporting_update_tool/

cd <current-active-directory>/external/metabase-reports/metabase_reporting_update_tool/

python3 metabase_import.py https://FQDN/metabase/api/ "email" "password" "database" "survey" "Collection Name"

Mysql Reports

# Copy 5.13.1/kubernetes/external/metabase reports/metabase_reporting_update_tool/mysql/
 To <current-active-directory>/external/metabase-reports/metabase_reporting_update_tool/

cd <current-active-directory>/external/metabase-reports/metabase_reporting_update_tool/

python3 metabase_import.py https://FQDN/metabase/api/ "email" "password" "database" mysql "Collection Name"

Configuration

Add FILE-ENGINE-PUBLIC-URL string2000 attribute to MS Exchange, Facebook, and Instagram channels set to tenant's Public File Engine URL. (e.g., [https://iac01.expertflow.com/file-engine])