About the Salesforce and Aurora integration
The "Khoros Connector for Salesforce" enables you to create a tight integration between your Khoros Community Aurora content, Salesforce content, and Salesforce cases. For more information on setting up this integration, contact Khoros Services. Note: You must have a full Salesforce license to take advantage of the Khoros/Salesforce integration. The following are the key features of the Aurora and Salesforce integration: Automatically escalateunanswered threads toSalesforcecases Manually escalate threadstoSalesforce cases Provide a private support case portal to their community members View community member details and statistics within Salesforce Use enhancedfederated searchacross Aurora and Salesforce content Link Salesforce and Khoros Community Aurora content viapostbackfrom Salesforce to the community Before you start Decide on your target Salesforce environment. Khoros strongly recommends that you first enable the integration in a Salesforce developer or sandbox org before deploying the integration to your production environment. Make sure you have your Salesforce integration enabled in the Aurora community environment that will connect to your Salesforce environment. Your Khoros Customer Success Manager can assist with this process. Khoros will enable the integration in your staging environment before enabling it in your production environment. Learn more about Installing and configuring your Khoros/Salesforce.com v3/v4 integration.Aurora: Install the Salesforce integration package
Khoros periodicallyreleases updates to theConnector for Salesforce package to introduce new features and address defects. Note:In addition to deploying the package to your Salesforce server, you need to activate the integration on your Khoros community before you can configure and use the integration. Contact Khoros Support for assistance with activating the integration on your community instance. This document explains the basic deploymentprocess for a new deployment of the Khoros Connector package to your Salesforce org. The process uses the standard Salesforcemethodology for deploying managedpackages from the AppExchange. To install the integration package for the first timein yourtarget Salesforce org: Download the appropriate package: Production Package Sandbox Package Click Get it Now. Select Install in productionor Install in sandboxandclick Confirm and Install. Select Install for All Users and click Install. In the Approve Third-Party Access window, select Yes, grant access to these third-party web sites and then click Continue. When the package is deployed, you can confirm it by going toSetup > Installed Packages: The Khoros Salesforce Integration app in the app navigation menu is located on the top-right corner of the Salesforce window:Aurora: Configure remote site access for your Salesforce integration
The Aurora/Salesforce integration must be able to access your Khoros community. Part of this integration involves mentioning community APIs in the allowed list so Salesforce doesn't block them. To configure remote site access: In your Salesforce.com environment, go toSetup. Go toAdministration Setup > Security Controls > Remote Site Settings. By default, two Remote Site Settings with the NameSpace prefix "LiSFintegration" appear. For the Khoros (Lithium) setting, clickEdit. Enter theBase URLvalue according to your Khoros environment.Note:Be sure to include thehttps://and HT credentials. Use the following format: https://<HTUSER>:<HTPASSWORD>@<***Community URL> Example: https://test123:qwerty98765@community-stage.khoros.com/ Khoros Community Stage Base URL Sandbox https://[community_id].stage.lithium.com Production https://[community_id].lithium.com Note:Your Khoros Community Success Manager (CSM) can provide you with your Community ID. Note:If you have a more descriptive CNAME/vanity address for your community, use that name when creating the URL (for example,https://community.mycwebaddress.com). SelectDisable Protocol Security. (If you have HTTPS enabled, you can keep this setting enabled.) Salesforce.com expects data to be transmitted via HTTPS (a combination of HTTP and the SSL protocol). The Khoros/Salesforce.com integration talks to your community using its provided REST API, which is publicly available and is accessed via HTTP. ClickSave. ClickEditfor theSFSelfsetting and provide the Remote Site URL as your existing signed-in Salesforce URL (for example,https://na16.salesforce.com). ClickSave. Repeat steps 3 – 9 for your production community, replacing the name with something descriptive such as “Khoros community – Production” and the URL with the final URL for your production community (for example,https://community.mywebaddress.com). Note:You can also repeat this process to connect multiple Khoros communities to your Salesforce instance. For custom domains (Salesforce 3.9 or later): ClickNew Remote Site. EnterSFSelfInstancefor theRemote Site Name. Enter yourRemote Site URL(for example, "yourinstance.salesforce.com"). Enter aDescriptionfor this site. SelecttheActivecheckbox. ClickSave.Aurora: Configure custom Salesforce settings
The Khoros Community integration package leverages custom Salesforce settings, which are used by many components and relates to the Khoros Community configuration settings on Salesforce. To apply settings for your Khoros environment: Log in to your Salesforce.com environment. From the dropdown on the top right of the page,select App as "Khoros Salesforce Integration." Click the Custom Settings tab. Go to the Feature Settings tab and click Create. Enter the Feature Settings: Feature Setting Name:Default is "DefaultSetting." Do not change this setting, as it is non-editable in newer packages. Create New Contact record: Select this option to enable the creation of a new Contact during user sync if a Contact with the matching email ID is not present. During User Sync, Contact and Community users are linked together. The linkage is necessary for Case Portal functionality. (You must enable the Community User Trigger below for this setting to work.) Link Community User with Contacts: Select this option to allow linking of Community user and Contact during user synchronization, if a contact with same email ID already exists. The linkage is necessary for Case Portal functionality.(You must enable theCommunity User Triggerbelow for this setting to work.) Case closure:Select this option to allow automatic case closure when a comment on a post is accepted as solution on community.(You must enable theCaseTriggerbelow for this setting to work.) Max Allowed Private Message Subject Length:Sets the maximum length the Private Message subject (up to 43 characters). Max Allowed Private Message Body Length:Sets the maximum length the Private Message body. No of Federated Search Results from Salesforce:Limits the number of Federated Search results (appliesto Salesforce results only). Default value is 100(Package 4.1 onwards). Enable Community User Trigger:Select this option to enable Community User Trigger. This trigger runs on community user creation/update and links community users with contacts. This linkage is necessary for Case Portal and User Sync functionality. Enable Case Trigger:Turns on or offtriggers on cases, which synchronize case status changes with community and also mark a case as closed. Enable Case Comment Emails:ToggleCase Comment email on and off. (Package 3.7 onwards) (Optional) Fallback Community Username:Enter username of the Community user to which postbacks should fall back to when a Community user is not found corresponding to the email address of the user replying. This is also used in case of multiple users with the same email address. Entered Community user should be a valid value. (Package 4.0 onwards) Allow Case Comments for public Community Cases:Select this option to enable thecreation of Case Comment on Public Community Cases in Salesforce. (Comment does not sync to community.) If not selected, it does not allow case comment creation for public community cases in Salesforce. (Upcoming, Package 4.2 onwards) Note: The Enable Knowledge andLightning Knowledgeoptions must be turned off as they are not supported in the community. These options allow knowledge base articles to be created, updated, deleted, and searched from the community. Click Save. Configure your remote site access. Click the Community Settings tab and click Create. Enter the Community Settings: In the Community Id field, enter your community ID. (You can get your ID from your Customer Success Manager, if you don't have it. If you've already entered this information,clickEdit.) In theUsernamefield, enter the Khoros username to be used in Khoros API calls. Note:This user must be a non-SSO user with administrator permissions, and the email address for this user must be verified in the community.If an agent has an account on the target community that usesthe same email address as their Salesforce account, their personalcommunity user account is used as the author of the postback. We recommend that your brand's Salesforce agents create their own community accounts for this purpose. Enter the Khoros Password associated with above username. Enter the Base URLvalue according to your Khoros environment (see below).Note: Be sure to include thehttps://and HT credentials. Use the following format: https://<HTUSER>:<HTPASSWORD>@<***Community URL> Example: https://test123:qwerty98765@community-stage.khoros.com/ Select the Is Proxy Enabled? checkbox. Enter theContext Name.Set to “t5" unless your Community has a “Reverse Proxy” implementation in place, in which case, contact your Customer Success Manager or Khoros support and request the value oftapestry.context.namefrom your community config. Click Save. To set the maximum number of search results to be returned in the Federated Search component, go to the Feature Settingstab and set the No of Federated Search value. Click Save. With HT-Access turned off in the Khoros community: Khoros Community Stage Base URL Sandbox https:// [community_id].stage.lithium.com Production https:// [community_id].lithium.com Note: If you have a more descriptive CNAME/vanity address for your community, use that name when creating the URL (for example, https://community.mycwebaddress.com). With HT-Access turned on in the Khoros community: Note: Contact Support to get the ht-access credentials for your community. Khoros Community Stage Base URL [Example with community id as “abc”] Sandbox https://htusername:htpassword@abc.stage.lithium.com Production https://htusername:htpassword@abc.lithium.com Note: Contact yourCustomer Success Manager to get your Community ID.Aurora: Create a new Salesforce email service
After configuring thecustom Salesforce settingswith the help of Khoros Community integration package, you must: Create a new email service Create a new email address under email reply handler Disable workflows(for upgrades only) Important:If your community is connected to a Salesforce instance that has a namespace prefix, the Community config 'salesforce.api_namespace = <Namespace of org you are connected with>' needs to be updated. To have your namespace updated,open a Support ticket. Create a new email service In the Salesforce portal, go toSetup > Develop > Email Services. ClickNew Email Service. In theEmail Service Namefield, enter "Email Reply Handler.” Search and attach "EmailReplyHandler" in Apex Class. ForAccept attachments, selectNone. ClickSave. Create new email address under email reply handler In the Salesforce portal, go toSetup > Develop > Email Services. ClickEmail Reply Handler. SelectNew Email Address. ForEmail Address Name, enter "Default." For theEmail address, enteremail_reply_handler. Remove values fromAccept Email From. ClickSave. Disable workflows(for upgrades only) If you have upgraded the Salesforce Connector from a version lower than v4.2, all existing workflows for sending emails to Case contacts are moved to triggers. Since it is not possible to deactivate existing workflows via upgrades, you must do so manually. Go toSetup > Workflow rules > Mark below mentioned workflows as inactive. Notify customers (with access) on Case creation. Notify customers (with access) on Case status change. Notify customers (without access) on Case creation. Notify customers (without access) on Case status change. If this is not done, users will receive two email alerts for each case activity relating to case creation, case status updates, and case comments.Aurora: Add federated search component to the Salesforce sidebar
The Federated Search feature includes relevance search filters and contextual search results that enable Salesforce Customer Support Executives (CSEs) to make quicker and more effective customer query and issue resolutions. The features include: Search filters: You can filter search results by Posted Date and Case Status. Note: When performing a federated search, you can filter for results for up to 3 connected Khoros communities as described under Configure Custom Salesforce settings. Link search results to cases: While reviewing search results, CSEs might find a particular search item useful for resolving a case. CSEs can use the Link to Case option to associate a search result with a case thereby providing an existing solution or a helpful article/post be linked to the case. Improved handling of case interrupts: When Salesforce agents create new cases, they can now refer to existing content, which might help defer future cases or provide an already available solution. The Enhanced Federated Search reads the case info (subject, description) and shows content related to the case, sourcing information on similar Salesforce Cases, Salesforce KB articles, and Khoros Community posts. When agents find content related to the case, they can add it to the case as Related Content. Add Federated Search component to the Salesforce sidebar To take advantage of the Enhanced Federated Search, you must select the Khoros Home Page Layout for the System Administrator assignment and thenenable the Federated Search componentfor all other Salesforce pages. To add the search component to your Salesforce sidebar: In Salesforce, go to Setup > App Setup > Customize > Home > Home PageLayouts. Click Page Layout Assignment. Click Edit Assignment. Click System Administrator. Select Khoros (Lithium) Home Page Layout. Click Save. To make the Federated Search component persistent on all other Salesforce pages, you must enable it at Setup > App Setup > Customize > User Interface > Show Custom Sidebar Components on All Pages. When enabled, the Federated Search component displays on the left-side of the page, as shown here: Searches performed with the Salesforce Federated Search return results from all integrated repositories in a single search-results page. Note: Integrated repositories include Salesforce.com cases, solutions, and knowledge articles and Khoroscommunity content. Currently, the Salesforce API call limits you to searching 3 communities at one time. If you have more than three communities connected in your integration, you can select up to three of them at one time in the filter options shown above. Set the maximum number of results for theSalesforce federated searchcomponent Sign in toSalesforceas an Admin. Go toCustom Settings > Feature Settings. ClickEdit. In theNo of Federated Searchfield, set the maximum number of resultsto return. ClickSave.Aurora: Modify Contact, Case, Solution, and Account Page Layouts and set up Reporting Dashboards
After you’ve deployed the package, you must add its custom fields to your Contact, Case, and Solution page layouts. How you add these fields depends on your organization’s needs.Refer to the Salesforce.com documentation on administering page layouts. You can also use the fields within the package to create new reporting dashboards as needed. The Khoros Salesforce.com integration includes a default Dashboard Folder as a place to start, and this article provides overviews of the functionality of the included Dashboard components. Refer to the Salesforce.com documentation on creating and administering dashboards. Contact Page You can add one of these Salesforce.com Visualforce pages to your Contact page layout: Contact User Metrics (Component name: ContactUserMetrics): This Visualforce page provides message posts, logins, private messages sent—among other community metrics—for the community user identified by the Salesforce.com Contact. Contact User Details (Component name: ContactUserDetails): This Visualforce page displays the community user’s avatar, first and last names, rank, and roles. Contact User Message History(Component Name: ContactUserMessages): This Visualforce page displays two panels: a list of the messages most recently read by the community user and a list of the messages most recently posted by the community user. To access the Contact page in Salesforce: Go to Setup > App Setup > Customize > Contacts > Page Layouts > Contacts > Page Layouts > Page Layout Assignments. Click Edit Assignment. Click System Administrator and select Contact Layout-Community. Click Save. Note: This component makes up to 2 Khoros API calls each time a Contact record is viewed when there’s a related Community User. The package includes a default layout for the community User Object, which you may want to modify or apply different permissions to. Case Page For Case and Case Closed loop support, you need to add the component CaseThreadMessages (Visualforce Page) and Community Postback Comments related list to the Case page layout. Although you maychoose a different layout based on your requirements, we recommend using the sectional layout. Note: Federated Search is included as an inline page component on the Case Page. To access the Case page in Salesforce: Go to Setup > App Setup > Customize > Case > Page Layouts > Page Layout Assignment. Click Edit Assignment. Select System Administrator Profile. Select Case Layout - Community from the Page Layout to Use drop-down menu. Go toSetup > App Setup > Customize > Case > Page Layouts. Click Editnext to"CloseCaseLayouts" of the Case Close Page Layouts section. In the Quick Find search box, search for the "Postback Options" component. Drag and drop thePostback Options componentin the Case Details section. Click Save. To access the Closed Case page in Salesforce: Go to Setup > App Setup > Customize > Case > Page Layouts > Close Case Layout. Click Edit. In the Fields area, click Add Postback options. Click Save. Solution Page Here's the recommended layout for the Solution page: To access the Solution page in Salesforce: Go to Setup > App Setup > Customize > Solution >Page Layouts > Page Layout Assignments. Click Edit Assignment. Click System Administrator and select Solution Layout-Community. Click Save. Account Page To access theAccount page in Salesforce: Go toSetup > App Setup > Customize >Accounts > Page Layouts > Page Layout Assignments. ClickEdit Assignment. ClickSystem Administratorand selectAccountLayout-Community. ClickSave.Aurora: Grant Khoros Support access to your Salesforce instance
From time to time, Khoros Support may ask you to grant sign-in access in order to assist you with a question, issue, or request. This is so thatSupport can sign in to the application using your login information to troubleshoot and fix issues stemming from your inquiry. To grant sign-in access to your Salesforce instance: Click your username in the top menu. Select My Settings. Expand the Personalmenu in the left pane. Click Grant Account Login Access. Under Grant Access To list, find Khoros (Lithium) Support. Choose the expiry period for the access. Click Save. Sourced from Salesforce Knowledge Base.Read the sourceSalesforce article.Aurora: Understanding the Salesforce connector components and their entities
You can configure and customize the Khoros Salesforce Connector to your need using theobjects and entities described in this section. The following sections describe theobjects in the Salesforce package: AccountObject CaseObject Community Postback CommentObject Community User Object Contact Object Khoros Feature Settings Object Private Message Object Related ContentObject Solution Object Other Entities AccountObject The Account objectisthe parent object for contacts.This helps in the grouping of individual users for use in the "Supervisor view" in the Khoros Community.This object uses the “Account Layout – Community” page layout, which displays account-related information. CaseObject This section discusses the Caseobject and all the entities that are used with this component to create or modify page layouts, etc. Object Name: Case Purpose: This object stores case-related information that is created when either a post in the Khoros Community is escalated, or a private support case is created in the Case Portal. Type: Custom Object Page Layout:The “Case Layout - Community” page layout displays case-related information. Entities: The following table describes all the entities that can be used on the "Case Layout - Community” page layout: Entity name Type Purpose Name of the page layout where thisentity is used Agent Login Custom Field This field holds the login information about the agent. Case Page Layout Agent Comments Custom Field This field holds the comments of the agent. Case Page Layout Author Login Custom Field This field holds the login information of the author. Case Page Layout Agent Reason Custom Field This field holds the reason that the agent enters during case creation. Case Page Layout Last Case Comment Custom Field This field is used to store last comment added to a case. Case Page Layout Description RTE Custom Field Captures the rich text content (HTML)being fetched from Community Forums. Case Page Layout Community Tags Custom Field This field holds the list of tags that are attached to a case that is created using Khoros escalation. This is a semi-colon ";" separated list. Case Page Layout Community ID Custom Field This field holds the Khoros community id Case Page Layout Community URL Custom Field This field holds the URL of the Khoros Community message corresponding to the case. Case Page Layout Latest Reply Time Custom Field This field captures the time of the latest reply on a Case. Case Page Layout Latest Reply User Role Custom Field This field captures the role of the user who posted the latest reply for a Case. Case Page Layout Latest Reply User Rank Custom Field This field captures the rank of the user who posted the latest reply for a Case. Case Page Layout Postback Options Custom Field This picklist or dropdown menu holds the postback options for case closure. Case Page Layout Topic_UID Custom Field This field holds the Message UID from Khoros community. Case Page Layout Thread ID Custom Field This field holds the ID of the thread containing an escalated message. Case Page Layout Khoros User Replied Custom Field This flag is used to determine if a Khoros community user has replied to a case. Case Page Layout Community User Custom Field This lookup field holds the identity of the community user who posted the message associated with the case. Case Page Layout Message UID Custom Field This field holds the messaged UID of a message from the Khoros community. Case Page Layout Message Posted Custom Field This field holds the date and time information of an escalated message. Case Page Layout Board ID Custom Field This field holds the Board ID of the Khoros community board containing the escalated post or message. Case Page Layout Author Rank Custom Field This field holds the rank information of the Author. Case Page Layout CommunityUser Reply Custom Field This is a Lookup field that links to the Khoros community user who replied to a case. Case Page Layout Board Name Custom Field This field holds the name of the Khoros community board containing the escalated post or message. Case Page Layout Community Postback CommentObject This section discusses the Community Postback Commentobjectand all the entities that are used with this component to create or modify page layouts, etc. Object Name:Community Postback Comment Purpose:This object is used to store case comments posted by agents, as replies to the related Khoros post. Type:Custom Object Page Layout:The “Community Postback Comment Layout” page layout displays postback comment-related information. Entities: The following table describes all the entities that can be used on the "Community Postback Comment Layout” page layout: Entity name Type Purpose Name of the page layout where this entity is used Case Custom Field This entity is the parent entity for the Community Postback Comment object. Postback Comment Page Layout Subject Custom Field This field holds the subject of the Postback Comment. Postback Comment Page Layout Salesforce Agent Custom Field This field holds the information about the Salesforce Agent. Postback Comment Page Layout isNew Custom Field This field holds information about whether the comment is new or modified. Postback Comment Page Layout Thread ID Custom Field This field holds the ID of the thread containing an escalated message. Postback Comment Page Layout Postback Comment Custom Field This field holds the content in the body of the postback comment. Postback Comment Page Layout Messsage_ID Custom Field This field holds the Khoros Message ID of the postback comment. Postback Comment Page Layout Reply Message ID Custom Field This field holds the ID of the reply message that is created while posting a comment back to the Khoros Community. Postback Comment Page Layout Post as Private Message Custom Field This field is used to specify if the postback comment is a private message or a public message. Postback Comment Page Layout Board ID Custom Field This field holds the Board ID of the Khoros community board containing the escalated post or message. Postback Comment Page Layout Agent Login Custom Field This field holds the username of the Agent who escalated the case. Postback Comment Page Layout Mark As Solution Custom Field This field is used to mark a comment as an accepted solution. Postback Comment Page Layout FullId Custom Field This field holds the 19-digit Salesforce ID of the postback comment. Postback Comment Page Layout Community User Object This section discusses theCommunity Userobjectand all the entities that are used with this component to create or modify page layouts, etc. Object Name: Community User Purpose: This object is used to store details about the Khoros community users. Type: Custom Object Page Layout:The “Community User Layout” page layout displays community user-related information. Entities: The following table describes all the entities that can be used on the "Community User Layout” page layout: Entity name Type Purpose Name of the page layout where this entity is used # of Private Messages Sent Custom Field This field holds the number of private messages sent by a community user. Community User Page Layout Contacts page # of Private Messages Received Custom Field This field holds the number of private messages received by a community user. Community User Page Layout Contacts page # of Solutions Accepted Custom Field This field holds the number of solutions accepted by a community user. Community User Page Layout Contacts page Total Minutes Online Custom Field This field holds the value of the total number of minutes a community user has been active on the Khoros community. Community User Page Layout Contacts page # of Messages Read Custom Field This field holds the number of messages read by community a user. Community User Page Layout Contacts page # of Posts Authored Custom Field This field holds the number of messages posted or authored by community a user. Community User Page Layout Contacts page # of Page Views Custom Field This field holds the number of pages viewed by a community user. Community User Page Layout Contacts page Is User Deleted? Custom Field This field holds the information about the current status of a community user. It shows whether a user is deleted or active in the community. Community User Page Layout User Profile Avatar URL Custom Field This fields holds the URL of the user’s Avatar in the Khoros Community. Community Users page to populate the URL. Administrative Notes Custom Field This field holds the administrative Notes of the community user. Community User Page Layout Community ID Custom Field This field holds the Community ID of the Khoros Community. Community User Page Layout Biography Custom Field This field holds the biography of the community user. Community User Page Layout User Homepage Custom Field This field holds the URL of the user’s personal webpage specified in the User Details page in Khoros community. Community User Page Layout Has Support Portal Access Custom Field This flag's value determines if the community user has access to the Support Portal in Khoros Community. Community User Page Layout Last Name Custom Field This field holds the last name of a community user. Community User Page Layout # of Kudos Received Custom Field This field holds the value of the total number of Kudos a community user has received. Community User Page Layout Contact Custom Field This field holds the lookup to a Contact that is associated with a community user. Community User Page Layout Community User URL Custom Field This field holds the URL of the user’s profile in Khoros Community. Community User Page Layout First Name Custom Field This field holds the firstname of the community user. Community User Page Layout Email Address Custom Field This field holds the email address of the community user. Community User Page Layout Location Custom Field This field holds information about the location of the community user as stored in Khoros Community. Community User Page Layout # of Logins Custom Field This field holds the total number of times the Community User has signed in to Khoros Community. Community User Page Layout Khoros SSOID Custom Field This field holds the SSO ID of the community user. This field is populated from Khoros Community when user sync is run. Community User Page Layout Last Visited On Custom Field This field holds the timestamp of the last visit time of the community user to Khoros Community. Community User Page Layout Khoros User ID Custom Field This field holds the User ID of the Khoros community user. Community User Page Layout Community User SSO ID Custom Field This field holds the User SSO ID of the Khoros community user. Community User Page Layout Rank Custom Field This field holds information about the rank of a community user. Community User Page Layout Contacts page Roles Custom Field This field holds information about the roles granted to the community user in the Khoros Community. Community User Page Layout Contacts page Registration Time Custom Field This field holds the registration timestamp of the user inKhoros Community. Community User Page Layout # of Fans/Followers Custom Field This field records the total number of fans or followers of the community user. Community User Page Layout Contact Object This section discusses theContactobjectand all the entities that are used with this component to create or modify page layouts, etc. Object Name: Contact Purpose: This object is used to store details about the contacts created during user synchronisation. Type: Custom Object Page Layout:The “Contact Layout - Community” page layout displays the Salesforce contact-related information. Entities: The following table describes all the entities that can be used on the "Contact Layout - Community” page layout: Entity name Type Purpose Name of the page layout where this entity is used Is Supervisor Custom Field This field records whether the community user is granted is the supervisor permissions or rights in Khoros Community. Contact Page Layout Community User Custom Field This field holds the lookup to a Community User that is associated with this Contact. Contact Page Layout User Type Custom Field This field indicates whether the Contact has an associated community user inKhoros Community. Contact Page Layout Khoros Feature Settings Object This section discusses the KhorosFeature Settings object and all the entities that are used with this component to create or modify page layouts, etc. Object Name: Khoros Feature Settings Purpose: This setting holds the Khoros Feature Settings that are used to enable or disable various Khoros app features. Type: Custom Setting Entities: The following table describes all the entities that can be used with the KhorosFeature Settings component: Entity name Type Purpose Name of the page layout where this entity is used User Sync: Create New Contact record Custom Field This field is used to specify whether contacts must be created for community users while performing user sync. Feature Settings (In Custom settings) User Sync: Link with Contacts Custom Field This setting is used to associate Contacts with Community Users when they share the same email address Feature Settings (In Custom settings) Private Message Object This section discusses thePrivate Message objectand all the entities that are used with this component to create or modify page layouts, etc. Object Name: Private Message Purpose: This object holds the private messages posted from a Case as a private message to the Community User. Type: Custom Object Page Layout:The “Private Message Layout” page layout displays the private messages-related information. Entities: The following table describes all the entities that can be used on the "Private Message Layout” page layout: Entity name Type Purpose Name of the page layout where this entity is used Community Postback Comment Custom Field This field holds the parent postback message associated with this private message. Private Message Layout Case Custom Field This field holds the parent Case associated with this private message. Private Message Layout Body Custom Field This field stores the content in the body of the private message. Private Message Layout Sent By Custom Field This field stores information about which user sent the private message. Private Message Layout Recipient Custom Field This field stores information about which user received the private message. Private Message Layout Subject Custom Field This field stores the content in the Subject of the private message. Private Message Layout Related ContentObject This section discusses theRelated Content object and all the entities that are used with this component to create or modify page layouts, etc. Object Name: Related Content Purpose: This object is used to store information about the Related Content for a Case. Type: Custom Object Page Layout:The “Case page layout” page layout also displays information the related content linked to a page. Entities: The following table describes all the entities that can be used on the "Case page layout” page layout: Entity name Type Purpose Name of the page layout where this entity is used Case Custom Field This field holds the parent Case associated with this Related Content. Case Page Layout Posted By Custom Field This field stores information about which user posted the content. Case Page Layout Content URL Custom Field This field stores the URL of the related content from the Khoros Community or Salesforce. Case Page Layout Posted On Custom Field This field stores the timestamp of the last modification made to the linked content. Case Page Layout Content Source Custom Field This field stores information about the source of the related content. Example: Salesforce or Khoros Community. Case Page Layout Content ID Custom Field This field stores the content ID of the Related Content. Case Page Layout Content Type Custom Field This field stores information about the Content Type of the related content. Example: SFDC Case, Community TKB, etc. Case Page Layout Content Title Custom Field This field stores the title of the related content. Case Page Layout Case Status Custom Field This field holds the status of the parent case to which the related content was posted. Case Page Layout Solution Object This section discusses theSolutionobject and all the entities that are used with this component to create or modify page layouts, etc. Object Name: Solution Purpose: ASolution record is created when a case is closed. The solution record captures the title and details of the solution. Note:Any other fields associated with this object are either deprecated or not used. Type: Custom Object Page Layout:The “Solution Layout - Community” page layout displays information related to a solution. Entities: The following table describes all the entities that can be used on the "Solution Layout - Community” page layout: Other Entities This section describes all the entities that are not asscociated with any single component or object like the ones discussed above. These entities are used to perform various actions.This information is provided in the following table: Entity name Type Purpose Name of the page layout where this entity is used KhorosIntegration App This is a Khoros Salesforce App which contains all the Khoros connector Related functionalities. Salesforce Home Page Khoros Remote Site This remote site setting allows Salesforce to connect with Khoros Community. Remote Site Settings SFSelf Remote Site This remote site setting holds the salesforce instance URL. (For internal use). Remote Site Settings Khoros Home Page Layout Home Page Layout This is the Default Home page for Khoros Salesforce app. Khoros Home page Federated Search Home Page Component This enables the Federated Search functionality on the Khoros Home page. Khoros Home page Non-Community Vs Community Contacts Report This report records the number of contacts created on a particular date on Khoros Community and Salesforce. Report Community Cases Vs Non-Community Cases Report This report records the number of cases created on a particular date in Salesforce. Report Case Comments with Community Content Report This report records the number of related content created on a particular date. Report Khoros (Lithium) Salesforce Integration Reports Report Folder This is a folder containing reports. Folder containing reports Private Message Tab This tab is used to navigate to private messages in Salesforce. Tab Community User Tab This tab is used to navigate to community users in Salesforce. Tab Federated Search Tab This tab is used to navigate to the Federated Search page. Tab Custom settings Tab This tab is used to navigate to the Custom Settings page. Tab Community Setting Tab This tab is used to navigate to the Community Settings page. Tab Community Postback Comment Tab This tab is used to navigate to navigate to community postback comments in Salesforce. Tab RelatedContent Tab This tab is used to navigate to navigate to related content in Salesforce. Tab Community Postback Report Custom Report Type This is a custom report type that enables you to create custom reports for postback comments. Reports Contacts with Community users Custom Report Type This is a custom report type that enables you to create custom reports for contacts and community users. ReportsAurora: Install and use the Salesforce Lightning connector
The Khoros Salesforce Lightning Connector is available for use with the Lightning Experience introduced by Salesforce. This version of the connector is provided alongside the already available Salesforce Connector (Classic). To make the most of the Salesforce Lightning experience, use theSalesforce Lightning Connector for integrationswith Khoros Community. The Khoros Salesforce Lightning Connector supports these features: User interface redesign Additional information in tooltip format Drag-and-drop capability for designing pages Learn more about these new features. Installing the Khoros Salesforce Lightning Connector To configure and use the KhorosSalesforce Lightning Connector, perform all the installation stepsdescribed in the Integrating with Salesforce section for the classic version of the Salesforce Connector, then perform the steps described here. Installing the Khoros Salesforce Lightning Connector includes these tasks: Switch the connector experience to Lightning Register a custom domain Assign the Lightning page layout to a case Assign the Lightning Page Layout to a Community User Assign the Lightning Contact page layout to a Contact record Activate the Case Record Page Activate the Community User Record Page Activate the Contact Record Page Activate the Home Page Layout Override the Postback Comments edit action Disable Caching Switch to the Lightning connector experience You can choose to switch your connector experience between Classic and Lightning. To use the Khoros Salesforce Lightning Connector: Log into your Salesforce account. Click the username in top right corner of the screen. Click Switch to Lightning Experience. Register a custom domain You must have a custom domain to use the Lightning components. Creating a custom domain also creates a custom domain name for your Salesforce organization. You must use this custom domain name to login. Note:login.salesforce.com continues to work as before. To create your custom domain: Sign in to your Salesforce account. Go to Setup > Company Settings > My Domain. Create a domain name of your choice. Click Check Availabilityto ensure your domain name is available. Note:Afteryou create a domain, you can neither delete (nor deactivate) the domain nor use the same domain name in any other Salesforce Org. Therefore, if you are configuring a sandbox or a test environment, ensure that you are not using domain names reserved for production environments. Click Register Domain. (Wait to receive a confirmation email about the creation of your domain.) Sign out of your Salesforce account. Sign in to your Salesforce account using the custom domain you created. Go to Setup > Company Settings > My Domain. Click Deploy To Users. Click Save. Assign the Lightning page layout to a case Many of the Lightning features are pulled off the page layout and added to individual components. Hence, a different page layout is created for Lightning. To assign the correct Case page layout for the Lightning connector: Sign in to your Salesforce account. Go to Setup > Object Manager > Case > Case Page Layouts. Click Page Layout Assignment. Click Edit Assignment. Select the System Administrator profile. Select theCase Layout - Community - Lightningpage layout from the Page Layout To Use drop-down menu. Click Save. Assign the Lightning page layout to a community member Many of the Lightning features are pulled off the page layout and added to individual components. Hence, a different page layout is created for Lightning. To assign the correct Community Page layout for the Lightning connector: Sign in to your Salesforce account. Go toSetup > Object Manager > Community User >Page Layouts. ClickPage Layout Assignment. ClickEdit Assignment. Select theSystem Administratorprofile. Select theCommunity User Layout Lightningpage layout from the Page Layout To Use drop-down menu. ClickSave. Assign the Lightning Contact page layout to a Contact record Many of the Lightning features are pulled off the page layout and added to individual components. Hence, a different page layout is created for Lightning. To assign the correct Contact record page layout for the Lightning connector: Sign in to your Salesforce account. Go toSetup > Object Manager >Contact>Page Layouts. ClickPage Layout Assignment. ClickEdit Assignment. Select theSystem Administratorprofile. Select theContact Layout Community Lightningpage layout from the Page Layout To Use drop-down menu. ClickSave. Activate the Case Record Page You will see the default case page design in the Lightning experience, devoid of the Khoros-built customization. To activate the Case Record Page, which is a Khoros-built customization: Sign in to your Salesforce account. Go toSetup > Lightning App Builder In the Lightning Pages section, click Viewbeside the Case Record Page. Click Activation. Click Assign as Org Default. Click Save. Click Back to exit the app builder. Navigate to any Case record to verify if the new view has been activated. Activate the Community User Record Page You will see the default Community User design in the Lightning experience devoid of the Khoros-built customization. To activate the Community User Record Page, which is a Khoros-built customization: Sign in to your Salesforce account. Go toSetup > Lightning App Builder In the Lightning Pages section, clickViewbeside the Community User Record Page. ClickActivation. Click Assign as Org Default. ClickSave. ClickBackto exit the app builder. Navigate to any Community User record to verify if the new view has been activated. Activate theContactRecord Page You will see the default Contact Record Pagedesign in the Lightning experience devoid of the Khoros-built customization. To activate the Contact Record Page, which is a Khoros-built customization: Sign in to your Salesforce account. Go to Setup > Lightning App Builder. In the Lightning Pages section, click Viewbeside the Contact Record Page. ClickActivation. Click Assign as Org Default. ClickSave. ClickBackto exit the app builder. Navigate toany Contact recordto verify if the new view has been activated. Activate theHomePage Layout You will see the default Home Page design in the Lightning experience devoid of any Khoros-built customizations. Toactivate the Home Page Layout that is compliant with the Khoros Salesforce connector: Sign in to your Salesforce account. Go toSetup > Lightning App Builder. In the Lightning Pages section, click Viewbeside Home Page Layout. ClickActivation. Select Set this page as default Home page. Click Next > Activate. Override the Postback Comments edit action In Lightning, the Postback comments “Edit” operation is overriden with custom component. To ensure that the “Edit” operation works as expected in the Khoros Salesforce Lightning connector: Sign in to your Salesforce account. Go toSetup > Object Manager > Community Postback Comment > Button, Links and Actions. In the Edit row, expand the dropdown menu, then click Edit. Select Lightning Component Bundle. Select the LiSFIntegration:LTI_Lightning_PostbackCommentEdit component. Click Save. Disable Caching When caching is enabled, there will be a delay in the display of any changes made to a Salesforce record in a custom component. In other words, you must refresh the page a few times before the changes you made appear. To improve this experience, you must disable caching in your Salesforce account: Sign in to your Salesforce account. Go toSetup > Security > Session Settings. De-selectEnable secure and persistent browser caching to improve performance. ClickSave.
