Release Notes

New Features in Version 4.0

Richer Handling of Microsoft Office Documents (Optional Module)

The application now includes more intuitive handling of Microsoft Office documents. By default, this includes a preview mode that displays the document's text (Excel documents are not currently supported for preview), as well as lets people add comments. (PDF documents are also previewed.)

Better integration also optionally includes the Jive Desktop add-in for Microsoft Office. With the add-in, people can upload their document, then synchronize changes as they work -- all without leaving their Office application.

Support for Mobile Devices

With this version, Jive adds a native iPhone application so that users need never be far from the community. Downloadable from the App Store, the iPhone app provides a UI through which people can keep up with both content and their connections.

Using the admin console, administrators can grant or reject access to individual mobile devices and community members using them.

Jive Market Engagement (Optional Module)

Jive Market Engagement provides features through which marketers can collect observations about the market and from them synthesize viewpoints to drive decision-making. The Social Media Console provides a way to remain attentive to information relevant to market research.

Permissions Model Reworked

The permissions model was completely redesigned to make permissions easier to apply, and to make it clearer how permissions are applied in each area.

• Small-grained permissions -- reading, creating, voting, and so on -- were grouped into levels based on common community roles and access levels.
• The admin UI provides better cues about how permissions are applied in each area.
• The admin user interface provides better information about how permissions are inherited among spaces.
• A "default space" now represents a template for applying permissions to new spaces.

Personalization and Customization UI Enhancements; Added Widgets

Changes to the page personalization and customization UI make the interface more scalable and easier to use. For example, widgets are now grouped into four categories (people, places, content, other). Users select a category, then choose a widget from the list.

Six new widget layouts give users more options when designing their pages. These include horizontal and vertical widget drop zones. New widgets were also added, including View Document, Featured Content, Quick Tips, and Your Content.

Better Scalability for the User Interface

Several changes were made to make the UI more scalable. Some of these changes are designed to present in smaller pieces those sets of information that could get quite large as the community grows.

Where spaces are listed, for example, the static space list was replaced with a list that shows only one level of the hierarchy at a time, letting the user navigate into those subspaces they want to see.

In some places where the user was being prompted to choose a space, they can now simply type the name of the space they want or choose from a list.

Places Improvements

Places are where people keep content, such as spaces, projects, social groups, and so on. This version enhances how people navigate and use existing places, but it also adds a new, personal place where people can keep content that's not quite right for community consumption. Here's a brief list of changes included:

• Projects can now be created in social groups as well as spaces.
• Group owners can edit, delete, and moderate their group's content.
• Spaces, projects, and groups now support categories (formerly tag groups).
• People can now save content to their profile, then decide who can see it (public, private, or specific people and connection labels).

Social Groups

Changes to the permissions model include support for separately granting permission for creating public and private social groups. It's now possible to grant permission to create public social groups, but not private ones, for example (on upgrade, anyone previously with permission to create social groups will be able to create both kinds).

Social group admins have the same controls as space admins, including the ability to customize the homepage, create categories, edit and remove other peoples content, and even delete the entire group.

Rich Text Editor (RTE) Improvements

The rich text editor has been made more stable and intuitive. Here are some of the changes:

Improvements and fixes for users

• Cursor position and stability are more reliable than in previous versions.
• Table and list editing were improved.
• ALT+TAB and CTRL+TAB now work in Windows as they should.
• CTRL+z and CTRL+y are now supported for undo and redo, respectively.
• Pasting content from Word, Excel, or HTML files produces much more consistent results than in previous versions.
• Issues related to single and double quotes were fixed.
• Support was added for linking to files using the file: protocol.

Improvements for developers

• To better support customizations from Jive Professional Services and others, the editor's plugin and macro support are richer and more robust.
• The editor now internationalized for localization.
• It's easier to implement the editor on a new page.

Private Discussions and Documents

People can now create private discussions and documents, controlling the participant list and visibility. Private content is not associated with a space and is available under the Your Discussions section of the user's profile. Previously discussions and documents had to be contained in a place visible to others.

Tag Groups Replaced with Categories

Tag groups were replaced with categories. Where tag groups were essentially a rollup of tags, categories needn't have tags associated with them. An administrator defines categories for use in a place (such as a space). If the administrator associates tags with the category, users adding those tags will receive a recommendation that they add their content to the category.

When creating a category, an administrator has the option to automatically associate content with the related tags. This is a one time process that will go back through created content and put it in the category based on matching tags. It is meant to be an easy way for administrators to categorize content that has been created before a specific category existed.

Email: Creating Content, HTML Format, Activity Digest

Functionality previously available in the Advanced Email Plugin was merged into the core product and is now available as an optional module. Through this feature, people can create community content by sending it in email to the community. The email addresses are focused per-place -- addresses available as vCards they can add to their address book.

Emails sent by the system -- such as notification emails -- were redesigned to include an HTML version.

The application can now send a digest email that captures activity of interest for the user who receives it.

Better License Management

The licensing model was reworked to support licensable components, including modules. Licensing support has also been extended to include Installation types (such as production and development types) and terms (such as whether the license should cover per-seat or per-page-view).

This version also includes support for collecting and reporting license and usage data. Regular license reports are now a required part of managing an application instance.

Support for Caching Static Resources with a Lightweight CDN

You can now specify the URL to a CDN server that clients will use to retrieve static resources. After configuring your CDN server, you can configure Jive SBS to be aware of it by entering that server's URL. When you do, Jive SBS will rewrite URLs to static resources so that the browser retrieves them at your CDN server's location. See the documentation for more on using the feature.

Bridging Content

With the bridging feature, administrators can connect two Jive communities together. Through this connection, people who are members of both communities can see content of one while they are in the other. This version adds the ability to bridge a discussion across communities.

Better Protection Against Automated Logins

You can now set up the application to discourage automated (computer-driven) registration and login. This protection includes login throttling to slow the login process and support for a captcha image.

The end user UI now also includes a password strength meter that helps users know how strong their password is.

Upgrade and Installation Notes

Email Improvements

Email message templates now support both text and an HTML format. if you customized your email templates, consider upgrading you customizations to the new template style. You can also now edit template markup for headers and footers that are applied to outgoing email. To include a header image the HTML email format, replace the ${sbsName} variable in the template (sbsName represents the community name).

If you're using the the "advanced email" plugin and you purchase a license that supports advanced email features (such as creating content via email), be sure to remove the plugin before upgrading. Properties that support the feature are different than they were.

The admin console UI for configuring has changed. The tab formerly at System > Settings > Email Server > Incoming Monitor is now called simply "Incoming". An Advanced Incoming tab has been added to support more robust reply-by-email and create-by-email features.

Social Groups

It's now possible to grant permission for someone to create public social groups, but not private ones. On upgrade, anyone previously with permission to create social groups will be able to create both kinds.

Microsoft Office Documents

The application now includes more intuitive handling of Microsoft Office documents, including a preview mode that displays the document's text (Excel documents are not currently supported for preview). To keep upgrade time as brief as possible, document previews are generated on first viewing, rather than all at once during upgrade.

Note: Software for generating document previews must be installed on a separate node. See online documentation for more information on installing a DocVerse conversion node.

Licensing

Regular license reports are now required to keep the license valid. Using the admin console, you can upload the required license reports or have them automatically uploaded.

Tag Groups Converted to Categories

During upgrade, tag groups will be converted to categories. The tags associated with the tag groups will be associated with

Permissions Reworked

The permissions model has been completely reworked to make it easier to understand and manage permissions. The best practice recommendation is now to assign permissions to user groups, creating overrides for individual users only when necessary.

Signup

For developers: createGroup(String name) has been removed in favor of createGroup(String name, boolean isFederated). This means that all custom group manager implementations or custom code that creates groups will have to be updated to reflect this change.

Special Notes

GroupService groupMembers Resource Returns Only Information Available to the Caller

The groupMembers resource of the GroupService REST web service returns user data for the specified group. However, data that is ordinarily not available to the caller is omitted. In other words, if the user name and email address is hidden from the member whose credentials are being used to request the resource via REST, then those fields will not be returned.

Resolved Problems

Issue List

Bugs

Regressions

Known Limitations

Notable

su - jive
~/bin/joosd/joosd start

Issue List

Bugs

Regressions