Escolar Documentos
Profissional Documentos
Cultura Documentos
Guide
December, 2009
Safe Harbor
Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation
may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such
uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com,
inc. could differ materially from the results expressed or implied by the forward-looking statements we
make. All statements other than statements of historical fact could be deemed forward-looking,
including any projections of subscriber growth, earnings, revenues, or other financial items and any
statements regarding strategies or plans of management for future operations, statements of belief, any
statements concerning new, planned, or upgraded services or technology developments and customer
contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with
developing and delivering new functionality for our service, our new business model, our past operating
losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our
Web hosting, breach of our security measures, the immature market in which we operate, our relatively
limited operating history, our ability to expand, retain, and motivate our employees and manage our
growth, new releases of our service and successful customer deployment, and utilization and selling to
larger enterprise customers. Further information on potential factors that could affect the financial
results of salesforce.com, inc. is included in our quarterly report on Form 10-Q filed on July 31, 2007
and in other filings with the Securities and Exchange Commission. These documents are available on
the SEC Filings section of the Investor Information section of our Web site.
Any unreleased services or features referenced in this or other press releases or public statements are
not currently available and may not be delivered on time or at all. Customers who purchase our
services should make the purchase decisions based upon features that are currently available.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking
statements.
Vendors
Resellers
Manufacturers YOU
Agencies
Different Platforms
Different Infrastructure
Different Standards
Different IT Teams
October, 2007
Setup > Customize > Salesforce to Salesforce One-click linkedIn style invitations Collaborate on business sensitive data
with customers, partners and suppliers
Leads
Opportunities
Accounts
Contacts
Tasks (Send Email, New Task, Open Activity, Activity History, Log a Call)
Any Custom Object
Product Catalog & Opportunity Products
Cases and Case Comments (public only)
Attachments
Email templates available once the Salesforce to Salesforce org preference is enabled
The templates can be customized and may include company logo, header etc (use html
format when creating email template)
The customized invitation email needs to have the Connection URL for the contact to
complete the invitation process
System Administrators and users with Modify All Data automatically have this permission
enabled
All other Salesforce profiles need to be given this permission by the Admin
Permission necessary to access the connections and templates tab
Permission necessary to send invitation, accept invitations and make any changes to
connections
Permission necessary to ‘mass share’ records using the ‘Forward to Connections’ list view
feature
Permission necessary to create ‘acceptproprietary
salesforce.com views’ onand
theconfidential
relevant objects – more details to follow..
5. Add the Connections tab for profiles with the Manage
Connections permission
External Sharing related list may be added to shared entity page layouts
• Do not add to layouts for user Profiles that shouldn’t be able to forward records
Ability to manually stop sharing record with a connection only available via this related list
• Best practice: do not include in portal page layouts
Individual Tasks & Opportunity Products may only be shared in this manner
Method to share any related record (e.g. Contact on shared Account record)
Received Connection column: shows name of connection that sent the record
Sent Connection column: pick one or more connections to forward the record
Customize by partner
type
Industry specific template
library
Apply to 1000s of new
invitations
Company A Company B
Free to send & accept invitations and share records (all editions including Group)
Only users with Manage Connections permission may send an invitation
Only contact with email address may be selected
Connection inherits applied templates Publish object/field rules
‘Invite to Connect’ option visible on the Contacts tab – list view action
Only users with Manage Connections permission will see this option
Option to apply active template to all new invitations
•Both sides may publish one or more standard and custom objects
•Pre-define Publish Object selection using Connection Templates
Ability to map other company’s picklist (multi-select) values to internal picklist values
Values not mapped, automatically come over during the insert/update
Assignment rules may be used with queues to mass share leads, cases and custom objects
A connection may be a member of one or more queues
Related records will not be shared when the parent is shared using
Only caveat is around Public Case Comments – these will be shared once the Case is accepted
Only ‘published’ fields will be sent (as defined by the connection detail)
Multiple connections may accept the record
Leads/Custom Objects/Cases: change ownership to queues with connections as members
User needs to have Edit CRUD on object and either be the Owner, Owner’s boss or System Administrator
Sharing the record does not remove visibility into record. Internal users continue to have full visibility
‘Forward to Connection’ option may be used to forward 1000s of records and child records
• Limit of 100 records per child entity
Only users with Manage Connections profile permission have this option
Only objects Published to and Subscribed by at least one connection will show up in the Related list
Tasks, Attachments and Opportunity Products can be shared using this option.
Only records owned by user or subordinates will be forwarded. System Admins can forward all records
Limit of 100 records per related object when the parent is forwarded manually (screen above)
Similar functionality available via the API. No sharing limits (e.g. Apex trigger on related record where
parent is already shared)
2 columns need to be
added to the related
list page layouts
**In exception cases when child records cannot be automatically accepted the user will need to
manually accept the record – ‘Parent Record Name’ in list view will show the parent relationship
Other subscribed fields come over during the next update (~2mins)
Only select fields available during acceptance (the rest come over during the first update, ~2mins)
• Account info (for new accounts): Account Name, Billing City, Billing State/Province and Billing Country
• Opportunity info: Name, Amount, Stage, Close Date
Acceptance only required if the record has been shared on its own (e.g. not as a child of the Account)
New with Spring ’10: Close Date, Name and Stage are no longer required to be subscribed. Additionally
these fields can now be mapped to other custom/standard date, text and picklist fields (respectively)
Only select fields available during acceptance (the rest come over during the first update,
~2mins)
• Person Account field is checked when incoming Account is of type Person Account.
• Account info (for new accounts): Account Name, Billing City, Billing State/Province, Billing Country & Account
Type
Only select fields available during acceptance (the rest come over during the first update, ~2mins)
• Account info (for new accounts): Account Name, Billing City, Billing State/Province and Billing Country
• Contact info: Name, Title, Mailing City/State/Country, Email, Phone
Acceptance only required if the Contact has been shared on its own (e.g. not as a child of the Account)
Share ‘Public’ comments • Cases and Case Comments can be Published and Subscribed
• Case required field (s): Subject
•Cases can be forwarded manually, by assigning to queue with
connection as member and/or using the API
•Public comments automatically shared with connected companies
if Comments are subscribed by target org
• Marking a comment ‘Private’ automatically terminates sharing
• Support for Escalation & Assignment rules
• Case History report has been modified to include Connections
• Additional reports can be built using CRT’s
“Show me Companies I’m “Show me Opportunity records “Show me custom object records
connected to” shared with connections” shared with connections”
New ‘connection’ column on lead, opportunity, account, contact, case and custom object history
related list (only covers fields tracked in history)
Updated history reports (leads, opportunities, account, contact, cases and any custom object)
Record Inserts: customers have the ability to bypass validation rules when a record is accepted by using
special connection criteria (see above)
Record Updates: use Connection User in validation criteria to ignore rules
Refer this blog for more details: http://blogs.salesforce.com/prm/2009/02/impact-of-sales.html
Blog highlighting step by step configuration of existing validation rules and apex triggers to avoid
errors can be found here: http://blogs.salesforce.com/prm/2009/02/impact-of-sales.html
Blog: http://sites.force.com/blogs/ideaList?c=09a30000000D9xo&category=For+Partners&sort=popular
S2S Website: http://www.salesforce.com/crm/partner-channel-management/partner-collaboration/