Spring '16 Important Features

1. 1.     Platform Security Health Check
   Spring ’16 provides an interesting new security Health Check feature that enables the current org configuration to be compared against a Salesforce recommended baseline. Any feature that highlights security risk or vulnerability is positive addition and should help mitigate against complacency.
   2.     Lightning Experience – Person Account Compatibility (Beta) enabled
   3.      List View filters can now be edited on-the-fly and record detail pages support inline editing. Both features providing enhancement to the general user experience.
   4.     Lightning Experience – Detect User Experience –
   Support is now provided for Apex script to reliably detect the current user experience, i.e. Salesforce1, Lightning Experience, Salesforce Classic. New Apex methods are available (User.UITheme and UserInfo.getUiTheme()) that provide a standardised approach that replaces the previous use of the sforce.one JavaScript global (and its unsupported approach caveat).
   5.     Apex Unit Tests
   New developers writing Apex Unit tests have suffered for years with the platform constraint that setup and non-setup objects can’t be created in the same Apex transaction (Mixed DML Operation Error). Typically this is problematic where User records are created in the test context alongside test records such as Accounts etc. With Spring ’16 it is now possible to create the setup object via @future method. A second improvement in context is the ability to change record creation date field values using the System.Test.setCreatedDate method. Where record processing logic is temporal in nature this ability will be helpful in writing tests that correctly validate the code logic.
   6.     Enterprise Edition customers now get access to 25 developer sandboxes instead of 1