Skip to main content
Kinetic Community

Application Glossary

Overview

Definitions of terms specific to Request CE.

Glossary

Space - A logical partition used for some types of multi-tenancy.  Spaces within an instance of the application live on the same database but contain their own data, permissions, and users.

Kapp - A collection of related forms within a Space. A service catalog is a typical example of a Kapp.  Kapp stands for "Kinetic Application".

Bundle - Defines the user experience for a Kapp including theming/branding and functionality required for end-users to interact with an application.  A bundle consists of files such as JavaServer Pages (JSPs), Javascript, CSS, images and other resources required for a web application.

Form - Collection of fields, text and possibly javascript and CSS that present a request to a customer.

Slug - URL-safe, friendly name representation used by forms and other resources within the application. Slugs are unique within a Kapp.

Attribute - An extra piece of data that defines something about the object it is attached to. For example, an attribute could define the icon for a form

Submission - One instance of a Form.

KSL - Stands for Kinetic Security Language. KSL is used to define permissions on forms, and is used in conjunction with javascript.

Webhooks - User defined HTTP callback. Most often used to communicate with Kinetic Task, but could send information based on actions in the application to any web service that exposes a RESTful interface.

Form Types - Types can be used to put forms into logical groups. The most common are Service, Template, and Approval.