Salesforce Winter ’14 introduced significant platform enhancements that transformed how organizations manage CRM functionality, sandbox environments, and user access controls. This comprehensive guide covers the major features released in Winter ’14, with practical implementation guidance for Salesforce admins and developers.
Performance Edition: Enterprise CRM with Integrated Platform Services
Winter ’14 launched Performance Edition in November 2013, combining core CRM functionality with Force.com platform capabilities. This edition integrated Data.com for lead enrichment, Work.com for performance management, Identity services for single sign-on, Live Agent for real-time customer support, and Salesforce Knowledge for content management.
Performance Edition targeted organizations requiring comprehensive customer relationship management with advanced platform features. The edition included all Unlimited Edition functionality plus:
- Clean, targeted lead and customer data from Data.com integration
- Coaching and feedback tools from Work.com for employee performance tracking
- Trusted identity services for secure authentication across applications
- Additional sandbox functionality for development and testing environments
As of November 2013, Unlimited Edition became unavailable for new purchases. Existing Unlimited Edition customers could maintain their current subscriptions or upgrade to Performance Edition for enhanced functionality.
Developer Pro Sandboxes: Enhanced Storage and Renamed Configuration
Winter ’14 renamed “Configuration Only” sandboxes to “Developer Pro” sandboxes, reflecting their expanded capabilities. The release significantly increased storage limits across sandbox types:
| Sandbox Type | Previous Storage Limit | Winter ’14 Storage Limit |
|---|---|---|
| Developer | 10 MB | 200 MB |
| Developer Pro | 500 MB | 1 GB |
| Full Sandbox | Same as production | Same as production (unchanged) |
These storage increases enabled more comprehensive testing scenarios and larger metadata deployments in development environments. Developer Pro sandboxes supported configuration-only refreshes while maintaining the expanded storage capacity.
User Sharing: Granular Access Control for Internal and External Users
User Sharing became generally available in Winter ’14, providing standard sharing functionality for user records. This feature addressed common Salesforce security interview questions about controlling user visibility within organizations.
User Sharing enabled administrators to:
- Set organization-wide defaults for user records to Private or Public Read Only
- Create user sharing rules based on group membership or custom criteria
- Configure manual shares for user records to grant access to specific users or groups
- Control external user visibility in customer portals and communities
Winter ’14 automatically enabled User Sharing in new organizations. Existing organizations required contacting Salesforce support to activate the feature.
User Sharing Implementation Example
Consider a manufacturing organization with multiple dealer networks. Using User Sharing, administrators could:
- Set user object organization-wide defaults to Private
- Create sharing rules for dealer groups requiring collaboration
- Assign “View All Users” permission to managers needing organization-wide visibility
- Configure manual shares for specific cross-dealer partnerships
To review user access permissions, navigate to Setup > Manage Users > Users in Classic interface or Setup > Users in Lightning Experience.
Custom State and Country Picklists: Standardized Address Data Entry
Custom State and Country Picklists achieved general availability in Winter ’14, replacing free-text address fields with standardized ISO-3166 compliant picklist values. This feature improved data quality and supported advanced reporting scenarios commonly discussed in Salesforce admin interview questions.
The picklists appeared in address fields across standard objects:
- Account (billing and shipping addresses)
- Contact (mailing and other addresses)
- Lead (address fields)
- Campaign Members (address data)
- Contract and Service Contract objects
- Quote objects
- Person Accounts (when enabled)
State and Country Picklist Benefits
Implementing standardized picklists provided several advantages:
- Data Quality: Eliminated address field variations and typos
- Reporting Accuracy: Enabled reliable geographic reporting and dashboards
- Integration Compatibility: ISO-3166 standards supported external system integration
- User Experience: Dependent picklists automatically populated state options based on country selection
The picklists functioned across Salesforce interfaces including record edit pages, list views, reports, dashboards, workflow rules, and assignment rules. Advanced Search supported state and country picklist filtering.
Implementation Note: Winter ’14 enhanced the beta version released in Summer ’13 with improved metadata discovery, Translation Workbench support, and Web-to-Lead form compatibility.
Deployment Monitoring Improvements: Enhanced Status Tracking
Winter ’14 improved deployment monitoring with detailed status messages on the Monitor Deployments page. These enhancements addressed common deployment challenges and supported quick deploy Salesforce scenarios using the Force.com Migration Tool.
Deployment Status Values
The enhanced monitoring included specific status indicators:
- Pending: Deployment queued but not started
- In Progress: Deployment processing with component and test progress tracking
- Cancel Requested: Rollback initiated but not completed
- Succeeded: All components deployed and tests passed successfully
- Succeeded (partially): Subset of changes committed with RollBackOnError = false
- Canceled: Deployment successfully canceled with no changes committed
- Failed: No changes committed due to missing files, component errors, or test failures
Additional improvements included:
- Start Time displayed actual deployment start (In Progress) rather than queue time (Pending)
- “Abort” button renamed to “Cancel” for consistency with status terminology
- Enhanced error messaging for troubleshooting deployment issues
Winter ’14 Impact on Salesforce Integration Patterns
Winter ’14 features influenced common Salesforce integration patterns through:
- User Sharing: Affected API queries requiring user record access permissions
- State/Country Picklists: Required integration updates to handle picklist values instead of free text
- Performance Edition: Provided additional integration endpoints through Data.com and Identity services
- Enhanced Sandboxes: Supported more comprehensive integration testing with increased storage
Migration Considerations for Winter ’14 Features
Organizations upgrading to Winter ’14 features should consider:
User Sharing Migration
- Review existing user access patterns before enabling User Sharing
- Plan sharing rule migration for complex organizational hierarchies
- Test API integrations that query user records
- Update custom applications that assume universal user visibility
State and Country Picklist Migration
- Audit existing address data for standardization requirements
- Update workflow rules, validation rules, and assignment rules referencing address fields
- Modify integration mappings to handle picklist values
- Plan user training for new address entry workflows
Frequently Asked Questions
What happened to Unlimited Edition after Winter ’14?
Unlimited Edition became unavailable for new purchases in November 2013. Existing customers could continue using and renewing their Unlimited Edition licenses or upgrade to Performance Edition for additional features like Data.com integration and Work.com functionality.
How do Developer Pro sandboxes differ from regular Developer sandboxes?
Developer Pro sandboxes (formerly Configuration Only) provide 1 GB storage compared to Developer sandboxes’ 200 MB limit. Developer Pro sandboxes support configuration-only refreshes and are designed for larger development projects requiring more metadata storage.
Can User Sharing be disabled after enabling it in an organization?
User Sharing cannot be disabled once enabled in an organization. Before enabling User Sharing, carefully plan your user visibility requirements and test the impact on existing integrations and custom applications that assume universal user access.
Do state and country picklists affect existing address data?
Existing address data remains unchanged when enabling state and country picklists. However, users must select from standardized picklist values when editing records. Organizations should plan data cleanup to align existing addresses with ISO-3166 standard values.
What deployment monitoring improvements help with quick deploy scenarios?
Winter ’14 enhanced deployment status tracking with detailed progress indicators, accurate start times, and clearer error messaging. The improved monitoring helps identify deployment bottlenecks and provides better visibility into component-level deployment progress for quick deploy validation.