AgileApps Support Wiki Pre Release

Difference between revisions of "Version 10.5 Platform"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 17: Line 17:
=== Next Release ===
=== Next Release ===
<blockquote>
<blockquote>
==== Sorting a View on Multi Object Lookup Fields ====
==== Sorting a View on a Multi-Object Lookup Field ====
:A multi-object Lookup field like the <tt>related_to</tt> 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 (for example, Cases) and sort Tasks by the Cases they relate to. (In the unlikely that a record targets a different object, that record is ignored.)  
:A multi-object Lookup field like the <tt>related_to</tt> 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 (for example, Cases) and sort Tasks by the Cases they relate to. (In the unlikely that a record targets a different object, that record is ignored.)  
:''Learn more: [[Feature]]
:''Learn more: [[Feature]]

Revision as of 01:02, 28 April 2015

See also:

Next Release

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 (for example, Cases) and sort Tasks by the Cases they relate to. (In the unlikely that a record targets a different object, that record is ignored.)
Learn more: Feature

Bug Fixes

LJP-57 Invalid subprocess-links in a process, when installed from a package
LJP-59 Validation when field removed from a form is used in a layout rule
LJP-82 Reinstalling a package with change to a field's type didn't reset the read-only property
LJP-89 Correct sorting issue in Tasks view
LJP-98 New dashboard was not visible to all
LJP-102 Custom Access Criteria for list view was not applied in combination with other expressions
LJP-103 Getting current action in a Form Script. (Syntax: Forms#Trigger on a Specific Action)
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-126 Layout rules could not be used to disable Radio buttons
LJP-150 Localization-capability needed for "Leave page/Stay on page" buttons in save-work warning dialog
LJP-154 Fix for formula editor