Salesforce Release: Developer Point of view

1. Choose Which Tests to Run in a Deployment : – Test levels enable you to have more control over which tests are run in a deployment. To shorten deployment time to production, run a subset of tests when deploying Apex components. As part of this change, the runAllTests deployment option is now replaced with testLevel. You can choose which tests to run in a deployment by setting the desired test level.

2. Access Any Data Anywhere with the Lightning Connector Apex Framework :- Use the Apex Connector Framework to develop your own custom adapter when the other available Lightning Connect adapters aren’t suitable for your needs. The custom adapter can retrieve data from external systems and synthesize data locally. Lightning Connect then represents that data in Salesforce external objects, which your users and the Force.com platform interact with.

3. View Query Plan Notes in Developer Console :- You can now view notes on your query plans in the Developer Console’s Query Editor. Salesforce displays all notes that are available for your highest-ranked query plan. To enable the Query Plan button in the Query Editor, click on Help | Preferences, set Enable Query Plan to true, and then click Save. The Notes pane displays in your Query Plan results

4. New Code Coverage Calculation for Multiline Statements :- Code coverage has changed for statements that are written on multiple lines. Each line that contains an expression is now included in the code coverage calculation for covered and uncovered code. Previously, a multiline statement was calculated as one line of code in code coverage. This change affects all API versions. As a result of this change, code coverage numbers can sometimes be calculated differently from the calculation done in Summer’15.

5. Reorder Your Batch Jobs in the Flex Queue Programmatically :- New Apex methods enable you to automate the prioritization of jobs in the flex queue. Previously, administrators could reorder jobs in the flex queue only from the user interface. For example, to move a job in the flex queue, call the System.moveFlexQueueJob() method and pass it the job ID and the new position.

Boolean isSuccess = System.moveFlexQueueJob(jobId, positionNumber);

6. Visual Flow Enhancement :- There are several enhancements in Visual workflow, those are followings

A) Verify Picklist Values in a Flow :- You can now create flow variables to represent picklist or Multi-Select Picklist values. Salesforce also added support for the ISPICKVAL() function in flow formulas.

B) Immediately Delete a Flow Version :- After you deactivate a flow version, you no longer have to wait 12 hours before you delete can it. Now you can delete a flow version as long as it isn’t active and doesn’t have paused or waiting interviews. If a flow version has paused or waiting interviews, wait for those interviews to finish or delete them.

C) Reference Global Variables in a Flow :- Visual Workflow now supports a subset of Salesforce global variables. Reference a global variable to access information about your organization or the user who’s running flow without using a query. Previously, you could access some of this information through lookup elements. However, unlike lookup elements, global variables don’t count against SOQL query limits. To add a global variable to a flow formula, open the Resources drop-down list and expand the SYSTEM GLOBAL VARIABLES section, as shown in the following screenshot

D) ~~See the Path That a Flow Interview Took Before It Failed (Beta)~~ :- When a flow interview fails, the flow creator receives an email with the subject “Unhandled process fault occurred…”. The email provides a message describing what went wrong. We added a list of every flow element that the interview executed so that you can see the exact path the interview took.

7. Process Builder Enhancement :- There are several enhancements in Prcoess Builder, those are followings

A) Compare and Return Values in Formulas :- Use newly supported functions to compare and return values in theProcess Builder. These new functions are now available to use in formulas.

INCLUDES
ISCHANGED
ISNEW
ISPICKVAL
PRIORVALUE

B) Update Fields Using Formulas and Date Functions :- When your process updates fields, you can now use formulas and date functions as the value, as shown in the following screenshot

C) Immediately Delete a Process :- After you deactivate a process, you no longer have to wait 12 hours before you delete it. Now you can delete a process, as long as it:

Isn’t active
Doesn’t have any pending scheduled actions

D) Define Additional Conditions When Updating Records :- When you update records in your process, you can now filter the records you’re updating using conditions. To add conditions in an Update Records action, please checkout the following screenshot

E) Use Multi-Select Picklists in More Places :- Previously, multi-select picklists were supported only when creating and updating records. Now you can also use multi-select picklists in process criteria, formulas, and quick actions.

8. Reduced Access for Apex Classes Using with sharing Keyword :- Apex classes defined with the with sharingkeyword no longer have unfiltered access to the User object if it’s set to private by the organization’s sharing rules. This change also applies to the Visualforce standard controller. Since this is documented behavior, this change shouldn’t affect pages that use standard controllers.

9. Streamline Managed Packages by Deleting Unused Components :- When updating a managed package, you can now delete permission sets and custom settings. By removing components that are no longer used by the app, you reduce its complexity and help create a more streamlined user experience for your customers.

10. See Which Apps, Tabs, and Objects Count Toward Organization Limits :- The number of custom apps, tabs, and objects that you can create or install in your organization depends on your edition and set of products purchased. You can now easily track how many you’ve used in your installed packages and how close you are to the limit for each.