Table Of Contents
Cisco WebEx Social Release Notes,
Release 3.4 SR2
Contents
Overview
What's New in Cisco WebEx Social
What's New in Release 3.4
What's New in Release 3.4 SR1
What's New in Release 3.4 SR2
Important Notes
Related Documentation and Training Videos
Defects
Using the Bug Toolkit
Known Defects
Resolved Defects
Cisco WebEx Social Release Notes,
Release 3.4 SR2
Revised September 16, 2013
These release notes provide important information for Cisco WebEx Social 3.4 SR2 build 3.4.1.10200.141.
Contents
These release notes include these topics:
•
Overview
•What's New in Cisco WebEx Social
•Important Notes
•Related Documentation and Training Videos
•Defects
Overview
Cisco WebEx Social is a collaboration platform that enables content creation, real-time communications, and other collaborations in a personalized manner.
What's New in Cisco WebEx Social
The following sections describe major new features and functions in the Cisco WebEx Social 3.4 release:
•What's New in Release 3.4
•What's New in Release 3.4 SR1
•What's New in Release 3.4 SR2
What's New in Release 3.4
New features and functions in Cisco WebEx Social 3.4 include the following:
•Updates and enhancements to the Cisco WebEx Social API. New features include:
–New operations for managing user groups
–New operations for managing versions of a post
–New Meta activities resource, which is a representation of a relationship between the logged-in user and the Activity activities resource
•The master account feature, which you configure from the Portal drawer, lets Cisco WebEx Social users set the same login credentials (user name and password) that they use to access various services in Cisco WebEx Social.
•The session setting feature, which you access from the Server drawer, lets you configure the maximum number of times that any user can be logged in to Cisco WebEx Social concurrently.
•Email configuration items have been consolidated in the Email Configuration area in the Application > Integration page of the Director.
What's New in Release 3.4 SR1
New features and functions in Cisco WebEx Social 3.4 SR1 include the following:
•Updates to the Cisco WebEx Social API, including:
–Enhancements to functionality of the meta query parameter
–Updates to the Metadata resource
–New Post Version and PostVersionDiff resources
–New Report Content as Inappropriate operation
–New User Group resource operations
–New operations for obtaining information about a post, obtaining information about the differences between two versions of a post, and restoring an older version of a post
•Various bug fixes
What's New in Release 3.4 SR2
Cisco WebEx Social 3.4 SR2 includes various bug fixes.
Important Notes
This section describes limitation, restrictions, and other important information that applies to this release of Cisco WebEx Social.
•Although the CAS tab appears in the Account Settings > Portal > Settings > Authentication window, Cisco WebEx Social does not support Central Authentication Service (CAS) and the fields in this tab are not used.
•When using Show & Share release 5.3 with Cisco WebEx Social, do not install Show & Share patch1.
•If SSO is enabled in your network, make sure that the Enable SSO box in the Notifier area of the Configuration window in the Director is checked. This configuration ensures that user accounts are not locked if a password lockout policy is configured in your Active Directory.
•Cisco WebEx Social no longer required redirects in the Cisco WebEx Social Apache server to the Sametime Proxy server. For Sametime chat to be operational, this change requires that each Cisco WebEx Social client (browser or mobile application that loading Cisco WebEx Social) have routing access to the SameTime proxy server.
•Using the ext3 file system on your NFS server can limit the number of library documents and post attachments that Cisco WebEx Social can store. For more information, use the Bug Toolkit to access the defect number CSCtk55146 (see the "Using the Bug Toolkit" section).
•This Cisco WebEx Social release adds support for using the IBM Sametime Connect client for chat and availability in place of the integrated Cisco WebEx Social client. To determine the availability of Sametime and to launch the client on new chat sessions, Cisco WebEx Social sends HTTP requests to the local Sametime service at localhost port 59449. Because the local Sametime service supports only HTTP, if your organization accesses Cisco WebEx Social through HTTPS, the web browsers of your users may block outgoing HTTP requests as a security measure. To allow Cisco WebEx Social to launch Sametime, you must instruct users to enable mixed content. Enabling mixed content varies from browser to browser. See your web browser documentation or search the Internet for detailed steps.
•If synthetic monitoring is not configured, it is enabled by default in release 3.4 SR1 for both fresh installations and upgrades. If synthetic monitoring has been enabled or disabled, that setting takes precedence over the default behavior.
Administrators can disable synthetic monitoring by setting the property synthetic_monitor_disabled to true. By default this property is not configured, which means that synthetic monitoring is enabled
Related Documentation and Training Videos
The following Cisco WebEx Social documents are available at http://www.cisco.com/en/US/products/ps10668/tsd_products_support_series_home.html.
•Cisco WebEx Social Administration Guide, Release 3.4
•Cisco WebEx Social Installation and Upgrade Guide, Release 3.4
•Cisco WebEx Social Server: Getting Started Guide, Release 3.4
•Cisco WebEx Social API Reference Guide, Release 3.4
•Cisco WebEx Social Backup and Restore Guide, Release 3.3 and 3.4
•Open Source Used In Cisco WebEx Social 3.4
•Cisco WebEx Social Theming Guide, Release 3.4
•Cisco WebEx Social Frequently Asked Questions, Release 3.4
•Cisco WebEx Social Compatibility Guide
Cisco WebEx Social training videos are available at http://howdoi.webex.com.
Defects
This section includes these topics:
•Using the Bug Toolkit
•Known Defects
•Resolved Defects
Note Because defect status continually changes, be aware that the information in the following sections reflects a snapshot of the defects at the time that the release notes were compiled
Using the Bug Toolkit
You can use the Bug Toolkit to find information about defects for the this release, including a description of the issues and available workarounds. The Bug Toolkit lists open and resolved defects.
To use the Bug Toolkit, follow these steps:
Procedure
Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
Step 2 Log in with your Cisco.com user ID and password.
Step 3 To look for information about a specific problem, enter the bug ID number in the Search for bug ID field, then click Go.
Step 4 To look for information if you do not know the bug ID number:
a. Choose Collaboration from the Select Product Category menu.
b. Choose Cisco WebEx Social from the Select Product menu.
c. Choose the version number from the Software Version menu.
d. Under Advanced Options, choose Use default settings or Use custom settings. The default settings search for severity 1, 2 and 3 bugs, open and fixed bugs, and only bugs containing bug details. Use the custom settings to change the severity and status parameters, or to search for keywords within the bug headline and description.
Known Defects
Table 1 lists known defects in this release.
Table 1 Known Defects
Identifier
|
Headline
|
CSCth11656
|
Some portlets are writing logs to other folders
|
CSCth78771
|
Issue adding multiple users in Cisco WebEx Social
|
CSCtj67519
|
Cisco WebEx Social only creates links for first tier of child pages
|
CSCtk02063
|
SnS: Progress bar does not update for WMV video—tried in FF in windows
|
CSCtk55146
|
CMS can have just under 32,000 folders
|
CSCtk98383
|
CM: Thread/post count in discussions needs to filter out hidden comments
|
CSCtl88103
|
For some users, Message Board posts cannot be seen
|
CSCtn14008
|
Issues updating Role Permissions
|
CSCtn42569
|
CWC crashes browser when connection to CUCM is lost for extended period
|
CSCtn48560
|
Confusing user experience for comments to a Micropost
|
CSCto31018
|
Safari 5: Changing focus via tab does not let you type into content
|
CSCto41766
|
Locked portlet becomes unlocked when containing tab is moved
|
CSCto56051
|
IE9: Hover card is changed undesirable to another user
|
CSCto79541
|
[Struts+Liferay] OutOfMemoryError when uploading large file
|
CSCtr84045
|
Video upload does not work for some users
|
CSCtw90000
|
Slow OCS async calls from browser holds up browser TCP sessions
|
CSCty31535
|
Occasionally services start without creating a pid file
|
CSCty92458
|
Address line: Error logsAddress line 3 has a limit of 75 characters
|
CSCtz32621
|
Tracking bug for PHP security issues
|
CSCtz42145
|
GNU libc GLOB_LIMIT Remote Denial of Service Vulnerability
|
CSCtz44909
|
Linux Kernel drm_mode_dirtyfb_ioctl() Local DoS Vulnerability
|
CSCtz44920
|
Linux Kernel USB Interface Local Information Disclosure Vulnerability
|
CSCua77372
|
No or very low audio on MAC
|
CSCua78056
|
Chat and presence (CUPS anad jabber): max chat sessions
|
CSCua98112
|
User sometimes does not receives notification that the other side closes
|
CSCua99198
|
[Decoupled chat] Desktop chat client is not launched when clicking on user
|
CSCub24665
|
Glibc contains vulnerabilities
|
CSCub70719
|
Admin password with special characters in OVF properties sets it to null
|
CSCuc69692
|
Social keeps setting name and companyid in loop
|
CSCuc70477
|
Accessibility: JAWS does not read out expertise, interests, work hours
|
CSCuc90357
|
Switching to a child page with some apps, takes 5 to 6 seconds in IE8
|
CSCud10461
|
IE8: JavaScript error in chat/IM presence
|
CSCud15220
|
Editor does not support resizing of images in Safari and Chrome
|
CSCud18265
|
WebEx Social lacks alerting for ActiveMQ degradation
|
CSCud96226
|
Adding to hashtag in micropost does not recognize appended text as hashtag
|
CSCue22974
|
Cannot move library documents from root to sub folder
|
CSCue45246
|
Line spacing in final post different than what was seen in editor
|
CSCug09600
|
WebEx Social instant meeting notifications not received by offline attendees
|
CSCug09630
|
Calendar, My Communities, Recent People, and Communities not loading
|
CSCug09631
|
Favicon issue on chrome
|
CSCug09633
|
Enabling of the permission field under Permission in Discussion category
|
CSCug09657
|
Apply Config should not be enabled when user logs in the Director page first time and does nothing
|
CSCug09659
|
Presence not updated when switching preferred client
|
CSCug57595
|
WebEx Social is saving last set user presence and tries to set it upon relogin
|
CSCug57610
|
Do not Disturb shown instead of Offline
|
CSCug57674
|
Stop recording or Send appears although call is not answered
|
CSCug57676
|
Disclose hidden community when post is turned to public
|
CSCug63147
|
Date of last status update incorrect in WebEx Social hover card.
|
CSCug72421
|
The communityName field search does not return correct results sometimes
|
CSCug85474
|
"Perform sync just once" causes LDAPsync from not running
|
CSCug87391
|
[httpd] memory leak when using Kerberos SSO and OCS
|
CSCug90409
|
IE Compatibility Mode makes Director web page unusable
|
CSCug92864
|
Documentation fails to explain requisite configuration for inbound email
|
CSCuh09554
|
Monit script check fails because NFS mount points appear unwritable
|
CSCuh13714
|
Integrity Check Failed Errors on 3.1SR3
|
CSCuh55193
|
Media query in CSS breaks content
|
CSCuh67522
|
Getting stuck when doing server rabbitmq-server status
|
CSCuh69059
|
Webex Social select user profile from likes list and scroll bar disappears
|
CSCuh70388
|
Full sync marks users inactive due to memcached errors
|
CSCuh74411
|
Mobile client—fetching members list in community times out
|
CSCuh76311
|
Bookmark portlet: sorting is not working for entries
|
CSCuh76312
|
IE8: Save on Display Settings page is not working.
|
CSCuh76315
|
Infosys-help: Attachments count incorrect after restoring an older version
|
CSCuh76316
|
Searching within a list throws user out of context
|
CSCuh76319
|
JS Error on trying to log in to WebEx Social
|
CSCuh76320
|
Infosys-help: Can comment a post after being unshared
|
CSCuh76322
|
Changes made in director UI not reflected by puppet during upgrade
|
CSCuh76323
|
msn.com opens in parent WebEx Social page instead of iFrame
|
CSCuh76324
|
UI request to start WebEx meeting loops endlessly
|
CSCuh76327
|
Posts shared from Twitter are not reflected in followers activities
|
CSCuh76329
|
Activities API does not return timestamp for share post activity
|
CSCuh76330
|
Unchecking all checkboxes in display settings page should throw error
|
CSCuh76332
|
Post with long title overlaps with the next layout
|
CSCuh76334
|
Suggestions not updated after applying Similar to you portlet setting
|
CSCuh76335
|
After added My Direct Reports , My Direct Reports changes to My
|
CSCuh76336
|
Export minor tab is not visible
|
CSCuh76337
|
Clicking on custom attribute in control panel leaves blank space
|
CSCuh76338
|
Cannot sort on Name and description in Favorite Communities
|
CSCuh76340
|
CKeditor does not launch intermittently in IE when creating a wiki
|
CSCuh76341
|
Searching community in last visited community returns multiple results
|
CSCuh76342
|
Unclear error message when exceeding SharePoint file size limit
|
CSCuh76345
|
User should not be able to create discussion category with existing name
|
CSCuh76349
|
Showing the cached info for an updated meeting (EWS)
|
CSCuh79056
|
Purpose of Cluster Security section in director is unclear
|
CSCuh79057
|
XSS: HTML in opensocial settings
|
CSCuh79058
|
Cannot play .wmv embedded video in post created via open API
|
CSCuh79060
|
The verb field is missing for reply to a blog activity
|
CSCuh79062
|
publicPost field in GET api/rest/users/@me/posts always false
|
CSCuh86688
|
"Is typing" notification keeps showing when user offline
|
Resolved Defects
Table 2 lists resolved defects in this release.
Table 2 Resolved Defects
Headline
|
Identifier
|
CSCui13207
|
Portlet preferences not being cached in memcached
|
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2013 Cisco Systems, Inc. All rights reserved.
Feedback
