Layton ServiceDesk - Release Notes - Version 6.5.7
From Layton Support
(Difference between revisions)
(Added Bugs 343 and 344) |
(Added Bugs 347, 349, 354, 362) |
||
| Line 28: | Line 28: | ||
|-style="vertical-align:top;" | |-style="vertical-align:top;" | ||
|342 | |342 | ||
| − | |Column | + | |Column ''(No Company)'' in Report |
|In the ''Request Statistics by Company'' report, a number of Requests appeared against the Company ''(No Company)'', despite the associated End Users having an assigned Company. | |In the ''Request Statistics by Company'' report, a number of Requests appeared against the Company ''(No Company)'', despite the associated End Users having an assigned Company. | ||
|-style="vertical-align:top;" | |-style="vertical-align:top;" | ||
| Line 38: | Line 38: | ||
|Cannot Set Second Task to "Complete" After Enabling Request Class Option "Close Request When Tasks Complete" | |Cannot Set Second Task to "Complete" After Enabling Request Class Option "Close Request When Tasks Complete" | ||
|There is an option in the Properties for a Request Class, ''Close Request When Tasks Complete'', that is intended to close a Request once all Tasks have been marked as complete. This bug prevented the second Task from being marked as Complete, causing a broken page. | |There is an option in the Properties for a Request Class, ''Close Request When Tasks Complete'', that is intended to close a Request once all Tasks have been marked as complete. This bug prevented the second Task from being marked as Complete, causing a broken page. | ||
| + | |-style="vertical-align:top;" | ||
| + | |347 | ||
| + | |''admin.sys_admin_value'' Column Length too Short, Causing PDF Reports Not to Be Saved | ||
| + | |The length of a column in the ''admin'' table was too short, truncating the path used in saving a PDF, thus it wasn't being saved. | ||
| + | |-style="vertical-align:top;" | ||
| + | |349 | ||
| + | |Custom Report Not Returning Analyst Details | ||
| + | |Adding ''user.sys_forename'', ''user_surname'' and user-defined fields to a custom report did not return any data for those columns. | ||
| + | |-style="vertical-align:top;" | ||
| + | |354 | ||
| + | |Setting to Disable Analyst Groups is Broken | ||
| + | |Disabling an Analyst Group in Manage Analyst Groups did not prevent it from appearing in Analyst Group selection dialogs. | ||
| + | |-style="vertical-align:top;" | ||
| + | |362 | ||
| + | |Where Companies Have the Same Site Name, End User Site Changes to First Company/Site Combination | ||
| + | |If both ''Company A'' and ''Company B'' have a Site called ''Site'', and the End User is assigned to ''Company B/Site'', ''Company A/Site'' will be written to the End User record instead. | ||
| + | |-style="vertical-align:top;" | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | |-style="vertical-align:top;" | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | |-style="vertical-align:top;" | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | |-style="vertical-align:top;" | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | |-style="vertical-align:top;" | ||
| + | | | ||
| + | | | ||
| + | | | ||
|} | |} | ||
[[Category:Update Notes]] | [[Category:Update Notes]] | ||
Revision as of 04:33, 21 April 2015
Upgrading
ServiceDesk v6.5.7 is a minor release of the product. The upgrade may be applied to any version of 6.2.0 or later.
Please log in to the client support portal to download the upgrade installer. To install the upgrade, first extract all files from the archive, back up your database, stop the IIS Admin service, stop the LaytonServiceDesk service, and finally, run the upgrade installer lsd657_upgrade.exe. We recommend that you right-click the installer and select Run as administrator to avoid permission issues.
New Features
Bug Fixes
| # | Title | Description |
|---|---|---|
| 300 | Broken Incoming Mail Icon | When the number of incoming emails in the queue exceeded 50, the icon was broken. Now it will display a 50+ badge  to indicate more than 50 emails are in the queue.
|
| 302 | Priority Menu Not Sorted Correctly | List of Priorities was being sorted by description, not title. |
| 338 | Change Approvers Do Not Appear in the Change History | When adding a CAB member or CAB group to a Change, this did not appear in the history. |
| 342 | Column (No Company) in Report | In the Request Statistics by Company report, a number of Requests appeared against the Company (No Company), despite the associated End Users having an assigned Company. |
| 343 | Clicking Group Queue Yields No Results | If a Group name had an ampersand & in the name, clicking the number of Unassigned Requests on the Group Queues page would give an empty list. The problem was because of the ampersand. |
| 344 | Cannot Set Second Task to "Complete" After Enabling Request Class Option "Close Request When Tasks Complete" | There is an option in the Properties for a Request Class, Close Request When Tasks Complete, that is intended to close a Request once all Tasks have been marked as complete. This bug prevented the second Task from being marked as Complete, causing a broken page. |
| 347 | admin.sys_admin_value Column Length too Short, Causing PDF Reports Not to Be Saved | The length of a column in the admin table was too short, truncating the path used in saving a PDF, thus it wasn't being saved. |
| 349 | Custom Report Not Returning Analyst Details | Adding user.sys_forename, user_surname and user-defined fields to a custom report did not return any data for those columns. |
| 354 | Setting to Disable Analyst Groups is Broken | Disabling an Analyst Group in Manage Analyst Groups did not prevent it from appearing in Analyst Group selection dialogs. |
| 362 | Where Companies Have the Same Site Name, End User Site Changes to First Company/Site Combination | If both Company A and Company B have a Site called Site, and the End User is assigned to Company B/Site, Company A/Site will be written to the End User record instead. |
