It is possible to setup thresholds for values in table columns in the supervisor.
The mechanism to perform this involves a combination of setting the threshold values - i.e. setting up values to go into "buckets", and then configuring CSS styles to color these elements.
To make our example easy to understand, we will take the Availability and Service Level counters from the ACD groups.
We want the service level to be colored green when it is 80% or above, yellow when it is 60% or above and red otherwise.
The first step is to define buckets into which values are placed. Each bucket will ultimately be used to define the CSS used (e.g. for foreground and background colors) with which the value will be rendered.
CSS experts: you can add whatever you want including animations and effects. |
The number of buckets you configure is not restricted, however, to keep the CSS simple, we will consider three buckets in the following examples.
The CSS definition which will be used by each bucket is shown in the table below. (We will see how to apply this later).
Bucket | Colouring | CSS Definition |
---|---|---|
0 | Green | background-color: #169A13; |
1 | Yellow | background-color: #FCC10F; |
2 | Red | background-color: #BB0F18; |
The following shows an example of values rendered using the three definitions above:
First of all, we will consider a three bucket definition using the buckets 0, 1 and 2 above (green, yellow, red - like a traffic light).
A bucket definition is a comma separated list of integers. The first value in the list is bucket 0, and so on.
When the system renders a value in a column, in order to decide what CSS rules to apply, it compares the value with the threshold all of the buckets defined using the following algorithm:
|
For our example, the bucket definition 80,60,0 can be used - defining three buckets with thresholds of 80, 60 and 0 respectively.
Note: in our example if the value was negative, it would not fit into any bucket and no CSS rules would be applied. Since a service level should never be less than 0, this will not matter. However, the principle of not having a bucket which fits a value can be used safely - if a value is not placed in a bucket, no CSS rules will be applied and the value will appear as usual (black text on the grey zebra striped background). |
Buckets are attached to columns, by defining:
The order of processing is as follows:
The actual settings required are documented in the table further below.
For our example, we need to configure the settings:
Here the 4 example settings are shown configured in the User Settings for the logged in user:
Setting Name | Column | |
---|---|---|
Thresholds.AcdSupervisor.Agents.AcdLoginTotalCallsAllGroups | Calls (all) | |
Thresholds.AcdSupervisor.Agents.AcdLoginTotalCallsCurrentGroup | Calls (Group) | (group details page) |
Thresholds.AcdSupervisor.Agents.AgentStatusDuration | Agent Status Duration | |
Thresholds.AcdSupervisor.Agents.AgentsCallsPerHour | Calls (hour) | |
Thresholds.AcdSupervisor.Agents.DiallerSuccessToday | Dialler Success | |
Thresholds.AcdSupervisor.Agents.AgentsPostCallDurationAverage | PC Ø | |
Thresholds.AcdSupervisor.Agents.AgentsPostCallPerHour | PC/h | |
Thresholds.AcdSupervisor.Agents.AvailabilityTimer | Available for | |
Thresholds.AcdSupervisor.Agents.BusyNoAnswer | Busy / No Ans. | This column contains two values - the number of busy calls to the agent, and the number of no answer calls to the agent. The values are added together and then the corresponding bucket is determined. |
Thresholds.AcdSupervisor.Agents.GroupStatusDuration | Group Status Duration | (group details page) |
Thresholds.AcdSupervisor.Agents.LoginDuration | Login Duration |