Bridgeline Digital Logo
Menu

Use Lightning components

With the Salesforce Lightning solution, OrchestraCMS becomes a repository for all your content, but does not allow for the creation of pages, because the pages are already built into the Lightning solution.

There is no migration path from the traditional use of OrchestraCMS (using Salesforce Visualforce pages) to the Lightning Solution. You can use one or the other. If you switch to Lightning, you won't be able to switch back easily to the Visualforce solution without re-creating everything (page templates and much of the content).

However, the Lightning Solution is much easier to configure than the Visualforce Solution.

Once OrchestraCMS is installed into Salesforce, it can be linked to any new or existing Salesforce Community. For more information, see Create Communities in Salesforce.

To install a Community site in OrchestraCMS

  1. In the OrchestraCMS main header, click Create New Site.
  2. Click Salesforce Site.
  3. Click Install. OrchestraCMS opens configured as a potential content repository for Lightning Communities.
  4. In OrchestraCMS, click Details.
  5. Click Edit.
  6. Copy and paste the URL of your site domain into the Site Secure Domain field.
  7. Copy and paste the Site URL into the Site Secure URL field. Change "https:" in the Site URL to "http:". In both fields, remove the slash at the end of the URL.
  • Further options in Details are not needed.

OrchestraCMS sections to use (and not use) with Lightning

In OrchestraCMS setup, these sections are relevant to the Lightning solution:

  • Licenses
  • Priority Levels
  • Profiles (but only the OrchestraCMS Author user license is needed; the Editor profile, which supports page permissions, is not relevant. (With Lightning, no page information is needed for your OrchestraCMS solution.)
  • Overture
    • Scheduler [to be confirmed]
  • Languages
  • Translation Groups
  • Targets
  • Content Types
  • Content Templates
  • Platform Cache (but not the Page version index)
  • Content Cache
  • Unlock (Content only)
  • Manage Libraries
  • Tags
  • Approval Process

In OrchestraCMS Setup, these sections are not relevant to Lightning:

  • Non-OrchestraCMS pages
  • Search Index
  • Remote Sites
  • Page Templates
  • Page Cache
  • Customer Community
  • Error Pages

In OrchestraCMS Manage Site, these sections are not relevant to Lightning:

  • Pages tab
  • Site Map
  • Recent Pages
  • Create New Page Wizard
  • Page Search
  • Full Preview
  • Time Travel
 

Live Site is used with Lightning.

How to use Salesforce Community Builder

This is where you will find all page management features, including, but not limited to, layouts, URLs, and styles. All are handled through Community Builder.

To access Community Builder for use with OrchestraCMS

  1. On Community Workspaces in Salesforce, under My Workspaces in your new Community, click Builder.
    • Alternatively, in Salesforce Setup, All Communities, click Builder next to the community you want to access.
  2. In the left corner of the Community Builder page, click the lightning bolt symbol to open the Component panel.
    • This reveals a list of five OrchestraCMS Lightning components that you can drag onto your page. Each has properties to configure.
 

Your solution might contain more components than those covered here.

OrchestraCMS Lightning components

Following is a description of the components and what they can do.

Dynamic Content Loader OrchestraCMS

This component, dragged to the page, allows you to load groups of content by content type and template.

  • You can also use taxonomy categories to further filter the content loaded.
  • Only one content type can be set per loader, but you can have more than one loader on a page.  

Fill in the properties field for the information relating to the taxonomies you'd like to use.  

  • The red asterisk is a reminder that this field needs to be filled in.
  • Select the Content Type.
  • Select the Content Template.
  • Select the Sort Order (Original Publish Date, Alphabetical, Priority Publish Date, or Published Start Date).
    • Original Publish Date renders the publish date of Version 1.
    • Priority Publish Date needs to be set in OrchestraCMS Properties You can set different priorities to control the order. (For example, an item with a priority of 1 shows up before and item with a priority of 2; but an item with a priority of 2 shows up before an item with no priority.)
  • Configure the Display Content Detail field so the content appears as a Modal Dialog Window, Inline, On an SObject Detail Page, or On a Custom Detail Page.
  • Fill in the Custom Detail Page URL field.

Dynamic Content Viewer OrchestraCMS

When you drag this component to the page, it becomes a placeholder for selected content detail on a content detail page according to the way you have configured it in the Dynamic Content Loader.

Search Results OrchestraCMS

Add this component to your Search page in Community Builder to return results for your searches that include a specific type of OrchestraCMS content. More than one Search Results component can be used on the same page, so you can include multiple types of OrchestraCMS content — one component for each type of content you want to return.

  • In the Properties panel, give your search results a name.
    • As with other properties, the small red asterisk is a reminder that this field needs to be filled in.

  • Leave the Search Term field as it is.
  • Select the specific content type you want to search (for example, Text) and the Content Template to display.
  • In the "Number of Results" field, state how many results you would like to display at first. This number will also determine how many results you will see when you click More Results.
  • Pre-defined targets (not ad hoc) are created in OrchestraCMS, but, as in other properties, you can click Ignore Targets if you wish everyone to see the content irrespective of the targets set on that piece of content.
  • As in other Properties, you can leave the name of the site blank if you are using the same site. If not, use the dropdown menu to select another one.

Static Content OrchestraCMS

This exposes a single piece of OrchestraCMS content. Drag this component onto the page. (You can create the content on the page or within OrchestraCMS.)

  • Fill in the properties field for the information you'd like to display.
  • The small red asterisk is a reminder that this field needs to be filled in.
  • Content Name: If the content already exists, this is the name of the existing content.
    • If it does not exist, you will be prompted to create the content if Enable Edit Mode is also selected.
    • If it does not exist and Enable Edit Mode is not selected, you will get an error message.
  • Determine the content template.
  • Pre-defined targets (not ad hoc) are created in OrchestraCMS, but, as in other Properties, you can click Ignore Targets if you wish everyone to see the content irrespective of the targets set on that piece of content.
  • Click Display Likes for an interactive response from readers.
  • Click Display Chatter Comments if you would like to reveal what your readers have to say about the content.
  • Optionally, give your content a heading.
  • You can leave the OrchestraCMS Site Name blank if you are using the same site. If not, use the dropdown menu to select another one.
  • If you would like to allow content authors to edit, change, or create new content, click Enable Edit Mode.

To create content on the page (once Enable Edit Mode has been selected)

  • In Preview or on the live site, any user who is logged in and who belongs to an OrchestraCMS Profile (with the proper content authoring permissions) has the controls to create content.
  • When the appropriate user selects the Document or Rich Text section, a new window opens with a place for creating text and the OrchestraCMS Rich Text Editor.
    • A new feature in the Rich Text Editor allows you to insert a Youtube, Vimeo or Daily Motion video.
  • When selected, the footer symbols at the bottom of the "Create Content" section can be used to toggle Properties, Targets, Preview, and Publish; or to apply taxonomy categories with the Content Loader.

  • When you have finished, you can click Delete Draft or click Save and Continue or Publish .

Edit or Expire content

  • To expire a piece of content, click Preview and then click the small arrow in the content to display a small dropdown menu. From here you can expire or delete.
  • The expired content will disappear in Salesforce, but not in OrchestraCMS. To restore the content, you will need to create a new version in OrchestraCMS.
  • The Edit option creates a new unpublished draft (the term in Salesforce Community Builder) or a new Version (the term used in OrchestraCMS).  
  • You can delete Salesforce (not OrchestraCMS) content in Salesforce by clicking the trashcan icon.

Taxonomy Menu OrchestraCMS

This component allows you to render any taxonomy as a menu.

For each taxonomy category, in Dynamic Content Loader properties, there is a field called Taxonomy Menu ID. This is the Identification name that will need to match one of the Taxonomy loaders. It is only used, however, if you have more than one loader or menu combination.

Enable Session Cache

When Session Cache is enabled, live site visitors can cache page content locally for faster subsequent load times. (Any new or updated content published during that session may not be visible.)

Performance can be improved on subsequent page hits and user interactions.

To cache content results locally in your browser:

  • On the Dynamic Content Loader/ Dynamic Content Viewer / Static Content Loader / Taxonomy Menu component configuration, select Enable Session Cache. 
    • The caches expire when the user's session ends (closing the tab or window).
    • With this option enabled, the components pull from the cache, if it is available, and skip the request to the server for content.
    • This can result in users seeing out of date content if a publish or update has been performed while they are browsing the site.

   

Enable Deep Linking

Deep linking updates the page URL so it can direct you to a piece of content or a page state. For example, if you have a Taxonomy menu and a Content loader, you could filter down to a desired taxonomy path to get the direct URL to that path.

Your site administrator has the option of selecting a check box to specify whether deep linking is on or off on a per-component basis.

When deep linking is available, you can navigate through a menu on a dynamic content loader and be able to bookmark or copy a URL link. When you use that bookmark or URL link, the page will display the state specified by the URL.

  • When you use an Inline Detail view, you can also bookmark or copy a URL link to a specific article. When you use that bookmark or link, the page will display the relevant article.