-
Copy the DLL Saleslogix.Social.Mashups.dll (from the bundle) to C:\Program Files (x86)\SalesLogix\Platform
-
Install the bundle: Saleslogix Social Buzz has the new social tabs.
-
Optionally, add the following directive to %ALLUSERSPROFILE%\Sage\Platform\Configuration\Global\MashupConfiguration.xml (this will allow declaration of other mashups making used of the Linkedin and Twitter providers):
Saleslogix.Social.Mashups.Processors.TwitterProcessor, Saleslogix.Social.Mashups Saleslogix.Social.Mashups.Processors.LinkedinProcessor, Saleslogix.Social.Mashups
Twitter and LinkedIn are both supported but must be configured under Administration -> Authentication Providers, then the users need to authorize the service under Tools -> Options.
For Twitter, the provider must be named "Twitter OAuth", and the parameters are as follows:
Provider URL = https://api.twitter.com
OAuth Version = 1.0
Request URL suffix: /oauth/request_token
Request token method: POST
Supports Callback: true
Secret: consumer secret obtained when registering Twitter application
Client ID: client id obtained when registering Twitter application
Host URL: https://api.twitter.com
Approval URL Suffix: /oauth/authenticate
Requires access token: true
Access Url Suffix: /oauth/access_token
For LinkedIn, the provider must be named "LinkedIn", and configured as follows:
Provider URL = https://www.linkedin.com/uas/oauth2
OAuth Version = 2.0
Supports Callback = true
Secret = consumer secret obtained when registering LinkedIn application
Client Id = client id obtained when registering LinkedIn application
Host Url = https://www.linkedin.com/uas/oauth2
Approval Url Suffix = /authorization
User Data String = ?response_type=code&client_id={CLIENTID}&state={STATE}&redirect_uri={REDIRECT_URI}
Requires access token: true
Access Url Suffix = /accessToken
Access Data String = grant_type=authorization_code&code={TOKEN}&redirect_uri={REDIRECT_URI}&client_id={CLIENTID}&client_secret={CLIENTSECRET}
When registering the application on LinkedIn developer network, set the default scopes as r_basicprofile, r_fullprofile, r_network, rw_nus
Displays updates retrieved from Social Network in a timeline Limitations: limited # of days and updates from both Twitter and Linkedin On some networks (e.g. Linkedin) updates cannot be retrieved if not connected to the person directly, if that happens there will be an error message “Unable to retrieve update for the selected user”
Really the same as Social Timeline, but displayed as a list instead of a timeline widget
Ability to configure and display “profile”, retrieved from social network. This is typically available even if not connected, though the information will be more limited the more distant the connection is Configuration is the same as the one used by the other tabs Stored in the database in EntitySocialProfile
A standalone page, distinct from the 3 tabs. Allow searching for keywords, retrieving matching post, and taking action on them (e.g. creating opportunities)
Add OAuth provider Add mashup processor Create mashups for update feed, people search (if appropriate), profile (if available) Add definition for network in DefineSocialNetwork.js
11/2/2013 - Nicolas Galler - Updated LinktoTwitter library, removed OAuth bundle as it is no longer necessary with 8.0 HF4
8/9/2013 - Nicolas Galler - Added 3 new tabs: Social Updates, Social Profile, Social Timeline, and 1 navigation item: Social Queue.
4/24/2012 - Mark Dykun - Uploaded the VFS bundle that was updated for SalesLogix 7.5.4. Note that there will be merges requred for some of the support files ensuring that the core functionality is not overwritten between service packs.
12/7/2010 - Mark Dykun - This Accelerator provides Twitter support to Sage SalesLogix 7.5.3 Client. It requires the Standard Problem/Resolution accelerator be installed first as it integrates with the Ticket Problem Type dialogs. The functionality augments several stock smartparts (Lead, Ticket, Defect, Ticket Problem Type) as well as the Link Handler (C# and Javascript) files. Make sure that you back the ones you have up and determine the change sets to migrate across. oAuth support is added in this release and before the user can post to twitter they will need to go to options tab and register the application with Twitter.
Apply the SocialFields SXB to add a new field to the Contact Table (TwitterId)