Jive-n Record Retention Extension

Document created by udit.shah on Jul 8, 2015Last modified by javier.garderes on Jul 3, 2020
Version 42Show Document
  • View in full screen mode

The Records Retention plugin is an effective tool to track activity in your Jive community. Before using it, be sure you understand what it captures and where it sends this captured information.

Overview

The Records Retention plugin records who does what, and when they do it in your Jive community. It captures snapshots of the activity within a community. In Jive-n communities, Records Retention Module exists as part of the core application code and it integrates with downstream SMTP, XML, or RestAPI based retention and e-discovery systems for retaining records.

 

Why would I use it?

This plugin is a useful tool to help an organization that needs to meet legal requirements, particularly in a regulated industry. It can also be used to track activity in a community.

 

What does it capture?

The Records Retention extension captures events for each content type and space type and some generic actions that can be triggered for almost any type of content entity. For the full list of retained events, refer to Understanding Records Retention.

 

Where does it send this captured information?

There are currently three ways to configure the Records Retention extension:

  • Email (SMTP): Each event is converted into an email message and delivered it to the configured email inbox or inboxes. For more information on configuration, see Configuring Records Retention for SMTP in the documentation.
  • XML: Each event is converted into an XML file and put into the Jive server binstore. For more information on configuration, see Configuring Records Retention for XML in the documentation.
  • Actiance (REST): Each event is sent to an instance of Actiance Vantage by using RESTful communication. For more information about Actiance Vantage, see Connected Capture on the Smarsh portal at https://www.smarsh.com/products/connected-capture/vantage-modal. For more information on configuration, see Configuring Records Retention for Actiance Vantage in the documentation.
    A secure connection is required to connect to the Actiance host. An SSL certificate must be created and imported into Jives java keystore (/usr/local/jive/java/jre/lib/security/cacerts) and there is no option to disable the behavior.

 

HIPAA compliance

Starting in 8.0.1, the records retention module meets the requirements of the Health Insurance and Accountability Act and ensures audit data recording user activity to electronic protected health information is protected.

 

Documentation

 

Releases

Records Retention release notes are included in the Hosted and On-Premise release notes. You can find them at Jive Hosted and On-Prem (HOP).

 

Downloads

You can find the downloads in the Attachments section at the end of the article.

 

Recent releases

Jive versions Compatible plugin versions Release date Description
9.4.0.09.4.0.0July 3, 2020Update for Jive 9.4.0.0 compatibility
9.3.0.09.3.0.0May 29, 2020Update for Jive 9.3.0.0 compatibility
9.2.0.09.2.0.0January 20, 2020Update for Jive 9.2.0.0 compatibility
9.1.0.09.1.0.0September 02, 2019Update for Jive 9.1.0.0 compatibility
9.0.7.19.0.7.1July 11, 2019Update for Jive 9.0.7.1 compatibility
9.0.7.09.0.7.0April 24, 2019Update for Jive 9.0.7.0 compatibility
9.0.6.09.0.6.0December 18, 2018Update for Jive 9.0.6.0 compatibility
9.0.5.09.0.5.0September 11, 2019Update for Jive 9.0.5.0 compatibility
9.0.4.09.0.4.0September 17, 2019Update for Jive 9.0.4.0 compatibility
9.0.3.09.0.3.0December 15, 2017Update for Jive 9.0.3.0 compatibility
9.0.2.0, 9.0.2.19.0.2.0July 5, 2017Update for Jive 9.0.2.0, 9.0.2.1 compatibility
9.0.1.09.0.1.0March 3, 2017Update for Jive 9.0.1.0 compatibility
9.0.0.19.0.0.1January 12, 2017Update for Jive 9.0.0.1 compatibility
9.0.0.09.0.0.0November 9, 2016Update for Jive 9.0.0.0 compatibility

 

Historical releases

Jive versions Compatible plugin versions
8.0.6.08.0.6.0
8.0.5.08.0.5.0
8.0.4.08.0.4.0
8.0.3.08.0.3.0, 8.0.3.1
8.0.2.08.0.2.0, 8.0.2.1, 8.0.2.2
8.0.1.08.0.1.0

Outcomes