Difference between revisions of "Version 9.0 Upgrades and Enhancements"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
| (22 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
< | <noinclude> | ||
:{| border="1" align="right" cellpadding="5" cellspacing="1" | :{| border="1" align="right" cellpadding="5" cellspacing="1" | ||
| | | | ||
| Line 8: | Line 8: | ||
|} | |} | ||
__NUMBEREDHEADINGS__ | __NUMBEREDHEADINGS__ | ||
==Enhancements in Version 9.0.18== | |||
== For Users and Designers == | === For Users and Designers === | ||
<blockquote> | <blockquote> | ||
==== Multi-Value Line Charts ==== | ==== Multi-Value Line Charts ==== | ||
| Line 18: | Line 18: | ||
==== Zero Values Supplied for Reports Grouped by Month or Month in Year ==== | ==== Zero Values Supplied for Reports Grouped by Month or Month in Year ==== | ||
:When a report groups data either by month (or by month in year), a zero value is now supplied for any month that has no data. This change keeps report formatting consistent, making them easier to read. | :When a report groups data either by month (or by month in year), a zero value is now supplied for any month that has no data. This change keeps report formatting consistent, making them easier to read. | ||
:''Learn more:'' [[Report Group#Date Groupings|Date Groupings]] | :''Learn more:'' [[Report Group#Date Groupings|Date Groupings]] in [[Report Group]]s | ||
==== Blind Copies Supported in Scheduled Reports ==== | |||
:When scheduling a report, it is now possible to specify Bcc addresses. | |||
:''Learn more:'' [[Reports#Schedule a Report|Schedule a Report]] | |||
</blockquote> | </blockquote> | ||
== For Designers == | === For Designers === | ||
<blockquote> | <blockquote> | ||
==== Workflow | ====Labels (titles) Available for Workflow Template Variables ==== | ||
: | :In the past, workflow template variables for the current state, previous state, action taken, and available actions in current state always contained internal ''names''. An additional set of variables now makes available the ''labels'' attached to those values, as well. | ||
:The new variables are: | |||
::*<tt>$workflow.current_state_title</tt> | |||
::*<tt>$workflow.previous_state_title</tt> | |||
::*<tt>$workflow.action_title_taken</tt> | |||
::*<tt>$workflow.available_action_titles_for_current_state</tt> | |||
:''Learn more:'' [[Template Variables in Workflows]] | |||
==== Captchas Supported in Web Forms ==== | ==== Captchas Supported in Web Forms ==== | ||
| Line 32: | Line 44: | ||
==== Enhancement to Pass Thru Authentication ==== | ==== Enhancement to Pass Thru Authentication ==== | ||
:When | :When implementing Pass Thru Authentication (PTA), it is now possible to use a form to send identification parameters to the platform. (Previously, it was necessary to pass a SOAP message and perform a conditional branch based on the results.) This enhancement simplifies the client side implementation of PTA, which is now simply a matter of hosting a form. | ||
:''Learn more:'' [[Pass Through Authentication#Message Formats|Pass_Through Authentication Message Formats]] | |||
</blockquote> | </blockquote> | ||
== For Admins == | === For Admins === | ||
<blockquote> | <blockquote> | ||
==== User and Role Management Separated in Access Profiles ==== | ==== User and Role Management Separated in Access Profiles ==== | ||
:The old "Access Control/User Management" permission has been divided into two different permissions, to allow for more fine-grained control of administrative privileges. One permission (User Management | :The old "Access Control/User Management" permission has been divided into two different permissions, to allow for more fine-grained control of administrative privileges. One permission (User Management) allows an admin or manager to create users and teams. The other (Access Control) is used by an application designer or "super admin" to create the roles used in the application. | ||
:''Learn more:'' [[Access_Profiles#Administrative_Permissions|Administrative Permissions]] in Access Profiles | |||
: | |||
</blockquote> | </blockquote> | ||
== Deprecated Functionality == | === Deprecated Functionality === | ||
<blockquote> | <blockquote> | ||
=== Removal of On View and On List View Data Policies === | === Removal of On View and On List View Data Policies === | ||
| Line 85: | Line 62: | ||
:To improve overall system responsiveness, therefore, the On (record) View and On List View triggers for data policies have been retired. | :To improve overall system responsiveness, therefore, the On (record) View and On List View triggers for data policies have been retired. | ||
:The change does not affect legacy applications. In addition, the capability can be enabled on a case by case basis, when exceptional circumstances | :The change does not affect legacy applications. In addition, the capability can be enabled on a case by case basis, when warranted by exceptional circumstances. | ||
</blockquote> | </blockquote> | ||
<noinclude> | <noinclude> | ||
[[Category:Release Notes]] | [[Category:Platform Release Notes]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 23:20, 9 January 2014
See also:
- Version 9.0 Platform Release Notes
- Release Notes for all versions
- Doc Notes for documentation changes
1 Enhancements in Version 9.0.18
1.1 For Users and Designers
1.1.1 Multi-Value Line Charts
- Multiple sets of values can now be displayed in a single graph, making it easier to do comparisons and see trends at a glance.
- Learn more: MultiLine Charts
1.1.2 Zero Values Supplied for Reports Grouped by Month or Month in Year
- When a report groups data either by month (or by month in year), a zero value is now supplied for any month that has no data. This change keeps report formatting consistent, making them easier to read.
- Learn more: Date Groupings in Report Groups
1.1.3 Blind Copies Supported in Scheduled Reports
- When scheduling a report, it is now possible to specify Bcc addresses.
- Learn more: Schedule a Report
1.2 For Designers
1.2.1 Labels (titles) Available for Workflow Template Variables
- In the past, workflow template variables for the current state, previous state, action taken, and available actions in current state always contained internal names. An additional set of variables now makes available the labels attached to those values, as well.
- The new variables are:
- $workflow.current_state_title
- $workflow.previous_state_title
- $workflow.action_title_taken
- $workflow.available_action_titles_for_current_state
- Learn more: Template Variables in Workflows
1.2.2 Captchas Supported in Web Forms
- A Captcha displays an image and asks the user to type the text it contains. (Providing the correct text shows that a person is filling out the form, rather than an automated "robot".) Captchas can now be included in a Web Form simply by putting a mark in a checkbox.
- Learn more: Web Form Settings
1.2.3 Enhancement to Pass Thru Authentication
- When implementing Pass Thru Authentication (PTA), it is now possible to use a form to send identification parameters to the platform. (Previously, it was necessary to pass a SOAP message and perform a conditional branch based on the results.) This enhancement simplifies the client side implementation of PTA, which is now simply a matter of hosting a form.
- Learn more: Pass_Through Authentication Message Formats
1.3 For Admins
1.3.1 User and Role Management Separated in Access Profiles
- The old "Access Control/User Management" permission has been divided into two different permissions, to allow for more fine-grained control of administrative privileges. One permission (User Management) allows an admin or manager to create users and teams. The other (Access Control) is used by an application designer or "super admin" to create the roles used in the application.
- Learn more: Administrative Permissions in Access Profiles
1.4 Deprecated Functionality
1.5 Removal of On View and On List View Data Policies
- In general, Data Policies that are triggered by On View and On List View are an exercise in redundancy. They generally add system overhead (a great deal of overhead), without adding any real value. For example, if a field is calculated, the calculation need only occur when the record is created or updated. If it is invoked every time a record is displayed, the system works overtime to re-calculate values that have already been stored.
- To improve overall system responsiveness, therefore, the On (record) View and On List View triggers for data policies have been retired.
- The change does not affect legacy applications. In addition, the capability can be enabled on a case by case basis, when warranted by exceptional circumstances.