Khoros Communities 22.6 Release
With this release, we have introduced encryption of Zoom apiKey to integrate with Community Events. We also have early access to the new version of Community Salesforce Connector. This new version comes with several issue fixes and enhancements. We have also fixed several bugs.Installing and configuring your Aurora/Salesforce integration
The following sections cover the step-by-step instructions for installing and configuring your Aurora/Salesforce integration: Install Salesforce integration package Configure Salesforce integration in Salesforce environment Configure Salesforce integration in community Install Salesforce integration package You must install the integration package in your Salesforce environment. Community Aurora supports v4.3 Salesforce integration and does not support previous versions (v1/v2/v3/v4). If you are an existing Community Classic customer who has recently migrated to Community Aurora, you must migrate from v1/v2/v3/v4 to v4.3 Salesforce integration. To initiate the migration process, contact your Khoros account team. If you are a new customer to Community Aurora and are looking to install the integration package for the first time in your Salesforce environment, refer to installing the Salesforce integration package. Configure Salesforce integration in your Salesforce environment After installing the Salesforce integration package, you can follow the steps below to configure various settings in the Salesforce environment: Configure remote site access Configure custom Salesforce settings Create a New Email Service Add federated search component to the Salesforce sidebar Enable postback comment via Salesforce Reply to community members from Salesforce via private messages Modify Contact, Case, Solution, and Account Page Layouts and set up Reporting Dashboards Configure Salesforce integration in your Community Enable SFDC package and configure the Salesforce.com integration in Khoros Community Admin Enable and configure the private support Case Portal (Enhanced SFDC Offering) Set up Salesforce search components for your Community integration Synchronize Community members with Salesforce. After you've deployed your Aurora/Salesforce integration, you can: Allow your agents and your community members to interact through a private support Case Portal View community member details and statistics within Salesforce.com. Leverage postback options when working Salesforce cases Reply to community members from Salesforce via private messagesAbout 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.Configure Salesforce integration in an Aurora community
After you set up your Salesforce environment, you need to configure your community environment to complete the integration. From the community Settings area, admins can access and configure Salesforce settings (Settings > Features > Salesforce). To configure Salesforce integration: Sign in to the community as an Admin. Go to Settings > Features > Salesforce. From the Settings section, configure the following: In Username for Salesforce, click Edit and configure the following: Username for Salesforce: Enter your full sign-in name (usually an email address) for a user with the System Administrator profile in your Salesforce environment. Password:Enter your passwordandyourSalesforce.comsecurity token in this field. For example, if your password is “secret” and your security token is “1234,” you would enter “secret1234” in this field. If you have lost your security token, consult theSalesforce.comdocumentation on how to reset it. Salesforce API URL: This is a mandatory field. Enter a URL for the Salesforce SOAP API based on the environment type you’re connecting to: Production: https://login.salesforce.com/services/Soap/u/ Sandbox: https://test.salesforce.com/services/Soap/u/ Authentication endpoint for Salesforce: Enter the authentication endpoint based on the Salesforce environment you’re connecting to: Production: https://login.salesforce.com/services/oauth2/token Sandbox: https://test.salesforce.com/services/oauth2/token Email for Salesforce integration failure notification: Enter the email addresses (separated by commas) of the members to be notified when the Salesforce integration point fails.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.
