About two weeks ago, I posted a list of the many setup steps I took to make my Winter ’10 prerelease org useable. Those are the same steps I have to take whenever setting up any Developer Edition org for the first time as well.
An insider at salesforce.com forwarded me this email that a senior person sent to quite a few also-senior people on various product teams:
- Subject:
- Preparing a New Org. Each Pre-Release. In 27 steps.
Body:
Yikes. http://www.x2od.com/2009/09/16/preparing-a-new-org.html
This is not the most widely-read blog about Salesforce, but it feels good to know that salesforce.com does have its ear to the ground and is taking seriously even the indirect feedback that we bloggers provide.
Kudos, salesforce.com.
PS. While I’m at it, I may as well also mention that too many fields are invisible to every profile. Example on Account: Site, Ownership, SIC Code, and more. And Annual Revenue is invisible to Customer Portal users. It would be great to have a guide or documentation.
PPS. Turns out that there’s no rhyme nor reason why some orgs have various fields invisible. Between demo, developer, trial, prerelease, and more, some fields are available and some are not. It is a huge waste of time to find all the fields and enable them.
RSS Feed
They do actually listen, you are right! One of my buddies at Appirio complained that the new login screen was confusing and they changed it in a matter of days. Take that SAP!!
Well that’s short and to the point.
They may have a light touch but there’s no question Salesforce.com focuses on and has successfully enabled a very powerful community.
A great change coming out of this would be a single screen to set many of these random settings. Perhaps it’s a screen you get to on initial launch of an org and also one that is easily accessible in Setup.