Introduction

Forcivity’s Component Pack for Lightning Communities gives you the ability to create impactful experiences for your Lightning App Builder and Community Builder pages with clicks, not code.

Before you Install – Organization Requirements

NOTE: The following items must be present before installation.

 

  1. Communities must be enabled in your org
    Setup / Communities / All Communities
  2. You must have chatter enabled
    Setup / Chatter / Chatter Settings
  3. You must have my domain set
    Setup / My Domain
  4. Content Delivery feature should be enabled
    This allows an optimized web-based version of Microsoft Powerpoint and Word documents.
    Setup / Content Deliveries and Public Links

Installation

Focivity’s Community Component Pack can be installed through the AppExchange in a matter of minutes with very little added configuration using the Force.com standard installation process. Note: Review the organization requirements above prior to install.

  1.  During installation, determine who should have access to the Component Pack for Lightning by simply selecting either Full Access or No Access for each profile in the list.
    -OR-
    You can elect to install the Component Pack for Lightning for Admins Only.
  2. The Component Pack for Lightning will automatically install into your Salesforce.com organization in a matter of minutes.
  3. Once the installation is complete, simply click ‘Done’ to return to Salesforce.com.
  4. Assign additional admin users to a permission set (see below).

Community Users and Guests Component Access

Configure the following so users and guests (public access) have access to Forcivity components:

  • Profile / Object Settings / Forcivity Components / Read and View All
  • Profile / Object Settings / Forcivity Welcome Mat Trackers / Read and View All
  • The Sharing Settings / Default External Access for Forcivity Component and Forcivity Welcome Mat tracker should be Public Read Only

NOTE: The View All requirement is new for Salesforce Summer 20.

Creating and Configuring Components

Add users to this permission set who need to be able to add and edit components. This permission set is available in Version 3.6 and higher.

Permission set: Forcivity Component Pack Admin
Description: Add admin users to give them access the Forcivity’s Component Pack for Lightning Communities app so they can create and edit components.
Assigned Apps: fcComp.Forcivity (fcComp__Forcivity)

Apex Class Access
All Apex classes within your Namespace Prefix (e.g., fcCom):

  • All files that start with <Namespace Prefix>.fc
  • <Namespace Prefix>.ForcivityExceptionData
  • <Namespace Prefix>.ForcivityExceptionData_Test
  • <Namespace Prefix>.RSS
  • <Namespace Prefix>.RSS_Test

System permissions: Access Libraries

Custom Setting Definitions
fcCom.Help Welcome Mat

Tabs
Within Permission sets, under the Object Settings add Tab Access (Available and Visible) for Admin and Component Pack.

Creating and Configuring Components

While most of the components within the Component Pack for Lightning are just drag and drop, the following components need additional configuration work.

  • Changes made to configurations immediately update the component when the component is saved. That is why we recommend testing changes in a sandbox and deploying the changes.
  • Blank fields are not shown unless a value is entered.
  • Best practice for URL links is to use relative links (e.g., /s/support) from community pages so you can move configurations between orgs. If you are linking to an external site, use an absolute link and open in a new window.

Lightning App Builder and Experience Builder

Use the configurations to drive the community components:

  • Once you drop the component on the page, you then can select the configuration.
  • If you make changes to the configuration, just refresh the page.
  • Configurations are re-usable with the Lightning App Builder or Experience Builder.

Testing and Deploying Components

While most of the components within the Component Pack for Lightning are just drag and drop, the following components need additional configuration work.

  • Use a sandbox to test your component configurations.
  • When deploying, the community pages can be deployed via a changeset.
  • The component configurations can be exported and then imported into your production org.

Additional Resources