{"id":5562,"date":"2016-06-28T00:42:41","date_gmt":"2016-06-28T00:42:41","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=5562"},"modified":"2016-06-28T01:58:15","modified_gmt":"2016-06-28T01:58:15","slug":"summer-16-top-features","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/summer-16-top-features\/","title":{"rendered":"Salesforce Summer 16 – My favorite top 20 features"},"content":{"rendered":"

Summer 16<\/a> is already in production and most of you already knows what’s there in pandora box. In this post, I will share\u00a0my favorite 20 features of Summer 16 release.<\/p>\n

\"Salesforce<\/a>
Salesforce Summer 16<\/figcaption><\/figure>\n

1. Clone Sandbox (Pilot)<\/strong>\u00a0: This feature is not yet generally available however worth mentioning. Till now, we could create Sandbox only from production, however Summer 16 gives us a way to create brand new sandbox from other existing sandbox instead of production.<\/p>\n

2. New Trace Flags in Debug Log<\/strong>\u00a0:\u00a0Now we can add trace flags on Automated Process, User, Apex Trigger and Apex classes as well. Before this release, we could only add trace flag on user. This enhancement\u00a0will give developers more control over what to display in debug log and overcome debug log size limit problems<\/a>.<\/p>\n

\n

\"Salesforce<\/a><\/p>\n<\/div>\n

<\/p>\n

3. User Provisioning support in Apex Test class<\/strong>\u00a0: Until now, it\u2019s been a challenge to test and manage the user provisioning process. But that\u2019s changed with the new test utility class for writing automated tests. Use the testConnectorUtil<\/em> class to write automated tests that simulate user provisioning. Invoke the createConnectedApp<\/em> method within an Apex test to create an instance of your connected app. For managing the provisioning process, Salesforce has extended the UserProvisioningRequest<\/em> object to better handle provisioning failures.<\/p>\n

4. Tooling API now supports Test Level<\/strong>\u00a0: The Tooling API\u2019s runTestsAsynchronous()<\/em> SOAP call and \/runTestsAsynchronous\/<\/em> REST resource now take a testLevel<\/em> parameter. Providing a TestLevel enum value of RunSpecifiedTests, RunLocalTests, <\/em>or RunAllTestsInOrg<\/em> lets you quickly and easily set up test runs. This parameter is required in the SOAP call, although its value can be null. For the REST resource, the new parameter is optional.<\/p>\n

5. Asynchronous web service callout supported by Named credential :<\/a><\/strong>\u00a0Named credentials are now supported in asynchronous web service callouts that use the Continuation <\/a>class. Previously, named credentials were supported in web service callouts that ran asynchronously only via Queueable Apex, that is, by implementing the Queueable interface.<\/p>\n

6. Skeleton Code for Global Apex Classes in Installed Managed Packages<\/strong> :\u00a0You can now view skeleton code that includes the global constructors, methods, variables, and properties for global Apex classes in the managed packages you\u2019ve installed in your org. Formerly, when you viewed these classes in Setup you saw their constructor and method signatures, but in other development environments you saw only (hidden)<\/em>. You can still see the constructor and method signatures in Setup.<\/p>\n

7. Get a Map of Populated SObject Fields<\/strong> :\u00a0A new method getPopulatedFieldsAsMap()<\/em> \u00a0has been added on the Apex SObject class that makes it more efficient to iterate over fields that have been populated in memory. Previously, iterating over just the populated the fields of an SObject involved some complicated programming. For example, if you queried an SObject using SOQL, it wasn\u2019t easy to tell which fields were returned.<\/p>\n

8. Create Lightning Components with Configuration<\/strong> : Now we can create Lightning component with configuration\u00a0from developer console. Example : before this release, we had to mention in our code that if Lightning component can be used in navigation by specifying\u00a0force:appHostable<\/em> interface.\u00a0\u00a0There are few other interfaces as well, which we needed to remember.<\/p>\n

\"Salesforce<\/a>
Salesforce Summer 16 Lightning Component Configuration<\/figcaption><\/figure>\n

9. Reference Static Resources with the $Resource Global Value Provider<\/strong>\u00a0: Before this release we had to provide URL of static resource in <ltng:require> tag. From Summer 16, to reference a specific resource in component markup, use $Resource.resourceName<\/em> within an expression. Include CSS style sheets or JavaScript libraries into a component using the <ltng:require> tag. To obtain a reference to a static resource in JavaScript code, use $A.get(‘$Resource.resourceName’)<\/em>.<\/p>\n

10. Enhancements in existing Lightning Components<\/strong> : Below lightning Components have been modified to add extra features like support of native datepicker in mobile, using currency shortcuts like k,m,b or t in currency etc…<\/p>\n