Difference between revisions of "Version 10.6 Platform"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 31: | Line 31: | ||
==== Bug Fixes ==== | ==== Bug Fixes ==== | ||
:* LJP-459 Information that was available only in background images was made available to the visually impaired | |||
:* LJP-466 Warn the user to save changes when a macro has made changes in a Form | |||
:* LJP-470 | |||
:* LJP-471 | |||
:* LJP-481 Calendar/Report Date Filter was using U.S. locale instead of user locale | :* LJP-481 Calendar/Report Date Filter was using U.S. locale instead of user locale | ||
:* LJP-529 Not possible to put an upper case "Q" in an email, in some browsers | :* LJP-529 Not possible to put an upper case "Q" in an email, in some browsers | ||
| Line 40: | Line 44: | ||
:* LJP-606 Active links in the print browser preview window were going to the old UI | :* LJP-606 Active links in the print browser preview window were going to the old UI | ||
:* LJP-614 Thousands-separator in some countries caused Charts to fail in a report | :* LJP-614 Thousands-separator in some countries caused Charts to fail in a report | ||
:* LJP-616 | |||
:* LJP-621 | |||
:* LJP-627 Lookup to a Child object was incorrectly opening to Parent object form | :* LJP-627 Lookup to a Child object was incorrectly opening to Parent object form | ||
:* LJP-629 Process was failing when creating a new request-record | :* LJP-629 Process was failing when creating a new request-record | ||
:* LJP-631 | |||
:* LJP-634 | |||
:* LJP-645 Tab-redirection was not working properly for a button added to a Form | :* LJP-645 Tab-redirection was not working properly for a button added to a Form | ||
:* LJP-666 | |||
</blockquote> | </blockquote> | ||
<!-- | <!-- | ||
Revision as of 22:33, 9 October 2015
See also:
- Version 10.5 Platform (previous release)
- All Release Notes
- Upcoming Releases
October Cloud Release (15 Oct 2015)
Record Level Visibility
- Visibility criteria can be specified on individual records, making the records visible only to a select audience. Visibility can be restricted to individuals, teams, roles, or to users who have a specified setting in a custom field. Multiple values can be specified for each record. Only users who match one of those values can see the record.
- Learn more: Record Level Visibility
Integration with MS Azure
- Microsoft Azure Active Directory can be used to supply user credentials, providing users with "single sign-on" capability.
- Learn more: SAML#SAML Settings for MS Azure
Trust Site
- How well is the AgileApps Cloud platform public cloud performing? Find out at the Trust Site! See uptime history, current status, and schedule of upcoming maintenance activities.
- Learn more: Trust Site
Email Events
- Incoming emails related to a Case can trigger email-event rules, allowing actions to be taken based on the content of the email fields, or simply on the presence of the message.
- Learn more: Event Rules
Bug Fixes
- LJP-459 Information that was available only in background images was made available to the visually impaired
- LJP-466 Warn the user to save changes when a macro has made changes in a Form
- LJP-470
- LJP-471
- LJP-481 Calendar/Report Date Filter was using U.S. locale instead of user locale
- LJP-529 Not possible to put an upper case "Q" in an email, in some browsers
- LJP-537 Layout Rules - Could not assign an empty string () to a Multiple Checkbox field
- LJP-548 Description was appearing before Report Name in a list of reports
- LJP-576 Lookup filter was working differently in a related information section, vs. a subform
- LJP-578 A field marked "Always Required" should required by default in a record Form
- LJP-592 Not possible to put capital Q in a record Note, as shift+Q quits the editor
- LJP-606 Active links in the print browser preview window were going to the old UI
- LJP-614 Thousands-separator in some countries caused Charts to fail in a report
- LJP-616
- LJP-621
- LJP-627 Lookup to a Child object was incorrectly opening to Parent object form
- LJP-629 Process was failing when creating a new request-record
- LJP-631
- LJP-634
- LJP-645 Tab-redirection was not working properly for a button added to a Form
- LJP-666