Component Pack for Lightning Quick Start

Click. Drag. Done.

Product Information

Release Notes

Slider

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.

NOTE: The following items must be present before installing the Component Pack for Lightning Communities.

  • Communities must be enabled in your org (Setup / Communities / All Communities).
  • You must have chatter enabled (Setup / Chatter / Chatter Settings).
  • You must have my domain set (Setup / My Domain).

How the Component Pack for Lightning Works

Once installed, the new components are available within the Lightning App Builder and Community Builder under the Custom Components list.

  1. Open the page to edit in Lightning App Builder or Community Builder.
  2. Select the from the Custom Component list.
  3. Configure the component using the attribute panel.
  4. Preview your changes.
  5. Publish the community.

It’s that simple.

Installation

Focivity’s Community Component Pack can be installed through the AppExchange in a matter of minutes with very little added configuration needed.

Like any other native Force.com application, the Component Pack for Lightning uses the Force.com standard installation process.

You can try the Component Pack for Lightning for 30 days. Just enter your information and you will not be billed until your trial is complete. You can manage this subscription with the AppExchange under your subscriptions. Pricing is based on company, not users.

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 permission set to users (see below)

Sandbox refreshes
All Component Pack for Lightning settings will persist across a Sandbox refresh. There are no added steps needed to configure the Component Pack for Lightning to work in your Sandbox.

Back to top

Visibility to the Components

User access to Forcivity Component Pack components

Configure the community so users and guests (public access) have access to Forcivity components.

Profiles for all users who need access to the Component Pack for Lightning:

  • Profile / Object Settings / Forcivity Components / Read
  • Profile / Object Settings / Forcivity Welcome Mat Trackers / Read
  • The Sharing Settings / Default External Access for Forcivity Component and Forcivity Welcome Mat tracker should be Public Read Only
Admin user access to Forcivity Component Pack application

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 users to give them access to Forcivity’s Component Pack for Lightning Communities
Adds the following permissions:

Assigned Apps: fcComp.Forcivity (fcComp__Forcivity)

Object nameObject PermissionsTable FieldsTab Settings
Forcivity ComponentsRead, Create, Edit,
Delete
8Visible
Forcivity Welcome Mat
Trackers
Read, Create, Edit,
Delete
7

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.

Configuration Notes:

  • Configurations changes are shown dynamically within the preview window.
  • 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.
  • Images need to be added to a changeset (Asset Files) when deploying to another org (production site).
  • Images are stored within the Asset Library under Libraries.
  • Blank fields are not shown unless a value is entered.
  • Best practice 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.

Images and Libraries

Certain components (Hero, Two Column with Image, Tiles) use images. These images are stored in the Files / Asset Library.

  • You can reuse images already stored in your Files / Asset Library folder.
  • Ensure you can add a folder in the Asset Library. We recommend creating a folder (e.g., Community Components) to make these files easier to manage.
  • Ensure you have public file sharing enabled and you have set your library member permissions appropriately. Note: If you use a Library_Adminstrator role for your library members, make sure you have reviewed that role’s rights (this can only be done Classic, and search for Content Permissions).

Lightning App Builder and Community Builder

Use the configurations to drive the community components.

  • All the Component Pack for Lightning components are located under the Custom Component section under the Components tab.
  • 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 Community Builder.
  • Each component has top and bottom margin setting to better help to align your components.

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.

Testing

  • 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.
  • For more details, see Deploying Community Changes.

Additional Resources

Back to top

Need Help?

Have an issue or question with one of our products?