Difference between revisions of "Version 10.6 Platform"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 29: Line 29:
: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.
: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]]
:''Learn more:'' [[Event Rules]]
==== JavaScript Functions to Hide Action-Menu Items and Assignment Buttons ====
:
:''Learn more:'' [[JavaScript Functions#Hiding Action Items and Assignment Buttons]]


==== Bug Fixes ====
==== Bug Fixes ====

Revision as of 20:04, 13 October 2015

See also:

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

JavaScript Functions to Hide Action-Menu Items and Assignment Buttons

Learn more: JavaScript Functions#Hiding Action Items and Assignment Buttons

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 Improve contrast ratios in UI
  • LJP-471 Maintain readability when browser font size is increased
  • 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 Navigation-confirmation dialog was appearing at inappropriate times
  • LJP-621 Sidebar was not refreshing properly when navigating via JavaScript
  • 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 Dashboard widget had the wrong link to report document
  • LJP-634 Picklist field was not showing the cursor focus
  • LJP-645 Tab-redirection was not working properly for a button added to a Form
  • LJP-666 A disabled checkbox was still editable