Version 10.5 Platform

See also: Version 10.4 Platform (previous release) All Release Notes Upcoming Releases

Next Release (15 Sep 2015)

Feature

descr

Learn more: Feature

August Release (15 Aug 2015)

Display User's Current Role

When the user has multiple roles, and the Switch User Roles feature is enabled (which means users can adopt only one role at a time), the currently-selected role is displayed in the page header, next to the user's name.

(LJP-379)

Email Addresses and URLs are Always Active

When a form was displayed in edit mode, email addresses and URLs were displayed as editable fields, and were not clickable. They now display as clickable fields, with an added "pencil" icon that can be clicked to edit their contents.

(LJP-31)

Usability Enhancements

• LJP-316: Form-details section no longer closes automatically after the user clicks "Save".
• LJP-377: Error messages display more consistently
• LJP-378: When a required field is empty, or a field value is wrong, the field in question is now highlighted with a red border on the form.
• LJP-361: Read-only fields now display consistently.
• LJP-404: Published packages give better instructions for publishers to provide to installers
• LJP-413: Display task name in the sidebar completion-dialog

Bug Fixes

• LJP-302: Platform was not properly parsing Java code error messages that ended with '\n', so the message was not delivered.
• LJP-315: A view with no name was created when the last standard view was removed.
• LJP-324: Users without the proper privileges were allowed to delete report folders.
• LJP-344: Platform threw an error when changing ownership on more than 5 child records.
• LJP-389: Tasks were editable, even though the tasks-tab was disabled.
• LJP-396: Clicking next to a checkbox caused it to be selected without displaying the checkmark to the user.
• LJP-399: Display submitter's photo ID in activity history
• LJP-431: Widget incorrectly renamed when report it is based on is moved/renamed.
• LJP-446: Rich-text fields marked as Required are no longer satisfied if they contain only whitespace
• LJP-476: Default value was not displayed for read-only Lookup field in an add-record Form
• LJP-479: Details-area of a Case form are no longer shown to portal users

Documentation Enhancements

• Customizing ServiceDesk Operations - Easy customizations to take control of default ServiceDesk behavior.
• HowTo:Create Application-Specific Help

July Release (15 July 2015)

Session Management

Session limits can be specified, to limit the number of concurrent sessions a user is allowed to have.

Learn more: Session Management

Task Assignment Notifications Controlled by Rules

When a task is created or re-assigned to someone else, an email notification is sent to the new task owner, by default. In new customer accounts, the behavior in each situation is now under the control of an Event Rule defined on the Tasks object, allowing notifications to be turned off or conditionalized so they are sent out only specified circumstances.

Learn more: Controlling Task-Assignment Notifications

Packaging Enhancements

• LJP-273 - Application reports that are visible to everyone and those that are visible to application roles are automatically added to a package as part of an application.
• When the "Overwrite Previous Package" option is enabled:

• LJP-326 - Email Templates, Quick Text definitions, and Web Forms defined on an object are now overwritten when the package is installed.
• LJP-220 - Processes deleted from the publisher's system are now deleted from the installer's system.
• LJP-278 - Translation Workbench entries deleted from the publisher's system are now deleted from the installer's system

Learn more: Package Items#Object Aspects

Other Product Enhancements

• LJP-317 - Improve the error message for a required field
• LJP-319 - Expand the clickable area of radioboxes and checkboxes to include the field label
• LJP-251 - Record more login-header information in the log to help troubleshoot certificate-based authentication

Bug Fixes

• LJP-194 - Error message pop-up was appearing behind the form
• LJP-197 - Alphabetical filtering opens for German language
• LJP-199 - Validations that depended on a Lookup field were failing unexpectedly
• LJP-229 - In accessibility mode, some field-help icons were misaligned and invisible
• LJP-241 - Change password feature was failing in some circumstances
• LJP-245 - Date-field validations were not triggered after using the date/time chooser
• LJP-246 - Guest user was unable to create a case
• LJP-252 - Unable to change the name of Parent Team when there are a large number of subteams
• LJP-253 - For Lookup autocomplete, use the user's selected format for date, date-time, time, and numeric/currency fields
• LJP-256 - Problems with the display of required fields and Lookups after installing a path for an on-premise installation
• LJP-259 - Display problem when translated button label was longer than the original button
• LJP-279 - Users logged into a local (non-cloud) platform were being randomly logged out
• LJP-280 - Field-help icons were misaligned and not reachable
• LJP-282 - Display the list of searchable objects in alphabetical order
• LJP-283 - Java search-records API was returning text-translation keys ("tokens") instead of translated text
• LJP-292 - Correct an error in the display of a form sections controlled by a Layout rule
• LJP-293 - COUNT function now operates correctly with a hardcoded string
• LJP-300 - Relationship aliases created by the Wizard were at times given duplicate names
• LJP-301 - Corrected for location of field hint icons
• LJP-303 - Deleted attachment was reappearing after clicking the [Cancel] button
• LJP-313 - Rich text areas were not appearing after selecting "Add New Record" from a Lookup window
• LJP-321 - Disable the new-record button when the user does not have privileges required to create a record.
• LJP-322 - Do no not change cursor shape when hovering over a disabled field
• LJP-323 - Change search box appearance to indicate that it is active
• LJP-333 - Records repeating in a long List view (duplicate of LJP-289)
• LJP-334 - A case that was created and then deleted continued to appear in the cases menu
• LJP-341 - Fields whose values are copied from a Lookup target-record no longer need to be present in the Form.
• LJP-358 - Layout rule applied to priority field now applies to the banner, as well as the field
• LJP-369 - The "Case" label that appears as a column header in Cases views now uses the singular object label.

(That column does not display a field. Rather, it displays a color-coded graphic that combines the case number and case priority. The column header was hard-coded to say "Case", and wasn't changing when the object name was changed--for example, to "Incidents", or "Investigations". Other columns display fields. Those column headings can be modified by changing field labels.)

Documentation Enhancements

• Validations#Complex Validation and Data Formatting - Tips for using JavaScript and Rules
• Application Branding#Change the Name of Predefined Objects

May Release (30 May 2015)

Bug Fixes

• LJP-122 - Scrolling fails when zoom is activated in Chrome or Firefox
• LJP-180 - Prompt to save changes when logging out
• LJP-182 - Reduce length of translation text for assign-owner buttons
• LJP-183 - Fix issue resulting from large number of teams
• LJP-187 - Properly display a reset-field when the field is protected
• LJP-190 - Error message showing up incorrectly for a required file field when value is present
• LJP-195 - Use a business rule to stop a running process
• LJP-197 - Make alphabetical filtering visible on first page of a Lookup dialog
• LJP-200 - Prompt to save changes when clicking Complete/Approve/Reject buttons
• LJP-203 - Proper enforcement of access-profile permissions when creating dashboard widgets
• LJP-208 - Fix Web Forms to work with https links
• LJP-210 - Properly apply "recalculate formula field value" option to existing records in a new formula field
• LJP-223 - Callable process not referenced correctly after package is deployed
• LJP-229 - Show field hints for fields that are made required by a layout rule in accessibility mode
• LJP-234 - Translations needed for text in session-timeout dialog
• LJP-247 - Lookup icon should not appear when Lookup field is disabled

Documentation Enhancements

• Static Resources#Accessing a JavaScript Resource from an Object Form
• Form Scripts#Add a Help Button to an Arbitrary Form
• Application Help Tab

April Release (2 May 2015)

Sorting a View on a Multi-Object Lookup Field

A multi-object Lookup field like the related_to field in a Task record has the capacity to target multiple objects. In the past, it has not been possible to use such fields for sorting. However, objects like Tasks typically point to only one kind of record (Cases). When creating a view, therefore, it is now possible to select the target record (Cases), causing the view to be sorted Tasks by the Cases they relate to. (In the unlikely that a record targets a different object, that record is not included in the view.)

Learn more: List Views#Customizing a List View

Change to Callable Processes

• The [New Callable Process] button lets you specify that the process will be a callable subprocess when you start creating it. That button replaces the checkbox that appeared only when you were saving the process you defined.
• When creating a callable process, there is no longer an option to add a step that executes another (second-level) callable process.

Learn more: Processes#Creating a Callable Process

Bug Fixes

LJP-68	Confirmation button missing when two consecutive process steps need the same role
LJP-74	Rollup Summaries are of wrong type, currencies are rounded
LJP-89	Correct sorting issue in Tasks view
LJP-102	Custom Access Criteria for list view was not applied in combination with other expressions
LJP-105	A dashboard icon to get to report was not appearing unless editing was allowed
LJP-109	Incorrect error message shown for a required field when using mobile access
LJP-121	Report presentation in dashboard did not match the actual report
LJP-150	Localization-capability needed for "Leave page/Stay on page" buttons in save-work warning dialog
LJP-154	Fix for form editor
LJP-162	Error message due to French translation with a special character
LJP-173	Error message when selecting a record from a lookup field