jiveclientconfiguration.json - Definition

The following document is meant to provide some insight as to the options/availability for your jiveclientconfiguration.json file. For any questions about any of this information, please just comment on the document.

Used in conjunction with persistence to define the persistence strategy.Example: mongodb://user1:password1@localhost/test

ignoreExtensionRegistrationSource

(optional)

A flag that will tell the SDK to not bother trying to validate against the Add-On Registry.

(true | false, default: false)

skipCreateExtension

(optional)

false / (true : default)

packageApps

(optional)

Used to configure your project for packaged apps at a global level (i.e. --apphosting="jive")

Note: a new feature added in Jive SDK 0.2.17 in the Tile definition.json

"registerTileWhenPackaged" : true

When added to a definition.json located in a tile directory (i.e. /tiles/TILE_NAME/definition.json) in your project, it will force the SDK to leave the register/unregister URLs on a Tile even when the Tile is apphosted inside Jive. This is good for scenarios where you want to notify external systems of the Tile installation, but runtime dependencies are not required.

packageAddOnConfigure

(optional)

Use this option if you want to package your addon configuration experience as well. See: meta.json > config_url

Values:

true - This will assume that your configuration path is resolved to the /public directory in your project.

(string) - A directory path that is appended to /public that gets prepended to the config_url value.

For example: config_url = /abcdef/configure, with a value of /tiles the output path would be /public/tiles/abcdef/configure

Note: A new feature added in Jive SDK 0.2.17 in the Tile definiton.json

"suppressTileDefinition" : true

When added to a definition.json located in a tile directory (i.e. /tiles/TILE_NAME/definition.json) in your project, it will omit that Tile from the /definition.json generated for the extension. It's a handy feature if you are trying to single source all your tile HTML/CSS/JS code into a single directory without having to manually manage.

suppressAddonRegistration

(optional)

A flag that will tell the SDK to configure the Add-On extension.zip to not force a registration challenge when installed. This is used primarily for simple Jive Apps. (true | false, default: false)

extensionInfo.uuid

(optional, recommended)

Locks in your Add-On UUID from ever-changing between builds and/or setting the ID for a specific app.

Your UUID is very important to lock in once you start real development, especially when it comes to signing add-ons (see jiveServiceSignature, below)

Note: You will need to re-run the build process for the changes to take effect.

extensionInfo.name

(optional, recommended)

Specify your app name that is seen in the Add-On Registration Screen.

extensionInfo.description

(optional, recommended)

Specify your app description that is seen in the Add-On Registration Screen.

extensionInfo.jiveServiceSignature

(optional)

Use this field to save the jiveServiceSignature from the Add-On Registration to complete the signing of your Add-On

To obtain the jiveServiceSignature, Ctrl+Click (or Cmd+Click) on the Upload button in Add-On Registration to get the screen to sign your package. You will need to paste in the Add-On UUID from extensionInfo.uuid. Once you get the value, paste the signature pack into this property.

If you have Add-On specific configuration you wish to do at the point of Add-On installation. Provide the URL to the your experience (defined in your Add-On), and Jive will instruct the Administrator to configure before using.

Default: %serviceURL%/configure

extensionInfo.health_url

(optional)

A URL that Jive can connect to to determine health and availability of the associated cloud service. See Add-On Health Check Format for detailed information.

extensionInfo.website_url

(optional)

The URL of a web site or page presenting information about this Jive Add-on or the company that developed it.

extensionInfo.community_url

(optional)

The URL of a web site or page where a user could learn more about, discuss, ask a question about, or report a problem with this Jive Add-on.

extensionInfo.author

(optional)

The name of the add-on developer

extensionInfo.author_affiliation

(optional)

The name of the add-on developer's company/affiliation group

extensionInfo.author_email

(optional)

An email to contact the developer

extensionInfo.support_info

(optional)

This may be either a URL or an email address where a user of this Jive Add-on can request assistance.

extensionInfo.info_email

(optional)

An email address where a user can request detailed information about this Jive Add-on, prior to using or installing it.

extensionInfo.tags

(optional)

The set of tags that are associated with the integration. These are defined by the partner.

extensionInfo.overview

(optional)

The name of an HTML file in /data that will contain a detailed overview of this Jive Add-on.

extensionInfo.install_instructions

(optional)

The name of an HTML file in /data that will contain a detailed explanation of steps required to install this Jive Add-on. This may not always be needed, but if we are expecting the Jive admin to deploy some kinds of companion network service for this Jive Add-on to work, this really needs to be here.

extensionInfo.eula_filename

(optional)

The name of an HTML file in /data that will be presented to the user as a legal agreement before they are permitted to install this Jive Add-on.

extensionInfo.privacy_policy

(optional)

The name of an HTML file in /data that will be presented to the user explaining the privacy policy concerning any information provided to this Jive Add-on or the network services it communicates with.

extensionInfo.screenshots

(optional)

An array of strings, up to 5. Each value is the name of an image file in /data that contains a 600 x 400 screen shot or preview image.

{add-on name}-screenshot_{screenshot #}.png

my-custom-config

(optional)

When developing your Add-Ons, it is best to centralize your configurations under a single block This allows ALL of them to be easily passed back and forth within your Add-On as a single object. You can make as many extra blocks as necessary, they can always be referenced like this:

jive.service.options['my-custom-config']

or for nested parameters such as my-custom-config.test.parameter, use: