Difference between revisions of "Version 10.0 Platform"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
:''See also:'' [[All Release Notes]] | :''See also:'' [[All Release Notes]] | ||
__TOC__ | __TOC__ | ||
==13 Jan 2014== | ==13 Jan 2014== | ||
<blockquote> | <blockquote> | ||
| Line 15: | Line 14: | ||
==== Loop Variables Easier to Use in Print Templates ==== | ==== Loop Variables Easier to Use in Print Templates ==== | ||
:When defining a Print template, related records (records that have a [[Lookup]] to the current record) need to be processed in a loop, because multiple records in the related object could be pointing to the current record. Such variables are easier to spot, because related objects are listed at the end of the Template Variables category list, under the heading "Related". And they're easier to use, because they include the entire loop syntax. The entire line of code can then be pasted into the template or, if a loop is already in place, you can paste only the part that is needed. | :When defining a Print template, related records (records that have a [[Lookup]] to the current record) need to be processed in a loop, because multiple records in the related object could be pointing to the current record. Such variables are easier to spot, because related objects are listed at the end of the Template Variables category list, under the heading "Related". And they're easier to use, because they include the entire loop syntax. The entire line of code can then be pasted into the template or, if a loop is already in place, you can paste only the part that is needed. | ||
:''Learn more:'' [[Print Templates | :''Learn more:'' [[Print Templates#Processing Related Records in HTML]] | ||
==== Auto Copy Scheduled Reports to Managers ==== | ==== Auto Copy Scheduled Reports to Managers ==== | ||
| Line 23: | Line 22: | ||
==== Dates and Times Exported in User Format ==== | ==== Dates and Times Exported in User Format ==== | ||
:The user's date format and time zone are used when exporting date/time data, allowing backup data exported by a user to be re-imported by the same user, without requiring a data conversion. | :The user's date format and time zone are used when exporting date/time data, allowing backup data exported by a user to be re-imported by the same user, without requiring a data conversion. | ||
:''Learn more:'' [[Export Data]] | :''Learn more:'' [[Export Data#Data Formats]] | ||
====Include Web Forms in an Application Package==== | ====Include Web Forms in an Application Package==== | ||
| Line 31: | Line 30: | ||
:The icon and description that appear in the catalog can be specified when the package is published. | :The icon and description that appear in the catalog can be specified when the package is published. | ||
:''Learn more:'' [[Packages#Publish a Package]] | :''Learn more:'' [[Packages#Publish a Package]] | ||
====REST API Enhancements==== | |||
:* When uploading a file using the REST API, the <tt>isBase64Encoded</tt>query parameter can be used to specify that the file contains encoded binary data. | |||
::''Learn more:'' [[REST API:record Resource#Multipart Operations for Raw Data]] | |||
:* Use the <tt>appId</tt> query parameter to restrict a list of returned objects to those that are part of a specific application. | |||
::''Learn more:'' [[REST API:object Resource##Retrieve all Objects]] | |||
:* When returning data for an enumerated field, the [[REST API:record Resource]] returns the field label in addition to the field value, using the XML attribute, <tt>displayValue</tt>. | |||
</blockquote> | </blockquote> | ||
<noinclude> | <noinclude> | ||
Latest revision as of 19:38, 28 March 2014
Release Notes for the Version 10.0 Platform.
- See also: All Release Notes
13 Jan 2014
Specify Plural and Singular Object Labels
- When defining an object (for example, when creating an application), both singular and plural labels can be specified. (Previously, labels could be modified only after the object was created.)
- Learn more: Application Construction Wizard, Object Construction Wizard
More Intuitive Names for Lookup Fields
- When defining an object relationship, the generated field name is now the singular version of the object name. When displayed in a Form, the field is more readily recognized by users.
- For example, when a Lookup field targets the Customers object, the default name is customer. (Previously, the default field label was related_to_customers.)
Loop Variables Easier to Use in Print Templates
- When defining a Print template, related records (records that have a Lookup to the current record) need to be processed in a loop, because multiple records in the related object could be pointing to the current record. Such variables are easier to spot, because related objects are listed at the end of the Template Variables category list, under the heading "Related". And they're easier to use, because they include the entire loop syntax. The entire line of code can then be pasted into the template or, if a loop is already in place, you can paste only the part that is needed.
- Learn more: Print Templates#Processing Related Records in HTML
Auto Copy Scheduled Reports to Managers
- Automatically deliver copies of scheduled reports to each recipient's manager, or to both their immediate management and second-level management.
- Learn more: Scheduled Reports
Dates and Times Exported in User Format
- The user's date format and time zone are used when exporting date/time data, allowing backup data exported by a user to be re-imported by the same user, without requiring a data conversion.
- Learn more: Export Data#Data Formats
Include Web Forms in an Application Package
Specify Catalog Description and Icon when Publishing a Package
- The icon and description that appear in the catalog can be specified when the package is published.
- Learn more: Packages#Publish a Package
REST API Enhancements
- When uploading a file using the REST API, the isBase64Encodedquery parameter can be used to specify that the file contains encoded binary data.
- Use the appId query parameter to restrict a list of returned objects to those that are part of a specific application.
- Learn more: REST API:object Resource##Retrieve all Objects
- When returning data for an enumerated field, the REST API:record Resource returns the field label in addition to the field value, using the XML attribute, displayValue.