In this post am trying to put together key features from Salesforce winter’16 release.  The major upgrade of Winter’16 release is responsive lightning experience User interface but for this release no support for person account will make it available to few customers post release. This will be 2 part series covering majority of features:

You can check release date of Winter’16 features for your production org from Salesforce trust site.

  • Achieve Faster search by Turning off record search on some objects.

While user performs search the string is searched across objects users has access. This sometimes results in slow search result if you have many records across objects. There has been new checkbox introduced named ‘Allow  Search’ to provide more control to administrator for what objects to include in search result. This option is available for existing objects on object detail page and for new objects  under ‘Search Status’ section.

‘Allow Search’ is turned on by default for existing objects and for new objects its turned off. If you want to allow users to search in new objects then make sure this checkbox is enabled.

  • More relevant search result when search contains punctuation marks.

This feature has been rolling from summer’15 release.

In certain situation when searching words containing punctuation marks like website address wouldn’t return relevant result from objects. With this update its possible to search words containing punctuation marks. For example you are searching for team xyz.com and within object’s field its stored as www.xyz.com then it will match and return all records containing string matching with xyz.com including or excluding punctuation mark.

  • The ‘record types’ can be found under under recent items list if you browsed it earlier for easy view and edit. 
  • Geolocation accuracy indicator in Address Compound object.

Address compound type will have new field named ‘GeocodeAccuracy ‘. This field can be used to populate accuracy value retrieved from geo-coding provider like Google map or any other. The value later on can be used by any external program or within salesforce to display accuracy of location found on map.

For example your search returns accuracy from geo-coding provider about 1200 meters for input address on an account. Now you can assign accuracy rating based on returned data and store it in ‘GeocodeAccuracy ‘ field. The field later on can be used to colour code location pin on map based on rating in ‘GeocodeAccuracy’ field.This gives user clear view of how accurate the result is.

  • UI changes for replace picklist functionality and email notification to admin after replace job completes.
  • You can now add up to 500 values into multi-select picklist. Also now you can create upto 25 roll up summary field instead of only 10.
  • Restricted picklist (Pilot)

Restricted feature will allow picklist to strictly adhere to values in it. Currently through apex classes, triggers or API calls its possible to add values which doesn’t exists in it. This can cause issues for reporting and data discrepancies. The checkbox ‘Strictly Enforce Picklist values’ available while creating new picklist. This feature is in pilot which means you have to contact salesforce support to enable it.

Note: Existing picklist can not be converted to restricted picklist.

  • Share picklist values across objects using global picklist (Pilot)

Sometimes you might have situation where certain set of picklist values needs to be reused across various objects. You can solve this problem by leveraging concept of global picklist. The global picklist allows to create common set of picklist and while creating new custom field of type picklist the global picklist can be selected to inherit values from it. The global picklist can be created right from setup tree.

Note:The global picklist are restricted picklist. You can not add any more values to global picklist or picklist based on it through API.

  • Decommissioning of individual data import available for account, leads, solutions and custom objects.

 There are different set of import wizard available for account, leads, solutions and custom objects which will be replaced with unified import wizard. The unified import wizard with its interactive design will provide single interface for every object’s data import. The individual import wizards are not entirely going away but they can be accessed from  Data Management | Data Import Wizard. On the Data Import Wizard page, click Legacy Data Import Tools. See the comparison between unified and individual import wizard

  • Process builder changes

You can schedule multiple group of actions from single process instead of limited to one schedule action.

‘Update record’ action has an easy option to select record to update. You can choose whether you want to update record that started the process or select the specific record. Previously you can only select case object itself to indicate which record to update.

Scheduled actions will act based on current data. for example you have scheduled action to notify customer to pay billing amount 10 days after due date. If customer pays off balance before 10 days after due date then schedule action to send notification shouldn’t execute.

ID field can’t use contains, starts with or end with operator. Multi-select picklist can’t use contains operator.

  • Sharing changes.

If you are increasing organization wide default access then changes takes effect immediately instead of waiting for hours in environment where there are lot of data for recalculation. For example you are increasing access from public read to public read/write. In this case your changes takes effect immediately.

When new sharing rule is added or modified recalculation can take several hours and you can’t add or edit any other sharing rules. with new object specific share lock(pilot) you can edit the sharing rules on same object or any other objects from UI or API.

That’s it for now in first part of this post. There is lot more to come in second part of post. Leave your feedback/comments about the post.