1. Description

The page on which the collected information about events in the system is accumulated.

It consists of the following elements:

1. Filter block (Fig.1(1));

2. Search field (Fig.1(2));

3. Refresh button (Fig.1(3));

4. Registry (Fig.1(4));

5. Pagination (Fig.1(5)).

Open

Fig. 1. Logs tab

1.1. Filter block 

It is designed to filter the data displayed in the registry entries.

It consists of the following elements::

1. Filtering fields (Fig.2(1));

2. Reset filters button (Fig.2(2));

3. Expant filters button (Fig.2(3)).

Open

Fig. 2. Filter block

1.1.1. Filtering fields

Available fields for filtering:

• Start: From;

• Start: To;

• Result;

• Agent;

• Duration (From and To fields).

1.1.2. Reset filters button

1.1.3. Expant filters button

1.2. Search field 

The search is performed on the Destination column.

1.3. Refresh button

(Fig.1 (3)).

1.4. Registry

The registry is a list of entries of existing objects in this partition, each of which consists of a set of fields:

1. Destination;

2. Agent;

3. Start;

4. End;

5. Offering;
   
   

6. Duration;

7. View number;

8. Attempt;

9. Result.

1.4.1. Destination

Here the numbers of Subscribers with whom there was an interaction, or other data depending on the task, are displayed. The absence of a value in this column is acceptable.

1.4.2. Agent

The name of the Agent with which the connection was attempted.

1.4.3. Start

The time of the start of an interaction - getting into the Queue.

1.4.4. End

The time of the end of an interaction - getting into the Queue.

1.4.5. Offering

The time when the task was offered to the Agent. The field will be empty if no offer has taken place.

1.4.6. Duration

Duration of interaction with the Queuing mechanism. It is counted from when the interaction began to when it ended.

1.4.7. View number

The number that the Member displays on their device when they call. How to set a number can be found here.

1.4.8. Attempt

Here the number of attempts to process this is Member displayed.

The field is empty if this is a canceled first processing attempt.

You can cancel the attempt in the Pre-executive schema.

1.4.9. Result

There are such options:

• missed;

• timeout;

• failed (the task was not connected to the Agent);

• abandoned (no follow-up connection expected);

• success.

1.5. Pagination