Enable OrchestraCMS Extensions
OrchestraCMS Extensions are additional content types and content templates that extend the capabilities of OrchestraCMS. The OrchestraCMS Extensions pack includes four page templates that are provided as samples for use with the additional content templates.
You will need access to three custom objects available in your Salesforce organization to support the Bookmarks, Content Anchors, and User Stories custom objects.
If you are using the Extensions pack along with the multilingual feature of OrchestraCMS, you can translate content into up to 20 languages and use all the multilingual functions of that release.
Requirements for Content Types
Some of the individual content types require specific Salesforce features to be available and enabled in your organization:
- The Salesforce Chatter content type requires Salesforce Chatter.
- The Salesforce Content content type requires Salesforce CRM Content (specifically Libraries).
- The Salesforce Dashboard content type requires Salesforce Dashboards.
- The Salesforce Ideas content type requires Salesforce Ideas.
For detailed information about each of these Salesforce features, see the Salesforce documentation.
Enable OrchestraCMS Extensions
OrchestraCMS Extensions are contained in a single managed package, and each content type within the package is a licensable feature.
Installation requirements
OrchestraCMS Extensions requires the following:
- OrchestraCMS Summer 2016 or later installed to your Salesforce organization.
- Three custom objects available in your Salesforce organization to support the Bookmarks, Content Anchors, and User Stories custom objects.
Install the OrchestraCMS Extensions package
After you purchase OrchestraCMS Extensions, you will be provided two links: one to install the managed package in a sandbox organization and one to install it in a production organization. We recommend installing the managed package and any updates to your sandbox environment first, which gives you an opportunity to test the features before rolling them out to your production organization.
OrchestraCMS Extensions contains three custom objects that count toward the custom object limit of your Salesforce organization.
Before you install the OrchestraCMS Extensions managed package, you should sign out of any instances of Salesforce that you currently have open. This will prevent the OrchestraCMS Extensions managed package from being installed in the wrong Salesforce environment.
Install OrchestraCMS Extensions to your Salesforce organization
- Click on the link you were provided, or copy and paste the link to your browser.
- Sign in to your Salesforce organization using a system administrator account.
- On the Package Installation Details page, click Continue.
- On Step 1. Approve Package API Access, click Next. Do not change any of the extended object permissions.
- On Step 2. Choose security level, set the security level for the package as required for your organization and click Next. Profile permissions can be manually changed after installation, but it is quicker to grant permissions during this step to avoid having to set individual permissions for each relevant profile.
- On Step 3. Install Package, click Install. When the installation process is complete, you will receive a confirmation email from Salesforce.
Visualforce permission sets
Visualforce pages need to be added to a permission set and assigned to users.
Visualforce pages for OrchestraCMS Extensions | |
|---|---|
ArticleGenerateDetail | ArticleGenerateDetailWithRelated |
ArticleGenerateSummary | ArticleGenerateSummarySmallWithImage |
BookmarkGenerateCurrentPage | BookmarkGenerateList |
CarouselEnhancedGenerate | |
GenerateSearchContentForm | GenerateSearchContentResults |
GoogleSearchGenerator | IdeasGenerateDetail |
IdeasGenerateListAll | IdeasGenerateListMy |
IdeasGeneratePost | RSSInboundGenerate |
SalesforceContentGenerateContentList | SalesforceContentGenerateLibraryList |
SalesforceContentGenerateSearchResults | SalesforceContentGenerateSelectList |
SalesforceDashboardGenerate | UserStoryGenerateApprovalsList |
UserStoryGenerateDetail | UserStoryGenerateSummaryList |
To create a new Permission set
- In Salesforce Setup, expand Manage Users.
- Click Permission Sets.
- Click New.
- Enter the permission set information. Enter the permission set name: OrchestraCMS Extensions. A license is not needed. Click Save.
- Under Apps, click Visualforce Page Access.
- Click Edit.
- Select each required Visualforce page (from the list, above) from Available Visualforce Pages on the left.
- Click on each and click Add to add it to Enabled Visualforce Pages on the right.
- Save.
Site Guest User permissions
The system administrator will need to apply permission sets for guest users in Salesforce.
On installation or upgrade, OrchestraCMS automatically generates ocms_SiteViewer, a permission set that is used to share with all guests in the organization.
If the guest user is not active but is activated later, and the administrator clicks on OrchestraCMS Site Details (under Setup), a message will appear to say the permission set doesn’t exist, or the guest user doesn’t have the required permission.
In that case, the “Validate Permissions” option should be used.
To validate permissions for a Site Guest User
- In OrchestraCMS Setup, under Site, click Details.
- Click Edit.
- Click Validate Permissions.
Set profile permissions and public access settings
There are object, field, and Visualforce page permissions that need to be added to the Salesforce profiles for OrchestraCMS users and site visitors. These could also be added to individual user accounts as a permission set.
The instructions in this section are based on the standard user interface for profiles. If your organization has the Enhanced Profile User Interface enabled, the procedures for setting permissions will be different, but the required permissions are the same.
The following table contains the required object and field permissions.
Custom object | Object permissions | Field permissions | Users that require permissions |
|---|---|---|---|
Bookmarks | Create, Read, Edit, Delete | All fields set to Visible* | OrchestraCMS users and site visitors |
Content Anchors | Create, Read, Edit, Delete | All fields set to Visible* | OrchestraCMS users and site visitors |
User Stories | Create, Read, Edit | All fields set to Visible* | OrchestraCMS users and site visitors |
The following table contains the required Visualforce page permissions. Although site visitors do not need access to all Visualforce pages (some are only used within OrchestraCMS), it can be easier to grant access to all Visualforce pages with the ocms_socfp namespace, because you can easily identify and select them all at once. There is no harm granting site users access to the additional pages if they do not have access to OrchestraCMS.
Visualforce page | Users who require access to the page |
|---|---|
ocms_socfp.ArticleGenerateDetail | OrchestraCMS users and site visitors |
ocms_socfp.ArticleGenerateDetailWithRelated | OrchestraCMS users and site visitors |
ocms_socfp.ArticleGenerateSummary | OrchestraCMS users and site visitors |
ocms_socfp.ArticleGenerateSummarySmallWithImage | OrchestraCMS users and site visitors |
ocms_socfp.BookmarkGenerateCurrentPage | OrchestraCMS users and site visitors |
ocms_socfp.BookmarkGenerateCustom | OrchestraCMS users and site visitors |
ocms_socfp.BookmarkGenerateList | OrchestraCMS users and site visitors |
ocms_socfp.CarouselEnhancedGenerate | OrchestraCMS users and site visitors |
ocms_socfp.GenerateChatterFeeds | OrchestraCMS users and site visitors |
ocms_socfp.GenerateChatterTrendingTopics | OrchestraCMS users and site visitors |
ocms_socfp.GeneratePeopleList | OrchestraCMS users and site visitors |
ocms_socfp.GenerateSearchContentForm | OrchestraCMS users and site visitors |
ocms_socfp.GenerateSearchContentResults | OrchestraCMS users and site visitors |
ocms_socfp.GoogleSearchGenerator | OrchestraCMS users and site visitors |
ocms_socfp.IdeasGenerateDetail | OrchestraCMS users and site visitors |
ocms_socfp.IdeasGenerateListAll | OrchestraCMS users and site visitors |
ocms_socfp.IdeasGenerateListMy | OrchestraCMS users and site visitors |
ocms_socfp.IdeasGeneratePost | OrchestraCMS users and site visitors |
ocms_socfp.LanguageDispatchAjax | OrchestraCMS users and site visitors |
ocms_socfp.LanguageDispatchGenerate | OrchestraCMS users and site visitors |
ocms_socfp.RSSInboundGenerate | OrchestraCMS users and site visitors |
ocms_socfp.SalesforceContentGenerateContentList | OrchestraCMS users and site visitors |
ocms_socfp.SalesforceContentGenerateLibraryList | OrchestraCMS users and site visitors |
ocms_socfp.SalesforceContentGenerateSearchResults | OrchestraCMS users and site visitors |
ocms_socfp.SalesforceContentGenerateSelectList | OrchestraCMS users and site visitors |
ocms_socfp.SalesforceDashboardGenerate | OrchestraCMS users and site visitors |
ocms_socfp.SearchContentAjax | OrchestraCMS users and site visitors |
ocms_socfp.UserStoryGenerateApprovalsList | OrchestraCMS users and site visitors |
ocms_socfp.UserStoryGenerateDetail | OrchestraCMS users and site visitors |
ocms_socfp.UserStoryGenerateSummaryList | OrchestraCMS users and site visitors |
ocms_socfp.ArticleEdit | OrchestraCMS users |
ocms_socfp.BookmarkEdit | OrchestraCMS users |
ocms_socfp.BookmarkListEdit | OrchestraCMS users |
ocms_socfp.CarouselEnhancedEdit | OrchestraCMS users |
ocms_socfp.EditChatterFeedContent | OrchestraCMS users |
ocms_socfp.EditChatterTopicFeeds | OrchestraCMS users |
ocms_socfp.EditChatterTrendingTopicsContent | OrchestraCMS users |
ocms_socfp.EditContentChatter | OrchestraCMS users |
ocms_socfp.EditPeopleList | OrchestraCMS users |
ocms_socfp.GoogleSearchEdit | OrchestraCMS users |
ocms_socfp.IdeasEditDetail | OrchestraCMS users |
ocms_socfp.IdeasEditListAll | OrchestraCMS users |
ocms_socfp.IdeasEditListMy | OrchestraCMS users |
ocms_socfp.IdeasEditPost | OrchestraCMS users |
ocms_socfp.LanguageDispatchEdit | OrchestraCMS users |
ocms_socfp.RSSInboundEdit | OrchestraCMS users |
ocms_socfp.RecordListEdit | OrchestraCMS users |
ocms_socfp.RecordListSimpleDetailEdit | OrchestraCMS users |
ocms_socfp.SalesforceContentEditContentList | OrchestraCMS users |
ocms_socfp.SalesforceContentEditLibraryList | OrchestraCMS users |
ocms_socfp.SalesforceContentEditSelectList | OrchestraCMS users |
ocms_socfp.SalesforceDashboardEdit | OrchestraCMS users |
ocms_socfp.SearchContentEdit | OrchestraCMS users |
ocms_socfp.UserStoryEditApprovalsList | OrchestraCMS users |
ocms_socfp.UserStoryEditDetail | OrchestraCMS users |
ocms_socfp.UserStoryEditSummaryList | OrchestraCMS users |
Custom object and Visualforce page permissions can only be added to Salesforce custom profiles.
Add OrchestraCMS Extensions permissions to a custom profile
- In Salesforce Setup, under Manage Users, click Profiles, and then click Edit next to the relevant profile name.
- Under Custom Object Permissions, set the following permissions for the OrchestraCMS Extensions objects:
- Bookmarks: Read, Create, Edit, Delete
- Content Anchors: Read, Create, Edit, Delete
- User Stories: Read, Create, Edit
- Click Save.
- Scroll down to the Field-Level Security area, and click View beside Bookmark.
- Click Edit, and then click to select Visible for every field that does not currently have it selected.
- Click Save, and then click Back to Profile.
- Repeat steps 4–6 for the Content Anchor and User Story objects.
- Scroll down to the Enabled Visualforce Page Access area, and click Edit.
- In the Available Visualforce Pages list, do one of the following:
- Select all of the Visualforce pages with the ocms.socfp namespace, and then click Add. This is the required option for profiles associated with OrchestraCMS users, but it can also be used for site visitors to simplify the process of assigning permissions.
- Select only the required Visualforce pages as shown in the previous table, and then click Add. This option is only available for site visitor profiles and assigns only the specific pages they require.
- Click Save.
Permissions for public site visitors (non-authenticated users) must be configured through your site’s public access settings. Keep in mind that most OrchestraCMS Extensions are not Enableintended for public websites and are specifically designed for intranets, communities, and portals. Because of this, public site visitors do not need access to the three custom objects.
Configure public access settings for your site
- In Salesforce Setup, under Develop, click Sites.
- On the Sites page, under the Site Label column, click the name of the site that will use OrchestraCMS Extensions.
- On the Site Detail page, click Public Access Settings.
- Scroll down to the Enabled Visualforce Page Access area, and click Edit.
- In the Available Visualforce Pages list, do one of the following:
- Select all of the Visualforce pages with the ocms.socfp namespace, and then click Add. Site visitors do not require access to all Visualforce pages, but this method can be used to simplify the process of assigning permissions.
- Select only the required Visualforce pages as shown in the previous table, and then click Add. This option assigns only the specific pages that site visitors require.
- Click Save.
View and install feature licenses
The OrchestraCMS Extensions license appears under the Feature Licenses section of the Manage Licenses page in OrchestraCMS Setup.
If you do not see OrchestraCMS Extensions listed as a feature license after you have purchased it, you can manually sync your instance of OrchestraCMS with the OrchestraCMS license server. This typically occurs automatically.
Perform a manual license sync
- In OrchestraCMS Setup, under Site, click Licenses.
- On the Licenses page, click Check Now.
The OrchestraCMS Extensions pack is displayed differently than other feature licenses, because individual feature licenses for specific content types are contained within it. When you install or upgrade OrchestraCMS Extensions, you are provided with a 30-day trial of the individual features that you have not purchased. This means that some individual features might have different expiration dates than others; this can also happen if you purchase individual features on different dates.
Individual features must be installed after the license is active in your organization. You can do this from the license detail page. As an OrchestraCMS administrator, you might choose to not install, or install and subsequently limit OrchestraCMS profile permissions, for the individual features that have not been purchased and are on a 30-day trial.
View and install individual feature licenses
- In OrchestraCMS Setup, under Site, click Licenses.
- Under Feature Licenses, next to OrchestraCMS Extensions, click License Detail.
- To install individual features, do one of the following:
- To install all features that aren’t currently installed, click Install All.
- To install an individual feature, click Install in the row of the feature.
- Click Back to return to the Licenses page.
After a feature is installed, it appears in the Custom Content Types area of the Content Types page in OrchestraCMS Setup.
If any of your OrchestraCMS Extensions licenses expire, the content types will be marked with an expired icon in the Custom Content Types list.
When this occurs, the associated content templates are no longer available to create new content or edit existing content.
Provide OrchestraCMS profiles access to new content types
When new content types are created—either by installing the OrchestraCMS Extensions pack or by creating a custom content type—all OrchestraCMS profiles other than the OrchestraCMS System Administrator profile must be updated to grant access to the new content types.
To provide OrchestraCMS profiles with access to new content types
- In OrchestraCMS Setup, under Site, click Profiles.
- On the Profiles page, click Edit next to the profile you want to update.
- When the edit page is opened, the Content Permissions section is automatically updated to provide access to the new content types; modify the Create, Edit, and Publish permissions as necessary to meet your requirements.
- Click Save.
Users assigned to the OrchestraCMS System Administrator profile automatically obtain access to the new content types without having to update their profile. All other profiles require, at minimum, the profile to be opened and re-saved in OrchestraCMS Setup.