Difference between revisions of "Version 10.5 Platform"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
Line 22: | Line 22: | ||
:* LJP-154 - Fix for formula editor | :* LJP-154 - Fix for formula editor | ||
:* LJP-162 - Fix a message containing a special character in French | :* LJP-162 - Fix a message containing a special character in French | ||
:* LJP-180 - | :* LJP-180 - Confirm logout request when there are unsaved changes | ||
:* LJP-182 - | :* LJP-182 - Reduce length of translation text for assign-owner buttons | ||
:* LJP-183 - | :* LJP-183 - Issue resulting from large number of teams | ||
:* LJP-187 - | :* LJP-187 - | ||
:* LJP-190 - | :* LJP-190 - |
Revision as of 18:29, 26 May 2015
See also:
- Version 10.4 Platform (previous release)
- All Release Notes
- Upcoming Releases
Next Release
Bug Fixes
- LJP-105 - Allow access profile to specify read-only access on reports
- LJP-150 - Localized labels for save-dialog
- LJP-154 - Fix for formula editor
- LJP-162 - Fix a message containing a special character in French
- LJP-180 - Confirm logout request when there are unsaved changes
- LJP-182 - Reduce length of translation text for assign-owner buttons
- LJP-183 - Issue resulting from large number of teams
- LJP-187 -
- LJP-190 -
- LJP-195 -
- LJP-197 -
- LJP-200 -
- LJP-203 -
- LJP-208 -
- LJP-210 -
- LJP-229 -
Documentation Enhancements
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