The Community Cloud is getting more and more popular among customers, it is pretty easy to set up and at the same time have some things which you need to be aware of. With a few implementations under my belt I feel that I can share a few things I learnt along the way.
15. Lightning Bolt is great but has limitations
15
● Navigation Menu items aren’t included
● Only default page variations are included. If a page doesn’t have
a default variation—for example, a page with two variations that
are both set to audience-based visibility—the page is excluded
entirely.
● Branding Editor properties and CSS customizations
● Localized content for multilingual communities
● Community Management settings
https://resources.docs.salesforce.com/206/latest/en-us/sfdc/pdf/community_templates.pdf
16. Winter ‘18 Will be Awesome
16
● New template - Customer Account Portal & Build your own
● Add website content from Drupal, Wordpress & others
● Dynamic branding based on audience
● Akamai integration and caching
● Community 360 for better support
● Unauthenticated communities even without licences for everyone!
18. Go and find for what you can use it.
Because you have something for sure!
18
Notes de l'éditeur
I did the community cloud consultant certification exam about a week after it was released. And from that moment I’m the “go to guy” with anything related communities. It is super easy is my usual answer.
Community Builder is about the same as App Builder
I like it for the narrower header, but included components are cool as well
Napili or Partner Central, in Winter we will get Customer Account Portal. Koa and Kokua being phased out.
They are nice already and super easy to customize, can you see they are all build on the same template?
Customer asked - how many different components are there?
There isn’t many components you can use on a page, but they are pretty flexible - richtext, html, list view, record details, chatter and a few more.
Forget complex sharing rules, apex sharing or roles - if we are speaking about the simple customer community. But sharing sets can be powerful as well and give you access to records which has something in common.
No way to publish to community chatter from process builder, use flow
Not all components are available for all communities types, don’t be surprised
No way to publish to community chatter from process builder, use flow
Not all components are available for all communities types, don’t be surprised
Look at components on appexchange - they might not support communities (as the RSS one), but you can always include that component in your own, which can run on communities.
Look at components on appexchange - they might not support communities (as the RSS one), but you can always include that component in your own, which can run on communities.
Like packages for communities, just add name, category and some pictures and click export
Then add it to your package - even in managed package it is possible to change everything in community based on specific template - it is a template after all.
It isn’t perfect - default views are not transferred and some other things doesn’t work as well
The summer release was great, the winter looks even better. Salesforce really pushes this thing, so it is great time to jump on the wave and ride
Most customers don’t think about Salesforce Communities because they don’t want to build a community. Don’t think about it this way, about social network, place where people will interact. Use it just for publishing things at first, the interaction might come later.
And Salesforce might give you a great price. Go for it.