Version 8.2 Platform Release Notes

See also: Version 8.2 Doc Notes Release Notes for all versions Version 8.2 Installable Version Release Notes

1 For Users and Designers

1.1 Major Enhancements

1.1.1 SQL Queries in the UI

The new SQL Browser lets you make safe, permissions-restricted SQL language queries against the data in the database.

Learn more:

• SQL Browser
• SQL Syntax
• SQL Functions

1.1.2 Direct Data Access using Short URLs

In version 8.2, documents, records, reports, views, applications, and dashboards can all be accessed with convenient, short URLs. Clicking the tilted "figure-8" icon on a page brings up dialog that gives you a URL you can copy. You can put that URL into an email, a web page, or a bookmark. Any authorized user who follows the link goes directly to the targeted page in the platform.

Learn more: Short URL

1.1.3 Include Images and Charts in Generated PDFs

HTML Print Templates (which produce PDFs) can include images stored in an object record, as well as charts.

Learn more: Insert Images and Charts into a Print Template

1.1.4 Vote on Your Favorite Feeds

Relay now lets you click a button to record the fact that you like a particular posting.

1.1.5 Private Relay Groups, as well as public

Now, a Relay group can optionally be private (visible only to its members), as well as public (visible to all, by default).

Learn more: Relay Groups

1.1.6 Form Layout Enhancements

Forms can now have from one to 4 columns.

Learn more: Edit a Section in a Form

1.1.7 More Control Over Labels and Data in Forms

• Label position above field, as well as to left
• Ability to specify custom CSS for field labels and field values

Learn more: Common Field Display Characteristics

1.1.8 Layouts for Web Forms

Web Forms allow users to send data to the platform from your own website. The process for creating such forms has been redesigned to make it smoother and more intuitive. In addition, it is now possible to design a customized Form in the platform, and use it in your website. (Previously, custom Forms could run only in the platform.)

As part of those changes the "script" web form has been retired. For backward compatibility, existing forms can still be either of type "Script" or "HTML", but new web forms are always of type "Form Layout" or "Generated HTML". (In a "Script" form, a link is provided that references JavaScript code hosted on the platform. In a "Generated HTML" form, the HTML for the form is created. You then copy that code into your page, and edit it as needed.)

1.1.9 Add Active Links to Relay Posts

When you generate a Relay post from a Data Policy, you can add one or more active links that go to a custom JSP page.

Learn more: Adding an Active Link to a Relay post

1.1.10 Support for thumbnails in image fields

When uploading an image to a record, it is also possible to specify a thumbnail for the image. When displaying the record, the thumbnail is then displayed, to save screen space.

Learn more: Image Fields

1.1.11 Use Formulas & Data Policies to Update Fields in Cascaded Lookup-Target Records

Fields in lookup-target records (referential fields) can now be updated by formulas and by data policy actions.

Learn more:

• How the Formula Builder Works
• Data Policy Actions
• Updating a Field in a Related Record during a Data Policy "Update Record" Action

1.1.12 Create New Records in a Data Policy Action

You have always had the ability to update records in a Data Policy action. Now you have the ability to add new records to an object, as well.

Learn more: About Data Policy Actions

1.2 Significant Changes

1.2.1 "Grid Sections" are now "Subforms

Subsections of a Form that allow a user to enter and display Related Record information used to be called "Grid Sections". Those sections are now called Subforms, to be more in line with industry-standard usage.

1.2.2 Logged-In User when Specifying Lookups

The record selection criteria you specify for a Lookup field determines the records the user will be able to choose from. Template variables that specify characteristics of the logged-in user are now available when specifying those criteria, making it possible to limit the record choices in ways that are relevant to that user (for example, who the user reports to, or what timezone the user is in).
Learn more: User-specific template variables in Dynamic Lookup Filters

1.2.3 Lists of Objects and Reports Restricted to Current Application

When making a selection from a list of objects or reports, users will now find that instead of listing every object or report for every application the organization has, the list will contain only the objects and reports they are likely interested in--those that are part of the current application.

1.2.4 Lookup-based Auto-Copy Fields

When you add a Lookup field to an object, it is now possible to automatically copy values from the target record to fields in the current record--prefilling them with data from the Lookup target. Those values can then be changed by the user, if needed, without affecting the original record.

Learn more: Lookup-Based Auto-Copy of Field Data

1.2.5 More Options for Charts

• Default labels are larger and darker, so they can be read more easily.
• You can change the font size and style of the labels in Bar, Line, and Area charts.
• A minimum value can now be specified for the Y-axis.

Learn more: Advanced Options for Charts

1.2.6 New Interface for Enumerated Values

In earlier versions of the platform, items in a list of values for Enumerated Fields were specified individually, one by one. There is now a spreadsheet-style ("grid section") interface that lets you specify all of the values at one time for fields like pick lists, radio buttons, and checkboxes.

Learn more: Setting Colors and Images for Enumeration Values

1.2.7 Default Values for Enumerated Fields and Lookups

Default values can be specified for enumerated fields (pick lists, global pick lists, multi-select pick lists, radio buttons, and checkboxes), as well as for lookups and multi-object lookups.

Learn more:

• Specifying a Default Value for an Enumerated Field
• Create a Lookup Field
• Default Value for a Multi Object Lookup Field

(As part of this change, the ability to specify defaults of Checked or Unchecked for multiple checkboxes has been removed.)

1.2.8 "As Entered" Option for Date/Time Values

Date/Time fields and formulas that return a Date/Time can be displayed "as entered", instead of being automatically converted to the system time zone when entered, and automatically converted to the user's time zone, when displayed.
Learn more: Field Display Types

1.2.9 Filter Expressions can Use Values Stored in Record Fields

When specifying Filter Expressions, the expression has always taken the form 'someField = someValue' (where one of multiple comparison operators can take the place of the equals sign). In this release, it is possible to specify a field value from the current record, using the syntax: 'someField =' + currentRecordFieldName

1.2.10 Better Selection Options for Workflow Task Owners (Decision Makers)

Choices of Task Owners for a record in a workflow (previously known as "decision makers"), have been enhanced:

• When the user is supposed to make a selection at run time, the list of users they need to choose from can now be restricted to a particular team, instead of automatically listing every user in the organization.
• For any field that is a Lookup to the User object, the title of that field becomes one of the designer's options for workflow owner. (For example, if a record has a User-lookup field called "Reviewer", then the state lists "Reviewer" as a possible Task Owner.)

Learn more: Task Owners in a Workflow

1.2.11 Automatically Assign Previous Task Owner for a Specific Action

A Workflow action can now specify "previous decision maker" or their manager as the new Task Owner. For example, if developer sends a "ready for testing" request to Q/A, then a "More Information Needed" action can automatically assign the developer who sent the request as the new Task Owner.

Learn more: Edit an Action

1.2.12 Assign Workflow Task Owners Programatically

By creating a class that implements the appropriate interface, developers can programatically designate one or more users as task owners for a record in a workflow.

Learn more:

• Workflow Task Ownership Class
• Assigning Task Owners in a Workflow

1.2.13 Set Start and End Dates for a Workflow

Have a special deal for the month of December? You can define a Workflow that is in operation only in that month. During that time period, actions defined in that workflow are available as buttons when viewing a record, along with action-buttons for any other workflows that are active.

Learn more: Workflow Start and End Dates

1.2.14 Clone a Workflow and Set a Cutover Date

It is now possible to clone a Workflow, modify it, and give it a future start date, when it will become active. It is also possible to set an end date for the original workflow. Together, the two dates define a cutover point at which the old workflow is replaced by the new one.

Learn more: Clone a Workflow

1.2.15 Indexes Can Use the Record Identifier

When creating an index on a custom object, it is now possible to specify the record "name" as the index field (where the record "name" is the Record Identifier declared in the Record Locators). (For standard objects that have a name field, that field can be used.)

When a unique index is created on that field, the record name is used to construct the short URL for a record.

So in addition to specifying "http://.../record/Customer/12345", for example,

it becomes possible to specify "http://.../record/Customer/ABC Co".

Learn more: Direct Data Access using Short URLs (above)

1.2.16 Thumbnail Views Deprecated

Record views that consist entirely of picture thumbnails are no longer supported in Release 8.2. Existing views will continue to function, but it is no longer possible to create new ones.

1.2.17 Relay Can be Restricted to Team Hierarchy

By default, a user can see and follow all other users. But with this new option, the people a user can see and follow can be restricted to members of the teams the user belongs to (and subteams, or "child teams", of those teams).

Learn more: Relay Feed Settings

2 For Developers

2.1 Major Enhancements

2.1.1 Development Sandboxes

Set up development and testing processes by creating Sandboxes--tenant "subspaces" that are safely separated from the production environment--and by deploying Packages between them.

2.1.2 APIs for SQL Queries

• The new Java execSQL API lets you run SQL queries from your Java code.
• The new REST execSQL resource lets you run SQL queries over the web.

2.1.3 Relay APIs

External applications can now interact with the platform's social networking features using the Relay REST APIs. Internal applications can use the Java APIs.

2.1.4 Email Listener Interface

A new EmailHandler interface makes it possible to listen for messages, split them into their components, and use platform APIs to act on them.
Learn more: Email Handler APIs

2.2 Significant Changes

2.2.1 Role-based Reports can be Added to Packages

It is now possible to package reports in folders that are visible to specific roles, as well as reports in folders that are visible to all.

Learn more: Package Limitations

2.2.2 Overwrite Option is Available for Unlocked Packages

Previously, the overwrite option was only available for locked packages. As of version 8.2, it is available for unlocked packages, as well. (This option only works for packages that are installed in 8.2. When the package is re-published with the overwrite option, the next package install uses that option.)

Learn more: Publish a Package

2.2.3 New Base64Codec Class to Decode Email Attachments

Since email attachments are encoded in Base64, a function is needed to decode them. Developers can now instantiate the Base64Codec class to get that codec, and then call the encode or decode functions, as desired.

2.2.4 New Utility Class for Service Configuration

The new ServiceConfiguration class makes it possible to get the service URL and the provider name, as specified by the service provider in the Basic Service Configuration.

2.2.5 New Parameters available in Data Policies that Run Java Code

Several new parameters are available that make it possible to write more robust data policies that can be used in a variety of contexts.

Learn more: Accessing Other Parameters in a Data Policy