Cisco Cisco WebEx Social for Mobile
3
Cisco WebEx Social Release Notes, Release 3.1 SR3
OL-29067-01
Important Notes
What’s New in Release 3.1 SR3
Cisco WebEx Social 3.1 SR3 fixes various issues.
Important Notes
This section describes limitation, restrictions, and other important information that applies to this release
of Cisco WebEx Social.
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.
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.
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.
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.
•
In some cases, the auto-generated e-mail aliases for Communities and Discussion Forum Categories
are not generated when upgrading from Quad 2.5(2) to Cisco WebEx Social. To work around this
issue, contact the Cisco Technical Assistance Center TAC to obtain an updated migration script. For
more information, use the Bug Toolkit to access the defect number CSCuc00380 (see the
are not generated when upgrading from Quad 2.5(2) to Cisco WebEx Social. To work around this
issue, contact the Cisco Technical Assistance Center TAC to obtain an updated migration script. For
more information, use the Bug Toolkit to access the defect number CSCuc00380 (see the
•
Preventing community owners from binding discussion categories to mailing lists—In earlier
releases of Cisco WebEx Social, community owners and community administrators were allowed to
bind discussion categories to mailing lists by default. In release 3.1, this feature can be enabled or
disabled by using the following property. Set this property to true to disable the mailing list binding
feature for community owners and community administrators. This way, only the Cisco WebEx
Social Administrator is able to create discussion category to mailing list bindings.
releases of Cisco WebEx Social, community owners and community administrators were allowed to
bind discussion categories to mailing lists by default. In release 3.1, this feature can be enabled or
disabled by using the following property. Set this property to true to disable the mailing list binding
feature for community owners and community administrators. This way, only the Cisco WebEx
Social Administrator is able to create discussion category to mailing list bindings.
communities.mailinglists.ui.adminonly
For information about how to set advanced portal properties, see the “Advanced Portal Properties”
section in Cisco WebEx Social Administration Guide.
section in Cisco WebEx Social Administration Guide.
•
Disabling outbound email notifications to mailing lists—By default, Cisco WebEx Social sends
email notifications to mailing lists each time a new discussion is created in the category. You can
enable or disable this feature by using the following property. Set this property to false to disable
the outbound notifications for all communities in Cisco WebEx Social.
email notifications to mailing lists each time a new discussion is created in the category. You can
enable or disable this feature by using the following property. Set this property to false to disable
the outbound notifications for all communities in Cisco WebEx Social.
outbound.email.mailinglists.enabled
For information about how to set advanced portal properties, see the “Advanced Portal Properties”
section in the Cisco WebEx Social Administration Guide.
section in the Cisco WebEx Social Administration Guide.
•
Beginning with Cisco WebEx Social 3.1 SR2, a configuration page appears the first time that a user
clicks the Sign-in button to access voice messages via the Visual Voice Mail portlet. On this page,
the user must enter the log in credentials that are required to access voice messages. The system
saves this information so it is not required for subsequent sign-ins to the Visual Voice Mail portlet.
clicks the Sign-in button to access voice messages via the Visual Voice Mail portlet. On this page,
the user must enter the log in credentials that are required to access voice messages. The system
saves this information so it is not required for subsequent sign-ins to the Visual Voice Mail portlet.
•
The following know issue applies to email notifications: If you are subscribed to a Cisco WebEx
Social community category, then subscribe to a discussion in that category, then unsubscribe from
that discussion, you continue to receive email notifications for replies to that discussion.
Social community category, then subscribe to a discussion in that category, then unsubscribe from
that discussion, you continue to receive email notifications for replies to that discussion.