SFDC Know How

With Summer'14, the Limits methods for script statements have been removed but are available and deprecated in API version 30.0 and earlier. Because the script statement limit is no longer enforced in any API version since Winter ’14, the associated Limits methods are no longer needed. The affected methods in the Limits class are: getScriptStatements() getLimitScriptStatements( )

With Summer'14, 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 xecuting 100 describe statements.

With Summer'14 The maximum number of Relationship Fields per object has been increased, from 25 fields to 40 fields.

With Summer'14 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 haracters, and existing fields are unchanged. To increase the length of an existing field, edit the field in Setup.

With Summer'14 External Organization-Wide Defaults enable you to set a different default access level for external users. Previously, if your organization wanted Public Read Only or Public Read/Write access for internal users but Private for external users, you would have to set the default access to Private and create a sharing rule to share records with all internal users. With separate organization-wide defaults, you can achieve similar behavior by setting the default internal access to Public Read Only or Public Read/Write and the default external access to Private. These settings also speed up performance for reports, list views, searches, and API queries. External organization-wide defaults simplify your sharing rules configuration and improve recalculation performance. Furthermore, they reduce overhead of sharing checks for search and reports, and improves sharing maintenance around realignments.

With Summer'14 release, the limit has been raised from three to seven for external IDs on custom fields per object. Very helpful indeed!

When setting the Login IP Ranges for a profile or your organization, you can also enter a description for each range to help identify the purpose of the range setting. To view or edit the Description field for login IP ranges for each profile: From Setup, click Manage Users > Profiles , then select a profile. In the profile page, go to the Login IP Ranges section. As you add or edit a Login IP Range, use the Description field to provide details, such as which part of your network corresponds to the range.  Very important feature for the organisations which have IP restriction in place. It was really difficult till now to keep track of which IP range is there for which location.

Clickjacking is a type of attack that tries to trick a user into clicking something, maybe a button or link, because they perceive they are clicking something safe. Instead, the button or link performs malicious actions on your site leading to data intrusion, unauthorized emails, changed credentials, or other site-specific actions.  Hidden iframes that load your site's pages can be placed maliciously by an unrelated page that entices the user to click a button or link that appears below the hidden iframe. With clickjack protection, you can configure whether your browser allows frames or iframes over your site pages. The default clickjack level for Site.com is set to Allow framing by the same origin only. You can set the clickjack protection for a site to one of these levels: Allow framing by any page (no protection) Allow framing by the same origin only (recommended) Don’t allow framing by any page (most protection) Note: Same-origin framing allows the site’s page t

The daily limit for emails that are sent from email alert actions was changed for free and trial organizations in Spring'14. For Developer Edition organizations and those evaluating Salesforce during a trial period, email alert actions in workflow rules and approval processes can now send a maximum of 15 emails per day per standard Salesforce user license.

Use the Analytics API via Apex for faster performance and easier maintenance. All the capabilities of the Analytics REST API are also available in the Apex API. The Analytics REST API, introduced in Winter ’14, gives developers access to many reporting and charting features that were previously available only through the web interface. If your customization strategy rests on Apex coding rather than the REST API, you can now use Apex to make all the same calls you can make with the REST API. For example, here’s a way you could use Apex to automate a reporting workflow. This Apex code takes a report ID and message as input, runs the specified report, and posts a Chatter message to every user or entity listed as a grouping. Reports.ReportResults res = Reports.ReportManager.runReport(reportId); FeedItem[] posts = new FeedItem[res.getgroupingsDown().getgroupings().size()]; for(Integer i=0;i<posts.size();i++) {     FeedItem post = new FeedItem();     post.ParentId = UserInfo.ge