Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Follow these steps to set up GoMeddo in a Salesforce Digital Experience

Step-by-step guide

  1. Set up you Salesforce Experience (former communities): https://resources.docs.salesforce.com/212/latest/en-us/sfdc/pdf/communities_dev.pdf

  2. Once created, go to Setup and search for Digital Experiences

  3. Next to the community you created, click Builder

  4. Add a GoMeddo Lightning Web Component to the page where you want to expose the calendar


  5. Set the appropriate GoMeddo objects External Sharing Model according to your organisation's needs: GoMeddo Community Sharing Settings

  6. Assign the a GoMeddo license and permission set to your community users: Assign Licenses & Permission Sets

  7. Enjoy your GoMeddo Community!

The LWR Experience Cloud templates do not work GoMeddo. As to some existing Salesforce limitations at the moment. See this link to read about the Lightning web security limitations https://developer.salesforce.com/docs/atlas.en-us.exp_cloud_lwr.meta/exp_cloud_lwr/template_limitations.htm.

Licencing

Our recommendation is to put in place Salesforce Community Plus licenses (or Partner licenses). Basic Community licenses will cause problems with access, as every Community user only has access to records from custom objects that have a lookup to their Account or Contact record. In most cases, every Community user needs access to all GoMeddo Resources based on their availability. This means Resources need to be publicly accessible and thus shared with everyone. This in turn means the organization-wide sharing setting need to be set to Public Read/Write. Unfortunately this is not possible with sharing sets (which are used with basic Community users) as per the documentation:

The Available Objects list excludes: 

  • Objects with an organization-wide sharing setting of Public Read/Write 

  • Custom objects that don’t have an account or contact lookup field

This means if we set the Resource object to Public Read/Write, it will not be accessible to Community users when using Sharing Sets (which come with basic Community licenses). Community Plus licenses have full access to the Salesforce sharing model and will not cause this issue.

Related issues

  • No labels