Salesforce.com

From Well Designed Urls WiKi

This page is used to discuss issues related to URL design at Saleforce.com.

Contents 1 About 2 Home Page 3 Url Structure 4 Configuring URLs

About

Salesforce.com offers software as a service (SaaS) for Customer Relationship Management (CRM) in which they are currently the market leader.

Home Page

http://www.salesforce.com

Url Structure

When I googled "Salesforce.com URL Structure" I didn't find anything that explained it so this is not exhaustive description. However, based on inspection, which I was obviously only able to do with my own Saleforce.com account and thus might not fully apply to others, it appears Saleforce.com's URLs work something like the following, assuming you are logged in to Saleforce.com:

Code	Mod	URL to Mod Home Page
001	Accounts	https://<SubDomain>.salesforce.com/001/o
003	Contacts	https://<SubDomain>.salesforce.com/003/o
006	Opportunities	https://<SubDomain>.salesforce.com/006/o
015	Documents	https://<SubDomain>.salesforce.com/015/o
500	Cases	https://<SubDomain>.salesforce.com/500/o
501	Solutions	https://<SubDomain>.salesforce.com/501/o
800	Contracts	https://<SubDomain>.salesforce.com/800/o
00O	Reports	https://<SubDomain>.salesforce.com/00O/o
00Q	Leads	https://<SubDomain>.salesforce.com/00Q/o
01Z	Dashboards	https://<SubDomain>.salesforce.com/01Z/o
a00	Custom Tabs(1)	https://<SubDomain>.salesforce.com/a00/o
a01	Products	https://<SubDomain>.salesforce.com/a01/o

(1) This is just for the first custom tab. Not sure about what happens we you create more.

For <SubDomain> it always appeared to be "na1" for "North American server #1". "emea" is used for European and Australian subscriptions.

Here are additional researched URLs for the following actions:

Action	URL to Execute Acction
View All Objects	https://<SubDomain>.salesforce.com/<Module>
View Object's Home	https://<SubDomain>.salesforce.com/<Module>/o
View Object	https://<SubDomain>.salesforce.com/<Module><ObjectID>
Add Object	https://<SubDomain>.salesforce.com/<Module>/e?retURL=<Previous>
Edit Object	https://<SubDomain>.salesforce.com/<Module><ObjectID>/e?retURL=<Previous>
Clone Object	https://<SubDomain>.salesforce.com/<Module><ObjectID>/e?retURL=<Previous>&clone=1
Add Related Task	https://<SubDomain>.salesforce.com/<Module>/e?retURL=<Previous>&who_id=<Module><ObjectID>

In the above table:

• The term "Object" in the Action column refers to a record/instance in a Module, i.e. an Account, a Lead, a Contact, etc.

• retURL will often start with "%2F" when viewed in your browser. %2F is just the hex-encoded equivalent of "/" that the browser performs automatically on such characters when found in URL parameters.

• <SubDomain> always seemed to be "na4" for these URLs, but your mileage may vary.

• <Module> refers to the three position alphanumeric from the first table (i.e. "003" for Contacts and "01Z" for Dashboards.)

• <ObjectID> refers to the internal ID that Saleforce.com maintains for every unique object in its system. If you ever use the Excel Connector for mass data updates you'll get to directly play with them.

• <Previous> refers to the previous domain-relative URL (i.e. starting with a "/" instead of "http://na4.salesforce.com/") to which Salesforce.com should return after the user completes the request action. If retURL is omitted, SaleForce.com returns to "/home/home.jsp".

• who_id refers to the Object to which the task should be associated, prefix with it's "Module" code from the first table.

There are a lot of other URLs in Salesforce.com, but they start breaking down in consistency and use different conventions for similar concepts as if different groups within Salesforce.com implemented them and they didn't have the foresight to coordinate on conventions. However, I think I've documented the most important URLs and with the above information you can probably grok any others on your own.

If you do end up figuring out any of the other URLs, please update this section and also if you would please consider posting a comment indicating which URL you documented with another link back here at the blog Thoughts On Salesforce.com where I initially documented Saleforce.com's URL structure.

Configuring URLs

Not Applicable