3. USING PARTNER COMMUNITIES
TO ENHANCE ECONOMIC
DEVELOPMENT
Learn about Wisconsin Economic
Development Corporation’s vision to
maximize economic and workforce
development effectiveness throughout
Wisconsin using Partner Communities.
#MWD14
5. Safe Harbor Statement
A Salesforce Admin
is safe in the office,
but that is not what
a User Group was
built for … so get
involved!
#MWD14
6. What is WEDC?
The Wisconsin Economic Development Corporation (WEDC) is a
public-private corporation created in 2011 as a result of a
bipartisan study that clearly indicated Wisconsin needed to
take a bolder approach to attracting, growing and retaining
businesses within the state.
It’s mission is to elevate the Wisconsin economy to be the best
in the world by providing a positive business climate, world-class
support services and economic development tools to accelerate
business start-up, attraction and growth.
#MWD14
7. Where a business finds help …
• Companies doing business
in Wisconsin have access to
numerous economic
development resources.
• While options are great,
coordination and
collaboration lead to
greater success.
#MWD14
8. The Vision
• In the Past: Everyone did their own thing
▫ 650+ economic development organizations across Wisconsin
▫ Difficult to coordinate initiatives across organizations
▫ Led to “silo” effect
• Vision: The In Force Network
• Utilize WEDC’s existing Salesforce investment to build a customized CRM system
• Develop with input from economic developers
• Preserve confidential business and operational data
• Provide collaboration between organizations
• Integrate with other data sets (Skills Wisconsin integration)
• Need to “sell” to partners already using their own system
• Partnered with Acumen Solutions
#MWD14
9. Architecture Options Considered
• Partner Communities
▫ Simple integration. Just “like” using Salesforce.
• Direct Access (Full Salesforce licenses)
▫ Requires significant configuration and maintenance costs.
• Salesforce-to-Salesforce Integration
▫ Applies to orgs already using Salesforce and have resources to manage.
• Customer Communities
▫ Functionality too limited for partners.
• Authenticated Sites
▫ Expected to go away as Communities adoption increases and matures
• Customer/Partner Portals
▫ Offers less functionality than Community based options.
#MWD14
10. Why Partner Communities
• Salesforce Communities
▫ Online platform that enables collaboration between WEDC and partners
▫ Can create fully-branded communities that connect members directly with each
other – and with relevant content, data and business processes
• Social Collaboration
▫ Members can interact, collaborate and form groups to support their interests
• Branding/Customization
▫ Companies can design their community to match their brand and website look
and feel
▫ Content and navigation structure is highly customizable
• Mobility
▫ Members can access the community from any device, anywhere
• Security & scalability
▫ Leveraging the trusted Salesforce platform, all data and member information is
always safe -- no matter how many members you have
#MWD14
11. Partner Community FeaturesCustomer Portal –
Enterprise Admin
Customer Community Partner Community
Accounts/Contacts ✔ Read & Edit only ✔
Leads & Opportunities** ✔
Q&A, Ideas & Knowledge ✔ ✔ ✔
Cases & Assets ✔ ✔ ✔
Custom Objects 10 10 10
Profile, People, Groups, Feeds & Files ✔ ✔ ✔
Site.com pages ✔ ✔ ✔
Mobile (Touch Browser) ✔ ✔
Role Based - user limit & complex
sharing
✔ ✔
Email & Delegated Admin ✔ ✔
Reports & Dashboards * ✔ ✔
Content Libraries ✔ ✔
Scalability 300K Millions 300K
12. Under the In Force Network Hood
• Standard Objects
▫ Accounts, Contacts, Opportunities, Activities,
Leads, Cases, Reports, Dashboards, Chatter
• Custom Objects
▫ Business Retention and Expansion Survey
▫ Investor Relations
#MWD14
14. Community Challenges
• Limitations of Community product
1. No Campaign support
2. Users can view but not create Reports
3. Users can not create List Views
4. Limited number of custom objects (20*)
5. Emerging market for AppExchange that work
with Communities
#MWD14
15. Lessons Learned
• Required a thorough review of existing platform security
to accommodate Internal vs. Partner users
▫ Changes to Org Wide Settings, Sharing Settings, and visibility to
Reports folders and List Views
• Modification of master-detail relationship on many
existing fields to set Detail object security
• Partner users want to maintain ownership of data
• Global Header need for Internal user access to In Force
Network, including Chatter groups
#MWD14
16. Skills Wisconsin Integration
Partner’s initiatives that matches qualified workers with
available jobs throughout the state.
• Field mapping exercise to identify data to be shared
• Purchased Informatica to create “Salesforce to
Salesforce” integration
• Sharing Accounts, Contacts, Opportunities, and custom
objects
• Not merging data. Creating copies with Read-Only access.
• Record Types to separate WEDC from SkillsWI data
#MWD14
17. Future of the In Force Network
• Grow user base
• Continue customization
• Increase functionality
• Create more customizable reports
#MWD14
