This document will serve as the Administrator's Guide for the Jive Events Extension.
The Jive Events extension is delivered in a .jar file that is installed on an existing Jive instance. The name of the file will depend on the version of the plugin (e.g. event-type-plugin-126.96.36.199-1.jar). The version number of will generally correspond to the version of Jive for which it was intended, with the -X suffix indicating the release number (0-based) for that version. For example, 188.8.131.52-1 indicates the second release of the extension for Jive 184.108.40.206. To be sure you have the most recent release of the extension for your version of Jive, consult the Jive Events Extension Compatibility Matrix, which will contain the recommended releases for each Jive version.
While the Events Extension is available for anyone to download, you must have a valid license to run it on your instance. You can check your license in your Jive instance's Admin Console, under the System --> Management --> License Information section.
If you see the Event Module entry listed in the License Components and Allotments section, you are all set to install the Events Extension. The extension itself may still be installed if it has not been license on your instance, but no Events functionality will be exposed. If the module is not listed, but you have purchased the Events Extension, contact Jive Account Support to have your license updated. If you have not purchased the Events Extension yet, contact Jive Sales and they'll be happy to hook you up.
For Hosted Customers
To install the Events Extension, hosted customers need only contact Jive Account Support, and request that the extension be installed. Installation only takes a few minutes, but will require a server restart.
For On-Prem Customers
Customers hosting their own Jive instance can install the Events Extension, like any other Jive Plugin, via the Admin Console. Once the file is uploaded, and the plugin is installed, the server will need to be restarted.
Once the instance is restarted, the Events Extension will show up in the Admin Console's Plugins tab. The Events Extension requires no additional setup, and events will be available as a content type to the Jive instance's users.
Uninstalling the Events Extension, which also requires a restart, will remove the extension from the system, but not its data. All Events-related data will remain in the system, but will not be visible by users.
Permissions for events are configured the same as any other content type, within the Admin Console's Permissions tab, in the Space Permissions section. Here, an administrator can determine which users or groups have permission to perform which actions with respect to events. Like other content types, permissions for the Events content type can be specified as one of three different presets, or an advanced, custom set of entitlements.
|Perm Level||Read||Create||Insert Image||Rate||Comment/Reply|
While the Evens Extension requires no addition setup beyond its initial installation, it is configurable by way of system properties. These properties can be modified, like all others, in the System --> Settings --> System Properties section of the Admin Console. However, there is an easier way to identify all possible configurable areas of the Events Extension – in the System –> Settings –> Event Custom Content Type Properties section.
Here all system properties relevant to the Events Extension are exposed, along with a description of what behavior is affected by the property's value.
|jive.event.country.filtering.enabled||This property has been deprecated. Filtering by country is currently not available.|
|jive.event.default.enabled.community||Specifies whether Events are enabled for new Communities by default. This affects whether the Events checkbox is checked by default when creating a new community.||true|
|jive.event.default.enabled.project||Specifies whether Events are enabled for new Projects by default. This affects whether the Events checkbox is checked by default when creating a new project||true|
|jive.event.default.enabled.socialGroup||Specifies whether Events are enabled for new Social Groups by default. This affects whether the Events checkbox is checked by default when creating a new project.||true|
|jive.event.default.enabled.userContainer||This property has been deprecated.|
|jive.event.description.required||Makes the Event Description field required for all events upon creation or update.||false|
|jive.event.eventAccess.closed.enabled||Makes the "Closed" event access level available. Closed events are visible by anyone who can see events in a particular place, but can be attended only by those users who have been invited.||true|
|jive.event.eventAccess.covert.enabled||Makes the "Private" event access level available. A private event can be viewed and attended only by the event's creator, contacts and invitees. Administrators of the place where a private event resides can also view/attend the event.||true|
|jive.event.eventAccess.open.enabled||Makes the "Open" event access level available. Open events are visible and can be attended by anyone who can see events in a particular place.||true|
|jive.event.eventType.required||Makes the Event Type field required for all events upon creation or update||false|
|jive.event.eventTypes||Specifies the available event types, in a pipe-delimited, "key=value" format.|
|jive.event.locale.filtering.enabled||This property has been deprecated. Filtering by locale is not currently available.|
|jive.event.location.required||Makes the Location field required for all events upon creation or update||true|
|jive.event.upcoming.maxResults||Specifies the maximum number of results that can be returned in an Upcoming Events Widget||100|
|plugin.events.ics.hostname||Specifies the hostname contained within an event's iCalendar (ICS) file, which is available for download while viewing the event, or attached to Event invitations sent via email.||localhost|
|plugin.events.ics.id||Specifies the identifier for an event's iCalendar (ICS) file.||-//Jive Software//Jive Events//EN|
Under the right circumstances, users can integrate their third-party Calendar, such as Outlook, with events within Jive. This integration is possible with any iCalendar- compatible system.
With no additional configuration, a user can add an event to their calendar simply by clicking the Add to Calendar link in the Event action sidebar. This option, however, does not provide for ongoing integration between Jive and a user's calendar.
A more robust version of iCalendar integration is possible with Advanced Email enabled and properly configured. Once this configuration is in place, a user that receives an event invitation via email will see a meeting invite. The invited user can then mark their attendance within their iCalendar-compatible client, and the response will be sent as an email back to the Jive instance, and the user's attendance will be reflected within the event within Jive.
Note that it is up to the individual user to set their preferences to receive event invitations and updates via email. This is done by electing to receive emai for Action Alerts and Notifications.