Summer14 release notes are here! So much goodness here.
As usual there are a tons of new features in the release than those detailed below, so make sure you check out the Release Notes in case one of the features I've missed is important to you.
Salesforce1 supports Blackberry
The Salesforce1 mobile browser app is now supported in BlackBerry® Browser on BlackBerry Z10 mobile devices and in the Good Access™ secure mobile browser.
See More List Views
Salesforce1 users can now see up to 200 of their list views for an object, not just their four most recently accessed lists. This fixes one of my biggest problems with the Salesforce1 interface. I make heavily use of list views on a day-to-day basis and it was incredibly frustrating when the list view I wanted dropped off of the list, this enhancement will make it much easier to get to the information I need in Salesforce1 fast.
Drill Down from a Dashboard to a Report
Users can now drill right to a report from a dashboard. When viewing a dashboard in the Salesforce1 app, just tap a dashboard component to see the report that’s delivering the data to the dashboard.
Search and Edit Files with the Edit Menu
The new Edit menu in the Developer Console allows you to quickly access search and edit functionality. The following options are now in the Edit menu
Speed Up Queries with the Query Plan Tool
The new Query Plan tool in the Developer Console can help speed up SOQL queries done over large volumes. Use the Query Plan tool to optimize and speed up queries done over large volumes.
The Query Plan Tool sounds a lot like Execution Plan tool within SQL Server Management Studio and will finally provide much needed insight into long running SOQL operations and will provide much needed metrics to help with the optimisation of SOQL queries.
For admins, one of the more exciting features is the new ability to access Activity Report when creating formulas or validation rules in Activities. By adding this field, admins can set up specific follow-up dates or compare the actual date of the activity to the date the record was created. This access opens up a wide variety of possibilities to customizing your work queue for users
Describe limits removed for all API versions
Limits for all Apex describe calls have been removed for all API versions. Describe calls include describes for sObjects, fields, field sets, child relationships, picklists, and record types. You’re no longer limited to describing 100 objects or to executing 100 describe statements.
Whilst I've never actually hit this limit myself, one less limit to worry about is a good thing.
Increased API limits
The maximum number of API requests for a Developer Edition organization has been increased from 5,000 to 15,000.
At last! I'm still not sure if this limit is high enough, but it's a lot better than the previous one which I've managed to hit after about 2 hours of work, at least now I'll be able to do a whole day's work whilst using a Developer Edition.
Attach Larger Files, Up to 25 MB, to Objects
We’ve increased the size limit for attachments to objects from 5 MB to 25 MB. Collaborate more easily with larger attachments to cases, accounts, orders, and other objects.
Receive Incoming Emails of up to 25 MB
We've increased the size limit for incoming email messages from 10 MB to 25 MB, making it more likely that you’ll receive even long messages with multiple attachments in their entirety.
Increased Maximum Number of Relationship Fields
The maximum number of Relationship Fields per object has been increased, from 25 fields to 40 fields.
Increased Maximum Length for Long Text and Rich Text Fields
The maximum length for Long Text and Rich Text custom fields has been increased, from 32,768 characters (32 KB) to 131,072 characters (128 KB). The default length remains 32,768 characters, and existing fields are unchanged. To increase the length of an existing field, edit the field in Setup
I've grouped all of these together, because whilst these are not the most exciting of changes they are well worth knowing about and allow developers even more flexibility when developing on the platform.
Submit More Batch Jobs with Apex Flex Queue
The Apex Flex Queue pilot enables you to submit batch jobs beyond the allowed limit of five queued or active jobs. Any jobs that are submitted for execution but aren’t processed immediately by the system are in holding status and are placed in a separate queue (the Apex flex queue). Up to 100 batch jobs can be in the holding status.
Administrators can modify the order of jobs that are held in the Apex flex queue to control when they get processed by the system. For example, you can move a batch job up to the first position in the holding queue so that it is the first job that gets processed when the system fetches the next held job from the flex queue.
The current limit of 5 queued or active batch jobs is small and there is no way of managing your batch queue unless you roll your own solution for scheduling and submitting batches. This pilot should vastly improve batch jobs in Salesforce and make them much easier to use for both developers and administrators.
Run Future Methods with Higher Limits
Avoid reaching governor limits in your asynchronous future method by running your method with double or triple capacity for a resource. Apex future methods (methods that are annotated with @future) currently have the higher asynchronous limits for heap size, CPU timeout, and number of SOQL queries. This pilot enables you to specify even higher values for these and for additional limits in future methods.
One of the following limits can be doubled or tripled for each future method
Visual Flow Enhancements
- Manipulate Multiple Salesforce Fields and Records at One Time in a Flow (Generally Available) :- Collect the values for multiple fields for Salesforce records with a single query, and manipulate that data with a single DML statement by using sObject variables, sObject collection variables, and loops in a flow. In Spring ’14, this functionality was available only with a pilot program.
- Changes to Trigger-Ready Flows :- New Methods of Launching Trigger-Ready Flows You can now launch a trigger-ready flow with these new methods, which are generally available.
- The Apexstart() method A custom button or link The flow URL The Run button in the Cloud Flow Designer
- Cross-Object Field References in Flows :- Now you can reference fields for records that are related to the values that are stored in an sObject variable. To do so, you must manually enter the references. You can reference cross-object fields to use their values anywhere you can reference a flow resource or enter a value.
- Send Email from a Flow :- Now you can send enail from flow. You now have two options for sending email from a flow: call an existing workflow email alert or configure the email within the flow.
The Summer14 release will be out in June but is available for Sandbox installation now. Even this time salesforce concentrated more on the mobile platform.