Salesforce IdeaExchange

8070 Ideas; Promoted 170377 Times; 16407 Comments.

all Ideas

Recent Votes
Recent Articles

Alphabetize the setup options (or at least organize it a bit better)

I often find myself in the Setup screen hunting around for what I'm looking for...

There's another idea on the IdeaExchange to add a search functionality to the Setup screen... I think that idea is definitely better than this one...but if that idea is still a ways off from being implemented, it may be helpful to at least sort in alpha order...rather than the current "organization," which seems to be a bit random.

Rename the "Call Center" app (re-brand?)

Service and Support is so much more than just the high-volume call center processing that this naming implies. Please rename this app.

Run APEX/Triggers/etc Code as Another Profile (doAs)

The ability to delegate execution of APEX code under another profile.

Scenario:
Currently a profile that has APEX Enabled turns on a lot of features that may violate business & security practices and should be disabled. Example if you are using an SControl calling APEX webserivces on a standard user, it will fail because APEX is not enabled. If it's enabled the standard user can do lots of stuff they shouldn't. This could violate business and security policies.

Feature:
The feature is the ability on Triggers/Classes/etc, at configuration time, specify a doAs Profile to execute the requested operations with APEX enabled, restricting features to a specific profile (or set of profiles). The consuming profile (standard user) could have privileges to execute the doAs operations, but without receiving all the rights of the privileged profile. The privileged profile could specify the set of profiles that have rights to use it's services. This is very similar to doAs in Java JAAS architecture and is very useful in security and isolation of functionality.

API Access to FY Setting in Organization object without View All Data

It is impossible for appExchange partners or orgs to create custom apps that maintain user security and allow users to select data based on fiscal year setting. Currently the only way for a user to have access to Fiscal Year settings through SOQL and the Web Services API is either:
* Grant them View All Data Access, or
* Enable Customizable Forecasting

I want to allow users to leverage the Fiscal Year settings stored in Salesforce within other non-native apps without enabling additional features or side-stepping security.

Salesforce.com Needs Better Logging Support

Salesforce NEEDS better logging capabilities for errors/exceptions/security violations/etc. Today Salesforce supports the System Log (when APEX is enabled) at the top of the page, which is very cryptic and limited in feature/function.

Salesforce needs post mortum logging, features can be turned on via Configuration->Development->Logging and log through the life of the appication for an acceptable timeframe or rolling logs.

Features Include:
- Security Exception Logging
- APEX Exception Logging/Tracing <not />
- Web2Lead conversion logging <no>
- WebService logging
- Portal logging
- Trace logging (System.debug/others)
- Assert messages

The support would allow admins/developers to go in after the fact and determine what happended with a rule/trigger/webservice etc and correct the issue. Today a lot of time is spent trying to recreate the issue using the apex cryptic popup log feature.

Analytic Snapshot Test Button

Would be nice if we could setup an Analytic Snapshot and run a test on the config. Only option now is to establish a standard schedule. Pushing a test button would be a nice feature.

Package Standard Button Overrides

When you override the functionality of a standard button (e.g. "New", "Edit", "Clone", etc.) in an app, you cannot package this override as part of your app, even for Custom objects. This is really annoying for the end user of the app as it requires numerous additional setup steps, especially if you have lots of overrides as part of your app.

Administrative alerts to contain the associated org ID

Frequently, I get emails from the salesforce system that notify me of API threshold limits, high storage utilization, etc. and they contain no information about what instance the message is referring to. I'm a partner and work with multiple companies but the same problem occurs for organizations that have deployed multiple instances for whatever reason.

For instance, an email I got yesterday:
------
This is an automated notification sent to you at your request by Salesforce.com.

Your organization has made 109953 API calls within the last 24 hours. This is 53% of your organization's 24-hour API call limit of 208000 calls. You will receive this notice once every 24 hours until your organization's API usage drops below 50% of your 24-hour call limit (104000 calls).
...
-----
I don't know if this is for one of my development orgs, a production org and for which client.

I'd like to see the org ID or org name merged into the content.

Ability to edit standard price book views.

Currently it is not possible to edit the standard view of a price book.

This means users have to unnecessarily create a duplicate view that they then have to edit to give them the look and feel they want while managing their views.

And when they do this, they can't delete the original system generated view.

Come on SFDC, you know it makes sense.

Allow "Refresh from Server" during deployment in eclipse

So often when you are trying to deploy a large amount of changes, one small field has not been refreshed from the Sandbox into Eclipse - or more typically has not been added to the proper package so your unit tests run, but the deployment validation fails.

Rather than having to close out of the entire deployment flow, select "Refresh from Server" and then redeploy, it would be MUCH more efficient to have that option during the deployment since just getting all of the items selected to deploy (oftentimes 50 out of 200 items are all you want to deploy) and even generating the payload takes a lot of time.

The deployment process is very time consuming currently.

Permit enablement of "Allow Activities" for packaged custom objects

Once a custom object is placed in a managed package it's not possible to enable activity tracking on it. Without activity tracking it's not possible to create workflows on the object that create a task.

From SF Help:
"Before you create a workflow task for a custom object, make sure the custom object tracks activities."

It should be possible to enable activity tracking on custom objects that are in a managed package.