Before upgrading, ensure that the system is idle, i.e, all agents are logged out from the AgentDesk.
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.
-
Update Helm repo
helm repo update expertflow -
Deploy the ActiveMQ helm chart
helm show values expertflow/activemq --version 4.10.6 > helm-values/ef-activemq-custom-values.yaml helm upgrade --install=true --namespace=ef-external --values=helm-values/ef-activemq-custom-values.yaml activemq expertflow/activemq --version 4.10.6 -
Deploy the AgentDesk helm chart
# 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 4.10.6
“Agent MRD Interrupted” Flow Modified in Conversation Studio
Note: Please take backup/export of your existing flow from conversation studio before any change
A new node for Agent MRD Interrupted flow has been added as part of the selecting different actions for Interrupted Conversations. This node supports the action to put a conversation on hold that has been interrupted. For more details on the Interrupted Conversations, please refer to its feature document.
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 (see the 'Agent MRD Interrupted' section—1st heading) 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 expertflow statefulset ef-cx-conversation-studio
b. Delete the existing Persistent Volume Claim (PVC) for Conversation Studio:
kubectl delete -n expertflow 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 expertflow/cx --version 4.10.6 -
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 4.10.6 -
Deploy the Campaign 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 4.10.6 -
Deploy the QM helm chart
# 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 4.10.6