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

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.

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)