Salesforce winter14 release notes

Following are few highlights in Salesforce winter14 release notes

Introducing Performance Edition 

Beginning in November 2013, Sales force offering a new edition that combines CRM and the Force.com platform with Data.com, Work.com, Identity, Live Agent, Salesforce Knowledge, and additional sandbox functionality.

Performance Edition is designed for customers that need to drive amazing growth, achieve new levels of customer satisfaction, and maximize sales and service success in the social and mobile world. Performance Edition includes all Unlimited functionality plus clean, targeted lead and customer data from Data.com, coaching and feedback tools from Work.com, trusted identity services from Identity, and more.

As of November 2013, Unlimited Edition is no longer available for purchase. Customers using Unlimited Edition can continue to maintain and renew their edition, or upgrade to Performance Edition.

“Configuration Only” Sandboxes Renamed to “Developer Pro”

The terminology is changing and the current “Configuration Only” sandboxes will now be known as “Developer Pro”. In addition, Developer and Developer Pro sandbox storage limits are increased as detailed below:

• Developer sandboxes increased from 10 MB to a 200 MB storage limit.
• Developer Pro sandboxes increased from a 500 MB to a 1 GB storage limit.
• Full sandboxes continue to have the same storage limit as your production organization

User Sharing—Generally Available

Control who sees who in the organization with standard sharing functionality.

User Sharing enables you to show or hide an internal or external user from another user in your organization. Previously, User Sharing for external users was enabled by default with Communities, while User Sharing for internal users was available through a pilot program.

With Winter ’14, User Sharing is automatically enabled in new organizations. You can:

• Set the organization-wide defaults for user records to Private or Public Read Only.

• Create user sharing rules based on group membership or other criteria.

• Create manual shares for user records to open access to individual users or groups.

• Control the visibility of external users in customer or partner portals and communities.

Existing organizations can contact salesforce.com to enable User Sharing.

How can your organization use User Sharing? For example, you might be a manufacturer who needs to include all dealers in your organization while still keeping them from seeing or interacting with each other. You can set the organization-wide defaults for the user object to Private. Then, open up access among groups of dealers who need to see and interact with each other in the organization with sharing rules or manual sharing. Additionally, you can assign the “View All Users” permission to users who need to see everyone in the organization.

To see who you have access to, from Setup, click Manage Users > Users.

Custom State and Country Picklists—Generally Available

State and country picklists allow users to select states and countries from predefined, standardized lists, instead of entering state and country data into text fields. State and country picklists allow for faster and easier data entry and help to ensure cleaner data that can be leveraged for other uses—in reports and dashboards, for example—with more dependable results. The states and countries in the picklists are based on ISO-3166 standard values, making them compatible with other applications as well.

State and country picklists are available in the shipping, billing, mailing, and “other” address fields in the account, campaign members, contact, contract, lead, person accounts, quotes, and service contracts standard objects. The picklists are also available for managing users and companies in Administration Setup. To use the picklists, first choose the country and then choose from the options that automatically populate the state or province picklist.

You can use the state and country picklists in most places that state and country fields are available in Salesforce, including:

• Record edit and detail pages

• List views, reports, and dashboards

• Filters, functions, rules, and assignments

You can also search state and country picklists using Advanced Search.For a step-by-step guide to implementing state and country picklists, see Implementing State and Country Picklists.

Note: In Summer ’13, Salesforce released a beta version of state and country picklists. Since then, we have made a number of improvements for general availability, including:

• Enhanced metadata discovery, which alerts you to potential problems in workflow rules, assignment rules, auto-response rules, and so on, when you enable state and country picklists.

• Enhanced support for Translation Workbench.

• Availability in Web-to-Lead forms.

Improvements to Deployment Monitoring 

Salesforce improved the status messages listed on the Monitor Deployments page to provide more information about the cancellation, success or failure of a deployment when you’re using the Force.com Migration Tool.

The values are:

• Pending—The deployment has not started. It is waiting in a queue.

• In Progress—The deployment process started, but has not finished. See the Components and Tests counts on the page to track the deployment progress.

• Cancel Requested—The deployment is being rolled back, but is not yet fully canceled.

• Succeeded—All components deployed successfully, and all tests ran successfully.

• Succeeded (partially)—A subset of changes were committed to the organization, but some files were missing, some components had errors, or some tests failed. You can only receive this status with the deployment option RollBackOnError = false.

• Canceled—The deployment has been successfully canceled. No changes were committed to the organization.

• Failed—No changes were committed to the organization because files were missing, components had errors, or tests failed. On the Monitor Deployments page, the Start Time now shows the date and time when the deployment starts (In Progress), not the time the deployment is waiting in a queue (Pending).

Also, the button to cancel a deployment has changed from “Abort” to “Cancel” to reflect the status messages more closely.

For more information of Salesforce winter14 release notes please click here