Layton ServiceDesk - Release Notes - Version 6.6.1

Back to List

Earlier Version Later Version

Overview

ServiceDesk v6.6.1 is a minor release of the product. You must be using ServiceDesk v6.2.0 or later before you can upgrade to the latest version. If you are using an earlier version please upgrade by downloading v6.2.0 from the Update > Layton ServiceDesk menu in the Client Support Portal before attempting to upgrade to the latest version.

Obtaining the Update

Please log in to the Client Support Portal to download the upgrade installer.

Test Installation

We recommend that you do a Test Installation and upgrade it before committing to updating your live system.

Procedure

Do not uninstall Layton ServiceDesk prior to upgrading. This is an update, not a full installer.

1. Extract the lsd661_upgrade folder from the archive
2. Back up your database
3. Stop the IIS Admin service
4. Stop the LaytonServiceDesk service
5. Run the upgrade installer lsd661_upgrade.exe inside the lsd661_upgrade folder. We recommend that you right-click the installer and select Run as administrator to avoid permission issues.
6. Start the IIS Admin and LaytonServiceDesk services.

New Features

#	Title	Description
65345	User Fields as Criteria in Business Rules	User-defined fields can now be used as both criteria and in actions.
65998	Different Email Settings for Different Request Classes	New setting for Request Class properties. Allows for rerouting of return emails from notifications.
66151	Link Requests Search Option	Problems and Changes can now be searched in the Request-form Links interface.

Bug Fixes

#	Title	Description
65780	Broken Search Page	If an End User was populated by going through the picker and End User search dialog, when the Search button was clicked, the page would break.
66117	Duplicate Entry in Combo Box After Application of Business Rule	If updated by a Business Rule, a user-defined combo box would have the populated value replicated so that it would appear twice.
66138	LSD Delete Analyst Feature Not Working	Deleting an Analyst who was associated with Requests would move the associations but would not complete the deletion process.