New features&fixes:Amethyst Administration interface 1.5.1.0

[Belinda Frick]

New features and fixes in the Amethyst Administration interface 1.5.1.0

Fixes:

Problem:
When a new template is created, the first question of each category does not save its score the first time.
The score is only saved when the score is saved for the second time.

Completion:
This problem only happened when the first question was added for a category.
The problem has been fixed.

Problem:
If the hostname of the Amethyst server is changed to a name that contains the previous name, the webadmin hangs.
For example, if the old name was amethyst and the new name is amethyst123, the webadmin will hang.

Completion:
Bug has been fixed.

Problem:
When a new Amethyst is installed, it has no recordings. The period between no recordings and the 21st recording
is the pre-evaluation mode.The 21st recording will be the install date for Amethyst. If Amethyst is licensed in
the pre-evaluation mode, Amethyst will keep on expiring.

Completion:
This bug has been fixed. If Amethyst is licensed in the pre-evaluation mode,
the install date gets set to the licensed date.

Problem:
The change log file is a list of files that still need to be archived. If this file does not exist, the purge will
not start. The webadmin must purge even if the change log does not exist.

Completion:
The Amethyst purge facility will purge the old data, even if there is no change log file.

Problem:
When a supervisor is modified, all the users are not in the list of available users. If there are two names where
the second one contains the first, the first will not be displayed. e.g. Amethyst and Amethyst recorder. The first
one will not display if you change a supervisor.

Completion:
When the second user contained the first, the first did not display.
This problem has been fixed.

Problem:
When an Amethyst solution has multiple card servers that are recording trunk side on multiple PABX's, the allowed
extensions are configured globally. Multiple PABX's can have duplicate extensions, which mean some licenses are
being used on multiple card servers. The extensions must be linked to a specific card server. Please take into
consideration that on some sites multiple card servers will be linked to one PABX and then the extensions must be
linked to all the card servers as if it is one server.

Completion:.
When an accepted extension in configured, the card servers that the extension must be accepted from must be set.
If there are no card servers configured, the extension will be accepted from all the card servers.

New features:

Motivation:
I need a place where I can see how many agents are currently in use. Only when you are using a card solution, does
the system report on how many licenses are available for the agents.

Completion:
On the license screen where the number of agent licences display, the number of available licences will be displayed.

Motivation:
Can the maintenance screen for virtual extensions be changed to allow the sorting of the extension and/or the user names.
When you have more than 1 screen full of agents to maintain, it becomes difficult to find the correct entry to update.

Completion:
By default the list will be sorted by the agent name. When you click on the vitual extention title, the list will be
sorted by the virtual extension number. Click on the user name title to sort the list by user.

Motivation:
Amethyst displays its log files in groups of 100 lines. This speeds up the display for large log files.The display of
the card server log file must work on the same principal.

Completion:
The cardserver log file will be displayed on pages of a 1000 lines each.

Motivation:
You need to configure the IP addresses of the cardservers in Amethyst, but this can get confusing when there are multiple
servers. Amethyst needs to save a display name for each configured IP address. This will help with configuration.

Completion:
When an IP address is added for a cardserver, there is a optional edit box for the display name. This name will display
with the IP address in brackets where the configuration and displays are chosen.

Motivation:
If the ftp address changes at a Amethyst installation, the ftp addresses need to be changed manually for each client.
There must be a feature where all clients can be changed from the webadmin.

Completion:
On the Amethyst home page there is a new option called Redirect clients to FTP address. Click on the option and a page will
display where the new FTP IP can be entered. To broadcast the new FTP address to all clients, click on the Apply Changes
button.

Motivation:
When log files get large on the Amethyst server, the webadmin takes long to display the log. The webadmin needs a better
way to display the large log files.

Completion:
When the user clicks on the View log files link, the Webadmin does not default to the sweeper log anymore. The user can
choose the desired log file from there. At the bottom of the screen there are links to change the current date to any
day inthe previous 6 months. The log files will be displayed in pages of 100 lines each. This will speed up the display
of large log files.

Motivation:
On the Amethyst webadmin, you can redirect all the clients to the current Amethyst server ip or hostname. This feature
must broadcast its IP or hostname out over the network and not just to the list of current users.

Completion:
When using the redirect IP/Hostname feature, Amethyst broadcast to the broadcast IP. This broadcast will not go through
network subnets.

Motivation:
The plugins for the SMDR link must begin with uppercase P, but there are plugins that went out with lowercase p's.
The Webadmin must load plugins that begin with both cases.

Completion:
Feature added. Both types of plugins will display in the drop down list.