Summer '13 Force.com Platform Release
Increased Query Size Limit
The maximum size for a SOQL query has been increased to 20,000 characters.
Additional comparison operators supported for primary key fields
The less than (<), less or equal (<=), greater than (>) and greater or equal (>=) comparison operators are now supported on ID (primary key) fields. Previously, only equals (=), not equals (!=), IN, and NOT IN were supported on ID fields. As an example, the following query is now allowed:
SELECT Name from MyObject__c WHERE Id > '001000000000abc'
FOR VIEW and FOR REFERENCE SOQL Clauses
Update objects with information about when they were last viewed or referenced using the FOR VIEW and FOR REFERENCE clauses, respectively. A record is considered viewed when the user sees the details associated with it, but not when the user sees it in a list with other records. A record is considered referenced when a related record is viewed. You can use these clauses when objects are viewed in a custom interface, such as a mobile application or a custom page.
This is an example of a SOQL query that retrieves one contact to show to the current user and uses FOR VIEW to update the last viewed date of the retrieved contact. The same statement both retrieves the record and updates its last viewed date.
SELECT Name, ID FROM Contact FOR VIEW LIMIT 1
This is an example of a SOQL query that retrieves a contact and uses FOR REFERENCE to update the LastReferencedDate field of the retrieved contact.
SELECT Name, ID FROM Contact FOR REFERENCE LIMIT 1
- REST API
recently viewed items resource
- Metadata API
User references are maintained: Users in your development environment (such as a sandbox) are migrated to your production organization or other sandbox. Previously, user fields were replaced with the name of the user performing the deployment. This required editing after the deployment to assign the correct usernames. Now, Salesforce maps usernames to those in the destination organization during the deployment. Usernames in fields for components, such as recipients of workflow email notifications or dashboard running users, are migrated to the new environment to preserve as much functionality as possible. For more information, see “Maintaining User References” in the Metadata API Developer’s Guide.