Saturday, September 11, 2010

2010-09-11 Saturday - SalesForce.com Winter'11 Release Notes

I'm doing an evaluation this weekend of OrchestraCMS.com for a client's possible use in their adoption of SalesForce.com

As part of that evaluation, I spent some time reviewing the Winter'11 Release Preview information:

http://developer.force.com/releases/release/Winter11

http://na3.salesforce.com/help/doc/en/salesforce_winter11_release_notes.pdf

I've extracted a few items from the release notes that caught my attention:

Page-86
With Winter '11, developers and partners can use a new CTI Developer's Toolkit to build CTI adapters for call center users working with the Service Cloud console
Page-91
In Winter '11, the High Volume Customer Portal User license is generally available. After you purchase the license, you can assign it to Customer Portal-enabled contacts so that large numbers of users can log in to a Customer Portal without affecting its performance.

Page-114
Revised Governor Limits
For Winter '11, Salesforce.com is reducing the number of items limited by the Apex governor limits. In addition, many of the remaining items have had their limits increased.

Tests no longer run in a separate context: Prior to Winter '11, governor limits worked with three different contexts, with different amounts of resources allocated for each context. For Winter '11. tests no longer have specific limits. Instead, they've been included with triggers, anonymous blocks, Visualforce controllers, and WSDL methods.

Removed limits:
• Total request time for one callout (HTTP request or Web services call) has been removed.

• Maximum size for a callout (HTTP request or Web services call) has been removed.
Increases to existing limits:

• General heap size has been raised from 2 MB to 3 MB, with no scaling. In addition, batch Apex heap size is 6 MB.

• Apex classes and triggers have been raised from 100,000 characters and 32,000 characters, respectively, and can now be 1 million characters long, not counting comments, test methods, and classes defined with @isTest.

• Maximum amount of Apex code allowed in an organization has been raised from 1 MB to 2 MB.

• Total number of ChildRelationship, RecordTypeInfo and PicklistEntry objects allowed and total number of fields calls allowed has been raised from 10 to 100.

page-117 

New AllOrNoneHeader SOAP Header
The AllOrNoneHeader header allows the create(), delete(), undelete(), update(), and upsert() calls to roll back all changes unless all records are processed successfully. The default behavior is to allow partial success of a call: 

Force.com Web Services API Enhancements
records without errors are committed, while records with errors are marked as failed in the call results. This new header gives you more transactional control over commitment of changes.

Page-118
Force.com Bulk API Enhancements
The REST-based Bulk API is optimized to process a large number of records asynchronously. It allows you to load large batches of data that are processed in the background. The Bulk API has been improved for API version 20.0:
  • Support for Binary Attachments

  • With API version 20.0, you can submit batches containing binary attachments, such as Attachment records or Salesforce CRM Content.

  • Increased Number of Daily Batches Allowed

  • The limit of batches allowed per rolling 24–hour period has been increased from 500 to 1000.

Page-120
Salesforce.com uses the SAML 2.0 standard for single sign-on and generates SAML assertions when configured as an identity provider.

Page-124
OAuth Version 2.0 Supported
Starting in Winter '11, Salesforce.com supports version 2.0 of the OAuth protocol for authenticating Web applications that access data in a Salesforce.com instance.

A wealth of documentation is available:


http://wiki.developerforce.com/index.php/Wiki

http://wiki.developerforce.com/index.php/Documentation#Apex_Code

http://wiki.developerforce.com/index.php/An_Introduction_to_Visualforce

http://wiki.developerforce.com/index.php/An_Introduction_to_Force_Database

http://wiki.developerforce.com/index.php/Integrating_with_the_Force.com_Platform

http://wiki.developerforce.com/index.php/An_Overview_of_Force.com_Security

http://www.salesforce.com/us/developer/docs/api/

http://wiki.developerforce.com/index.php/An_Introduction_to_Builder



No comments: