Switches

Some of Xema's behaviour is switched on or off for the whole cluster. Each switch is off until someone turns it on, and each is set from any server in the cluster with the xema command. A change takes effect within seconds, on every server, without restarting anything.

They are all under one command:

xema flags                       # every switch, and whether it is on
xema flags fields                # the switches that can be set
xema flags set <switch>=on       # turn one on (off, true, false, yes and no also work)

More than one switch can be set at once: xema flags set callHistory=on missedCalls=on.

Upgrading from a release before xema flags: a switch that was turned on before is off after the upgrade, and is turned on again with xema flags set. Run xema flags before upgrading and note what is on.

Queue recovery

What happens to callers who are waiting in a queue when the queue service restarts: during an upgrade, after a crash, or when its connection to the phone system drops and comes back.

Switch	Off (the default)	On
`requeueOrphans`	Each waiting caller is sent back to the call flow that put them in the queue, which carries on from the step after the queue. In most flows that ends the call.	Each waiting caller goes back into the queue they were in, in the place they had, and their waiting time carries on from when they first joined.

With requeueOrphans on, a caller still goes back to their flow when Xema cannot tell which queue they were in, or when their queue is no longer run on that server. A caller whose call an agent had already answered is left to be connected to that agent.

A caller put back into their queue is not counted as a second arrival: queue reports and call records show one wait.

xema flags set requeueOrphans=on

When to turn it on: on any cluster where a queue may restart while callers are waiting, which includes every upgrade of the queue service. Try it on a test server first: put a caller in a queue, restart the queue service with xema restart queue, and check that the caller is still waiting in the same place.

Agent features

Which optional parts of the agent's screen the cluster offers, and one rule for agents' phones.

Switch	When on
`crmDashboard`	The agent's screen shows the CRM dashboard panel.
`callHistory`	Agents can see their own call history.
`missedCalls`	Agents are shown the calls they did not answer.
`myDay`	Agents are shown a summary of their day so far.
`demoContent`	Content marked as demonstration material is shown, across the cluster.
`requirePhoneOnAgentAddress`	A phone that registered from a different address from the one the agent signed in from is refused.

xema flags set myDay=on