iPad Wallpaper (1024x768 at 132ppi)

(Click on the image to download the full-sized version.)

This is a new wallpaper background using the latest branding, at 480×360.

Blackberry Wallpaper 480x360px

For those of you using retinal displays, here’s one for you:

iPhone Wallpaper 640x960px

I expect to see you ALL using these at Dreamforce 2010!

(Thanks to Jamie Grenney at salesforce.com for the original image post years ago.)

First I'll list my conclusions, just so there's no misunderstanding. Then I'll explain some of the possible pitfalls that Chatter presents.

1. Chatter is amazing. It lets users share information in ways never seen before.
2. Chatter should be enabled in an org as an all-or-nothing switch - as it is now. Allowing it to be disabled for some users goes against its core purpose.
3. As a single-opt-in system, the risk of Chatter-Spam is huge, but responsibility falls to each user to self-police, and probably to each company to educate its users in appropriate chatting.

Let's compare Chatter, Facebook, and Twitter in terms of what is necessary for a conversation between two people to appear in my activity stream.

Facebook

Facebook is a double-double opt-in system. To see a wall post from one person to another in my stream, I must be friends with both of them, and each friendship-connection is a double opt-in, meaning that one person requests and the other approves.

Twitter

Twitter is a double-single opt-in system. To see one person's reply to another, I must be following both of them. But unless one of them decides to block me, the default is that I will see the entire exchange in my twitter feed.

Chatter

Chatter is a single-single opt-in system. This means that if I post something to anyone in the org, everyone following that person will see. Here's an example: Let's assume that every user at salesforce.com follows Marc Benioff. One user posts a photo of his son's graduation to Marc. Everyone following Marc will see it.

Sounds innocuous, right? Probably. But if a user keeps posting silly things to Marc, and enough people see it, other users could become annoyed.

Take it down a level, and imagine that everyone on a sales team follows each other. A junior AE keeps sending silly stuff to the strongest seller in the group, and all the sales people have to see it. This could clog their streams.

This is called a CLM: A Career-Limiting Move. As great power requires great responsibility, we must ask who should shoulder this responsibility.

1. The company: Training for users and a quick eye to bring inappropriate chatters into line.
2. Individuals: Just be careful. This is the Facebook public-posting dilemma. Don't forget that you have no control with whom you are connected, so anyone who wants to follow you will see anything you post, and anyone who follows someone you post to will see it as well.

The solution is NOT to turn off Chatter for certain people - Chatter is about the free-flow of data across an org, organized into forms that make it useful information. By putting information at the fingertips of every user, productivity will be increased.

Blocking people is also not a good solution.

Chatter Groups (Safe Harbor Statement!) will help, but will attenuate, not completely remove, the chances that this will happen.

Salesforce CRM should be a "sticky" app - that is, it should provide services in one place so that users see it as their central point of information. The best way to ensure the free-flow of information is to prevent blocking of certain users.

I successfully managed the licenses and tried to click the “Back to Previous Page” link, but something broke:

This should never happen for a Salesforce-generated URL

Here’s a video of the problem in action: Managing Licenses Previous Page Link Is Broken.

This is a story about the super-responsiveness of the salesforce.com support team. (I’m not including peoples’ names, but for any employees, it is Case 03580410.

I submitted my case May 24, and the first response was received May 25. The first person, JW, sent an email asking me to clear my cache and change my browser. I cleared the cache, used multiple browsers, and even tried with different packages in my org. All had the same problem.

May 27, JW tried to call me, but I was unavailable. (Good follow-up.) He also sent an email, and I promised to get back to him. I replied the next day and told him that the problem occurred even on different computers, with different browsers, and different packages. He quickly replied and asked to login to the org to try to recreate the issue.

The next step was for us both to login to the org while on the phone. He verified that the problem was happening, and we noticed something interesting:

Clicking “View Installed Packages” gives a URL like …/0A3?setupid… and clicking Manage Licenses gives a long URL including ?allPackageId=033600000004Pjn. The broken link was https://na7.salesforce.com/033600000004Pjn. See anything there?

The “Back to Previous Page” link should have taken me back to the /0A3 page (exactly as the browser Back button did), but instead tried to show me the inner workings of a package, which Salesforce clearly cannot display.

JW suggested that this was a problem with the app, as the link was on a page managing licenses for two managed apps by the same publisher. I quickly explained that I had developed managed applications before and that I knew that this was a feature created by salesforce.com, and therefore salesforce.com was responsible for the broken link. He said that he understood and that he would escalate the case to Tier 2.

Quick recap so far: Salesforce Support has responded quickly, so they get good points for that, but I’ve not been available to talk. The support rep has tried everything he and I can think of, and we have found a problem in a link that directs to the wrong URL. I’m up to Tier 2.

At this point, I don’t have any more communication until June 8. I’m not fussed, as I know it’s a real issue, but I have a good workaround (use the Back button).

June 8, GE sends me an email saying that he reproduced the error and escalated it to Tier 3 for further investigation. I thanked him and said that it felt bittersweet because I had found a real problem and it’s no fun when my beloved Salesforce CRM has a bug. He validated my feelings. (Warm fuzzies all around.)

The next day, GE sends an email. This is the text:

An issue tracking number has been attached to your case, and is awaiting prioritization by R&D. I will receive updates on this, but the timeline for rollout may not be known for some time. Just wanted to let you know that it has been queued up for a fix, and I will let you know more when I know. Feel free to check in any time, and also bear in mind that there is a very good workaround for this, being the browser back button J We’re just required to mention workarounds, even though I know you know this. Let me know if you need anything else.

Music to my ears! An issue tracking number! R&D looking into it! I had found a real bug and it would be fixed!

The point of all this is to say that for all the complaints (many justified) that people have about salesforce.com support (why do they automatically want login access when the problem sometimes has nothing to do with anything in an org???) there are times that they really shine.

Thank you, JW and GE. At least I know a fix is coming.

Salesforce CRM's formulas handle dates very well. If you want to enter a date value and have formula fields display, for instance, mydate__c + 21 days, that's simple. Just use mydate__c + 21.

Side note: If you try going the long way around and use DATE( YEAR( mydate__c ), MONTH( mydate__c ), DAY( mydate__c ) + 21 ) and mydate__c = 09/17/2010, Salesforce returns #Error! because there's no date 09/38/2010. Similarly, adding three months to a date like 1/31/2010 will also give an error. More about this in a future post.

DateTime fields are like Date fields, but they include... wait for it... a time component (and can be created in the running user's local time zone or in GMT).

Here's a use-case for a DateTime formula field:

A photography studio schedules photo shoots, and different packages include different durations. Similarly, we could use a hair salon which offers different services, each with a different duration, a dentist... you get the idea.

Requirements:

1. Enter a DateTime for an appointment start time (starttime__c)
2. Enter a duration (though in a production system, I'd include a value on the Product2 sObject, we'll just enter a value here) (minutes__c)
3. Display a read-only DateTime field with the end time (endtime__c)
4. The end time must be read-only to all users, like any formula field

Here's what won't work:

• A formula field won't work because there are no MINUTE(), HOUR(), SECOND() formula functions
• Workflow won't work because it depends on formulas to fill new values for date/datetime fields

That leaves Apex. First, the configuration:

1. Create DateTime field starttime__c
2. Create DateTime field endtime__c
3. Set endtime__c field-level security to Read-Only for all profiles
4. Create Number (18,0) field minutes__c
5. Create a trigger on the sobject

Here's the trigger:

trigger timeTrigger on TestObject__c (before insert, before update) {
    for (TestObject__c t : Trigger.New){
    	if(t.StartTime__c != null && t.minutes__c != null){
        datetime myDateT = t.StartTime__c;
        double d = t.minutes__c;
        Integer shootmins = d.intValue();
        if(mydateT != null && shootmins != null)
        	t.EndTime__c = myDateT.addminutes(integer.valueof(shootmins));
       	}
    }
} 

Regular readers will note that I do usually split triggers into a trigger and a class, but I've not done so here purely for the sake of brevity.

Here's the test code:

public without sharing class shootTimesTriggerTest {

    private static testMethod void ShootCalculateEndTime_PositiveTestCases() {
        TestObject__c to;
        TestObject__c l;    
        test.starttest();
        l = new TestObject__c (name = 'test');
        datetime myDateTime = datetime.newInstance(2008, 12, 1, 12, 30, 2);
        l.StartTime__c = myDateTime;
        l.minutes__c = 90;
        insert l;
        to = [SELECT id, EndTime__c FROM TestObject__c WHERE id = :l.id];
        datetime newDateTime = datetime.newInstance(2008, 12, 1, 14, 0, 2);
        system.assertequals(to.EndTime__c, newDateTime);
        l.minutes__c = 45;
        update l;        
        to = [SELECT id, EndTime__c FROM TestObject__c WHERE id = :l.id];
        newDateTime = datetime.newInstance(2008, 12, 1, 13, 15, 2);
        system.assertequals(to.EndTime__c, newDateTime);
        test.stoptest();
    }

    private static testMethod void OppCalculateEndTime_NegativeTestCases() {
        test.starttest();
        TestObject__c l = new TestObject__c (name = 'test');
        l.minutes__c = null;
        insert l;
        system.assertequals(l.EndTime__c, null);
        test.stoptest();
    } 
}

A few points about how this works:

• Triggers run in System mode, so they don't respect field-level security. Thus, we can set a field to read-only for all profiles, and the EndTime__c field will still be updated.
• The test code runs in System mode as well, avoiding any potential problems if the field were set to invisible to a profile and we used System.RunAs() to test for various profiles.
• Although I'm not a fan of using SOQL queries this often, I used these in the interest of saving time. Keep in mind that if you had quite a few queries in your regular code, adding these two might put you over the limit, so use queries sparingly!
• This is the only way I know of to add minutes to a DateTime.

Did I miss anything? Please let me know in the comments.

Overlapping this is another 8-hour window for NA0 (SSL) starting two hours earlier.

Also starting at 7pm PST, EU0 (EMEA) will be down for 2.5 hours.

All other instances will be down for 30 minutes, from 9pm PST.

As the email from salesforce.com explains:

Dear Salesforce Administrator, At salesforce.com, customer success through system availability and reliability is our top priority. As part of our ongoing plan to deliver high availability and reliability, we are enhancing our service infrastructure on our NA1 instance. Please be aware that salesforce.com will be performing scheduled maintenance that will extend beyond standard system maintenance windows. The current scheduled window is: Saturday, March 20th, 2010 from 7:00pm PST to Sunday, March 21st at 3:00am PST During this time, the salesforce.com NA1 service will be unavailable. Users attempting to access the service during this time will be presented with a scheduled maintenance notification page. We appreciate your patience during this maintenance window. Best regards, -salesforce.com Support

Copyright 2000-2010 salesforce.com - All rights reserved - Various trademarks held by their respective owners Salesforce.com, One Market Street, Suite 300, San Francisco, CA 94105

NA0 (SSL) March 20, 5:00 pm PDT - March 21, 1:00 am PDT The NA0 instance will have maintenance performed at this time. The instance will be unavailable for the duration of the maintenance. EU0 (EMEA) March 20, 7:00 pm PDT - March 20, 9:30 pm PDT The EU0 instance will have maintenance performed at this time. The instance will be unavailable for the duration of the maintenance. NA1 March 20, 7:00 pm PDT - March 21, 3:00 am PDT The NA1 instance will have maintenance performed at this time. The instance will be unavailable for the duration of the maintenance. All instances March 20, 9:00 pm PDT - March 20, 9:30 pm PDT The Salesforce.com Technology will be performing maintenance at this time. During this time all instances will be unavailable for the duration of the maintenance.

Firstly, you’ll need to contact salesforce.com to get this feature enabled.

Then be patient. It takes a minute or two for the update to propagate. Clearly, something was churning in the Force.com platform background!

Now we’ll navigate NOT to the Setup | Customize | User Interface screen (where this should be enabled). Instead, we’ll go to the Opportunity Page Layout screen.

Follow the cool prompts. They make it so easy, a … well, you know what I mean.

Step 1: Enable the Highlights Panel

Opportunity Layout Setup

Step 2: Edit the Page Layout

Choose Fields to Display

Note: You can only show fields in the Highlights Panel if they are in the page layout. (I have a feeling this has to do with Professional Edition or printable layouts, but I’m just guessing.)

Once you’ve done this for each page layout, click on the big button.

Confirmation - You are (mostly) done!

At this point, each user can enable the bar. I have no idea why the admin can’t just force this on all users – or maybe I missed something – but it seems to be an opt-in feature.

Step 3: Enable User Opt-In

Here’s the link to enable the feature. Of course, you may wish to watch a video as well!

The link to enable this setting

And here it is!

The new layout!

Return to top from the bottom of the page

It’s interesting that if you have this enabled, certain user interface settings (yes, at Setup | Customize | User Interface) cannot be changed:

When this is enabled, you cannot turn off two settings

Here’s my prediction: We will start to see two major mistakes during Salesforce demos:

1. We will continue to see the link asking if we want more information on inline editing (after more than a year, it’s time to turn that off, people).
2. At the top of the Opportunity detail page, we will see this link.

And I will continue to think less of all demonstrators who make these mistakes.

Happy Spring 2010!

I had this problem when Content was first released and I was asked to be one of the first SysAds to use it. At the time, we used Solution 1 (below), but since then, other products have been released to help with this.

Why is it even an issue?

• Surely we can download each file? Yes, but who wants to?
• Can't we do a Data Export and then upload those to Content? Yes, but all the files are renamed with their 15-character Ids, making renaming them all-but-impossible.

Solution 1

# Nick Marcantonio
# nmarcantonio at salesforce.com
# 08/07

$file = 'Attachment.csv';

open (F, $file) || die ("Could not open $file!");

$line = <F>; #read first line which is nothing but column headers
while ($line = <F>)
{
  ($id,$name) = split ',', $line;
  chomp($id);
  $id =~ s/\"//g;
  chomp($name);
  $name =~ s/\"//g;
  
  #print "$id : $name\n";
  
  $result = rename($id, $name);
  #print "$result\n";
}

close (F);

If you've done a data export you've noticed that all attachments are placed in the Attachments subfolder and named with their salesforce ID, not the actual file name or extension. One must then consult the Attachment.csv file included in the data export to find the name associated with the ID and rename the file. Attached to this solution is a Perl script that will rename all of the exported attachments to their proper names. Please follow these steps to run this:

1. Perform a data export and unzip the resulting zip file
2. Launch the data loader and export from the Attachments table ONLY the Id and Name column. This file must be named Attachment.csv.
3. Install ActivePerl. This will allow perl scripts to be run on a Windows machine. ActivePerl is available here (http://www.activestate.com/activeperl).
4. Copy the Attachment.csv file and the attached AttachmentParser.pl file to the Attachments subdirectory of the data export.
5. Double-click on AttachmentParser.pl.

All of the files named with their salesforce IDs will be renamed with their proper names and file extensions.

(This solution will work for documents as well. Follow the same procedure and be sure to name the extract from the Documents table Attachment.csv) 

Note: This will not preserve folders, as far as I know. You may be able to recreate this by exporting the Folder table and doing some work on that, as the Document table does include a FolderId column.

A heartfelt thank-you to Nick Marcantonio for his help!

Solution 2

Install DreamFactory's FREE DreamTeam Document Management application from the AppExchange to drag-and-drop your Documents to your desktop.
This doesn't work with Attachments, though, so you may need to use another method for them.

Please let us know how it goes - good luck and enjoy Content!

Although it was not clear how much of the demonstrated app will run on Force.com and how much will run on the CA servers (though it appeared to be 100% on Force.com), it was clear that the application was accessed via a force.com URL.

For more information, see http://www.ca.com/agile.

A release date for the product was not mentioned, but the earliest planned release of any newly-announced feature thus far is Spring 2010, so one might assume that this will not be available until then.

Workbook
http://www.salesforce.com/us/developer/docs/workbook/index.htm

Fundamentals
http://www.salesforce.com/us/developer/docs/fundamentals/index.htm

Cookbook
http://www.salesforce.com/us/developer/docs/cookbook/index.htm

Apex Advanced Code Example
http://www.salesforce.com/us/developer/docs/apexcode/Content/apex_shopping_cart_example.htm
https://sites.secure.force.com/appexchange/listingDetail?listingId=a0N30000001saDCEAY

And many more to come!

Salesforce Chatter is being pushed as a platform layer.

Looking at the “chiclet” slide that Marc Benioff unveiled, let’s start with the “old” slide:

Yes, this is not the exact slide, but getting a copy of the initial slide is proving difficult. We'll have to use this one from Dreamforce 2008 as a reference, and will need to imagine the rest.

• Notice that the bottom level is Infrastructure. This is the hardware that salesforce.com provides along with the promise that it will work properly. It is called Infrastructure as a Service, and there’s nothing new about that.
• On top of that is what we call the Force.com Platform. This includes Apex code, workflow, analytics, and Visualforce.
• And on top of that are the clouds: Service Cloud 2, Sales Cloud 2, and Custom Cloud.

However, the first new chiclet slide that Marc showed was misleading. The item with the big question mark was a cloud. And Chatter is not only a cloud.

Once Chatter was shown and demonstrated, the new chiclet slide did not just show it as a cloud. It was also shown as another platform layer. This is huge.

Chatter, clearly, is not just an application that sits on top of Salesforce CRM and the Force.com platform. (Examples of these are AppExchange apps like FinancialForce and even integration features like Google Docs for Salesforce.) Chatter is an integral part of the platform and will be a part of every customization. What does this mean? Just as with every custom object comes the ability to make Workflow and Validation Rules, with every custom object will come the ability to include Chatter features.

So let’s talk about the new slide. First, something negative:

From an IT perspective, we know that there are three levels to Software as a Service: Infrastructure as a Service, Platform as a Service, and Application as a Service. Where does Chatter fit in? I have no idea. In the Platform? No. Platform features are data-driven and can exist without a user-interface. In Infrastructure? Obviously not. So Chatter must be an Application. Obviously, salesforce.com is including Chatter as features in every application. But just because it is ubiquitous does not mean that it is a platform layer.

Now, something positive:

From a marketing perspective, nobody cares about the Service layers. Infrastructure? Platform? Application? All the people with money (CXOs) care about is what they’re going to get and what the product can do. If we look at the slide as a selling-tool, it’s perfect. It shows us features that are available across the board, in every object.

So my conclusion:

If I take off my developer hat, Chatter is a great feature that will help businesses run better. Sure, the slide is funny-looking, but it works.

And to all the tweeters out there, don’t forget to use #df09 and #forcedotcom!

I’m not sure what they’re trying to do, but they’re certainly not making it look like they’re worth my time. The Kim Jong Il joke is pathetic (though a deeper look at the text shows that it’s actually “Kim Jong II” – as in Kim Jong the Second) and there is at least one blatantly inflammatory remark:
Here’s a tip for SugarCRM: Salesforce CRM and the Force.com Platform are NOT SUPPOSED to run on Amazon SC2 nor Microsoft Azure!
To be fair, since Benioff is well-known for his demonstrations outside Oracle OpenWorld a few years ago (his own demonstration to which he alludes in his page 65 quote), SugarCRM’s tactic is understandable – but hopefully our Fearless Forceful Leader takes this more as a compliment (imitation and flattery and what-not) than an attack.
That’s all. No need to pick up a physical copy of the book – it’s available for download. In fact, I propose that someone host a copy on another site for download so that SugarCRM believes that far fewer people have downloaded the file.
Back to your regularly-scheduled Dreamforce programming.

Though a supplemental/unofficial guide to customizing SFDC for Twitter will be released soon on this site, I wanted to share a trigger I just wrote to add new Leads to a campaign:

Firstly, thank you to Scott Hemmeter at Arrowpointe, who wrote the original code that I customized.

Secondly, you could easily duplicate this trigger and set it to run on the Contact object as well.

Please don't set the trigger to "after update," as in testing, it ran into problems when converting a Lead and merging with a Contact already on the "Twitter" campaign.

trigger AddToTwitterCampaign on Lead (after insert) {

    // List containing each Lead being processed
    list<Lead> theLeads = new list<Lead>(); 
      
    //We only execute if we have a campaign named "Twitter"

    if([SELECT Count() FROM Campaign WHERE name = 'Twitter'] == 1){
        Campaign TC = [SELECT id, name FROM Campaign WHERE name = 'Twitter' LIMIT 1];
        
        for(Lead l:trigger.new) { 
            if (l.leadsource.indexOf('Twitter',0 ) >= 0 ||  l.leadsource.indexOf('Tweet',0 ) >= 0 ){  
                theLeads.add(l); // add lead to the main lead list
                }
            }
      
      // List containing Campaign Member records to be inserted
      list <CampaignMember> theCampaignMembers = new list<CampaignMember>(); 
    
      for (Lead ld:theLeads) {
          CampaignMember cml = new CampaignMember();
          cml.leadid = ld.id;
          cml.campaignid = TC.id;
          theCampaignMembers.add(cml);
        }

     //Insert the list of Campaign Members
      if(!theCampaignMembers.isEmpty()){
        insert theCampaignMembers;
        }
    }
}

The trigger requires that you have a Campaign called "Twitter," but feel free to change that to anything else you'd like.

Don't worry if you have other triggers that add Leads to Campaigns - this can work alongside them, so you can add Leads to as many Campaigns as you'd like.

Lookup filters function similarly to validation rules when you save a record. That is, actions that cause related records to save, such as changes to a roll-up summary fields, also trigger the lookup filters on the related record and block the save.

The implications for this are massive. Let's explore two examples:

Example 1: Filter as Validation Rule from Parent Record

• We create a lookup on a Child object to Parent.
• We filter the lookup to EXCLUDE Parent.Status = 'Closed' (Parent.Status is only Open or Closed.)
• We can edit the Child records as long as the Parent Status is not Closed.
• When Parent.Status is changed to Closed, existing related Child records are not affected...
• BUT if we attempt to edit a Child when the Parent is Closed, Force.com will throw an error (which we can customize) beause that the Lookup is invalid.
• (and clearly we cannot add new Child records either)

Conclusion: Thus, Filtered Lookups act much like Validation Rules. A quick experiment shows that Filtered Lookup errors actually fire before Validation Rules.

Example 2: Filter as Validation Rule on Roll-Up Summary (from Child Record) - what the line above was referencing

• Use the above example, but change the lookup to a master-detail relationship
• Create a Roll-Up Summary field to count all child records
• Prevent saving more than 10 child records for one parent record

Here, we have triggered a filter error without touching a parent record, yet we throw an error based on a value on the parent record.

This second example is significant because we could already prevent more than 10 child records from saving, but doing so required a Roll-Up Summary field on the parent object AND a Validation Rule on the child object. Now we can replace the Validation Rule with the Lookup Filter, though we still need the Roll-Up Summary field. Whether or not this simplifies things is definitely up for debate...

Conclusion

This is a very powerful feature! Thanks to salesforce.com for rolling it out, even in beta form.

Real world example: The above example would be great for Time Sheet Entry and Time Sheet Header objects, as they would create, in effect, a validation rule on the Header record preventing editing of any child records. Awesome!

For further reading, check Salesforce Help's Lookup Filters examples.

Our Daily Shinro site was listed “for sheer exuberance!”

I’m really proud of the site, though the lion’s share of the kudos go to John for the concept and site design. I just coded whatever he told me to code; he’s the creative one!

So if anyone is looking for a custom Force.com Site or website integration to Salesforce, contact us and let’s discuss your needs!

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.

Every time one encounters a fresh org, there are maintenance tasks to perform. I usually go through an org (whether a Developer Edition org or a Prerelease version) and do the same tasks, generally in no particular order. This time, however, I wrote down what I did as I did it. Looking at the list, it's hardly in any "best practices" order at all - it's just how I did it.

There's no need to follow every step, and it is not a complete list of all possibilities, but this should give you some idea of the possibilities and available tweaks: (*** indicates some of the new features in WInter '10)

1. Save login with 1Password/Roboform
2. Reset (Set) Security Token
3. Administration Setup | Security Controls
• Session time 8 hrs
• Passwords never expire
4. Create Record Types (and Business Processes) for Lead, Opportunity, Case
5. (Campaigns were not enabled in this prerelease org) - would have configured them here, similarly
6. Activities section: Calendar link on sidebar
7. Download latest versions of Connect for Outlook, Office Edition
8. Opportunities:
• Enable Similar Opportunities
• Enable Opportunity Teams
9. Create Account Master Record Type
10. Enable Account Teams
11. Create Contact Master Record Type
• Note: Asked to add to page layout. Not asked for Opportunities.
12. Enable Case Teams
13. Enable Public Solutions
14. Solutions:
• Enable Solution Browsing
• Enable Solution HTML
• Could have created a Solution Process & Record Type
• Did not enable multilingual solutions
15. Enable Self-Service
16. Enable Web-to-Case
17. Create default Owner, etc (auto prompted)
18. Enable PRM and Partner Portal (though have no licenses)
19. Salesforce to Salesforce
• Enabled S2S
• Set up S2S Connection Finder ***
• Added fields to page layout - Kept read-only for all profiles except System Administrator
• Enable Public & Private Tags
20. Enable Console for all Profiles
21. Search Settings - Enable Enhanced Lookup & Auto-Complete
22. User Interface
• Separate loading of related lists
• Spell Checker on Tasks & Events
• Collapsible Sidebar
• Custom Sidebar on all Pages
• Enhanced Profile Management ***
23. Set myself as default Workflow User
24. Looked at Develop | Custom Settings ***
25. Created a Default Queue and added myself
26. Set all Sharing Rules to Private
27. Update Home Page to the way I like it
• Order of wide section (top down): Calendar, Tasks, Items to Approve, Dashboard
• No changes to narrow section

Other things that may be possible in other orgs:

• Enable Customer Portal
• Customize Campaigns
• Set up Sites

Again, this is not meant to be a complete list. Also, it is not intended to be a how-to; for more information you may search the Help link at the top of every org page, check Salesforce Community, or Developer Force.

Happy configuring!