...
Buckets
The first step is to consider define buckets into which values are placed. Each bucket will ultimately be used to define the colors used, into which the values will be placedCSS used (e.g. for foreground and background colors) with which the value will be rendered.
| Info | ||
|---|---|---|
| ||
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 the each bucket is shown in the table below. (We will see how to apply this later).
...
A bucket definition is a comma separated list of integers. Ihe 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:
| Info | ||
|---|---|---|
| ||
|
...
|
For our example, the bucket definition 80,60,0 can be used - defining three buckets with thresholds of 80, 60 and 0 respectively.
- If the value is >= 80 it will be placed in bucket 0. Whilst it could fit into all buckets, the bucket with the highest threshold is bucket 0, and this one will "win".
- If the value is >= 60 but < 80, it will be placed in bucket 1. If could fit into buckets 1 or 2, but bucket 1 hast the highest threshold and will "win".
- If the value is < 60 it can only fit into the third bucket.
| Info |
|---|
Note: 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 for our example. However, this principle can be used safely - simply not having a bucket definition for a range of values will result in no CSS being applied and the value will appear as usual (black text on the grey zebra striped background). |
Attaching Buckets to Columns
Buckets are attached to columns, by defining:
- A User Setting (these can be defined by each user individually in User Master Data)
- An ACD Group Parameter (only used for values associated with ACD Groups - in the ACD Groups ... Parameters Tab for each ACD Group individually).
- A Client Parameter setting (these can be defined for the client account as a whole in Client Master Data)
The order of processing is as follows:
- If the user has defined a setting, use this setting.
- Otherwise: If the value is associated with an ACD group, check the ACD group parameters and use the setting if found.
- Otherwise: Check the Client Parameters for the appropriate setting.and use this setting if found.
- Otherwise: no setting is configured, no processing will occur.
The actual settings required are documented in the table further below.
For our example, we need the settings: