Those who have delved into the administration of Salesforce will notice that there are certain limitations on features (ie. 1000 email send limit per day) as well as undocumented features and features that require Salesforce support to directly enable in your system (org). Below is a collection of capabilities that can be “unlocked” with a call to Salesforce, and sometimes some persuasion and justification.
Certain SFDC features aren’t available by default – you must log a support case from your SFDC org, requesting SFDC to enable (or “provision”) them. Typically, they then send you a long email with all the details, which you must confirm and acknowledge, before they’ll actually activate the feature.
Some important activatable features are -
- Documented in SFDC’s How to Enable Additional Salesforce Features:
- Multiple Currencies
- Insertable System Fields
- Territory Management
- Single Sign-On
- Divisions
- Person Accounts
- Translation Workbench
- Extended Mail Merge
- Email Relaying
- Encrypted Custom Fields
- Outbound Messages (from Workflow)
- Making Product Quantity & Sales Price Optional
- Restricting users’s email addresses to an approved list of email domains
- Not documented, but definitely doable upon request to SFDC
- @future Apex keyword
- Disabling confirmation of changes to users’ email addresses (Requires approval from a CIO-level manager, and enabling user email domain restrictions first)
- Increasing org-wide Apex code limit
- Increasing the number of External IDs by object from 3 to X
Important notes:
- You may not be able to activate some features in a sandbox. (Pre-2009, no features could be activated. Now, some apparently can be.) Ask in advance to be sure – if not, the only way to get them there is to activate them in a production org, then do a refresh. This may require careful planning!
- There is often confusion on the SFDC side about what is possible to activate directly in Sandbox. We have been told by numerous people at SFDC that it was impossible to change licenses in Sandbox without a refresh. The license changes DO need to be made in production first, but a Sandbox refresh is NOT required.
- Multi-currency requires 30 minutes or more of org downtime. You’ll need to plan this with SFDC support during an acceptable customer maintenance window.
Certain “limits” of SFDC may be extendable, if you know to ask.
Typically, these will require logging a support ticket with SFDC.
- Field History Tracking – normally limited to 20 fields per object. SFDC may increase to 40-50.
- Apex Code Total Size – normally limited to 1MB 2MB (extended in Winter ’11).
- Attachment Size – normally limited to 5MB per file. SFDC can extend to at least 50MB.
- Future Method Limit – You can increase the number of @future method calls over the 200 limit per day per user.
- Sandbox refresh < 29 days – you can refresh your sandboxes once every 29 days, but sfdc will do it for you if you open a ticket.
- Daily apex / mass email limit – normally 1k per day. SFDC raised this to 15K per day but likely will push back hard for justification.
- Web-to-Lead daily limit – normally 500 but SF can raise to 2k per day w/o much hassle.
- Number of Rollup Fields limit – Normally limited to 10, but can be increased to at least 15.
- Number of Objects References by Formulas - Normally limited to 10, but can be increased to max 15 SFDC Support warned of performance issues that could then surface, like with list views.
- Roles – Normally limited to 500. Premier support rep was able to raise to 1,000 w/o hassle.
- Active Rules (Workflows/Escalation Rules, Auto Response, Assignment Rules) – normally limited to 50 active rules per object although Salesforce can increase to 300 without special approvals.
- Batch Limit - 500 batches per rolling 24 hour period. Can be increased with justification. More info on Batch Limits: http://www.salesforce.com/us/developer/docs/api_asynch/Content/asynch_api_concepts_limits.htm
- Apex Code Coverage – Can be temporarily decreased from 75%
- External ID – Normally 3. Can be increased to 5 or more in some custom objects.
