Layton ServiceDesk - Release Notes - Version 6.6.4

Back to List

Earlier Version Later Version

Overview

ServiceDesk v6.6.4 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.

Determining the Currently Installed Version

Please refer to this article to determine the currently installed version.

Obtaining the Update

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

Test Installation

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

Known Issues

On launch, you may see this error:

   Description: The application attempted to perform an operation not allowed by the security policy.
   To grant this application the required permission please contact your system administrator or change
   the application's trust level in the configuration file.
   
   Exception Details: System.Security.SecurityException: Request for the permission of type
   'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

Please refer to this article for the fix.

This will be resolved in a future update.

Upgrade Procedure

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

1. Extract the lsd664_upgrade folder from the archive
2. Back up your database
3. In Windows Services Console:
   1. Stop the IIS Admin service
   2. Stop the LaytonServiceDesk service
4. Open the lsd664_upgrade folder.
5. Right-click the installer lsd664_upgrade.exe and select Run as administrator. This will avoid permission issues.
6. In Windows Services Console, start the IIS Admin and LaytonServiceDesk services.

New Features

#	Title	Description
66615	Business Rule Action: Change Status on End User Comment	You can now create rules based within a specified number of Working Hours that an End User comment has been made. Example: If a Request is on hold and the End User comments within 2 days, the status can be changed to Open. See example here.

Bug Fixes

#	Title	Description
66360	PDF Report Attachments Are Blank	A new PDF engine has been implemented to resolve issues with large amounts of data being written to the PDF file. Please refer to the new section Temporary File Storage in Scheduling Reports for a caveat.
66643	Error in Calculating Elapsed Time in Business Rule	For the sys_changestatus_date and sys_lastcommentdate fields used as criteria, the value has been changed from days to number of Working Hours. This was necessary to resolve date math used in checking expiry of these fields. If you previously configured a Business Rule with these fields, they will need to be edited.

Released 2016-09-20