Version 10.5 Platform

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

Next Release (15 July 2015)

Task Assignment Notifications Controlled by Rules

When a task is created or re-assigned to someone else, an email notification is sent out to the new task owner, by default. That behavior is now under the control of Event Rules 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 Notifications

Bug Fixes

• 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.
• LJP-326 - When the "Overwrite Previous Package" option is enabled, Email Templates, Quick Text definitions, and Web Forms defined on an object are now overwritten when the package is installed.
• WF-5199 - 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 therefore 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