Overview
The Kinetic platform is built to be extended. It has four core components:
- Kinetic Request: web display and a dynamic form builder
- Kinetic Task: workflow and automation
- Kinetic Bridgehub: API and integration coordination
- Kinetic Filehub: storing and retrieving files and attachments
We have integrated a lot of enterprise systems over the years. When we have access to a system to test an integration, we generally document it and publish it for customers and partners to use at no charge.
Kinetic Request
Kinetic Request is the web application people use, with predefined workflows built in. What each person sees can vary by policy or business logic. Someone making a request, approving one or fulfilling one all work in Kinetic Request.
Its data objects include Users, Teams, Forms and Kapps (groups of forms). These have defined relationships and can be arranged to fit most requirements. Policy-based security applies cascading permissions to each element, controlling who can view, create or update data and who can manage the system itself.
Forms are built with a drag-and-drop builder and take on the look of their theme. Themes are separate from the rest of the platform and can be customized freely. A theme is a collection of JavaScript, CSS and HTML, built with Java Server Pages (JSP) or a framework such as React or Angular.
Kinetic Request handles the plumbing a secure web application needs. It authenticates users through PIV/CAC cards, SAML or LDAP, and manages security, forms and data storage. It can also fire events when data changes. These events are webhooks that send the relevant data to a REST API. The most common use is to call Kinetic Task when a form is submitted, which starts a workflow.
Kinetic Task
Most applications need workflow, data processing and business rules behind the user interface. Kinetic Task is our workflow and business process automation engine. You build workflows in a drag-and-drop builder, and some teams use Kinetic Task on its own as integration middleware.
Workflows are configured as task trees, simple or complex. A task tree starts when something calls its API, usually a webhook from Kinetic Request. Each tree is made up of task handlers, the individual functions within a process. An administrator imports handlers into the system, and they are then reused across trees.
Handlers follow a standard package format that defines their inputs, outputs and actions. They are written in Ruby and can connect by any method, including REST, SOAP and direct database access. A library of prebuilt handlers covers common functions, with examples showing how to build your own.
Kinetic Bridgehub
Most applications need data from other systems, for example to fill a table or a drop-down list. Bridgehub works with Kinetic Request to fetch that data. It turns a query into a standard structure that Kinetic Request can process, and it is where connections to other systems are managed.
Bridgehub ships with adapters for common systems such as LDAP and SharePoint. Each adapter translates a query and its response into the expected format, and defines how to connect to, authenticate with, query and transform data from its target system. When a system changes or is replaced, you update or swap the adapter, and the forms and portals in front of it do not change.
Adapters follow a standard format and are written in Java. Administrators can build, test and import their own. Because adapters are isolated from the rest of Bridgehub, custom adapters do not get in the way of future upgrades, and we encourage customers to write them.
Kinetic Filehub
Filehub works like Bridgehub, but for files uploaded through Kinetic Request forms. Where files may be stored is often regulated, so Filehub uses adapters to work with external stores such as Amazon S3 or a local file server. Each adapter handles authentication to its file store and returns files in a standard format Kinetic Request understands. Administrators can build, test and import their own.
Built to be reused
Bridges and handlers are usually built once and reused many times. Once the integrations exist, people who understand the process, but not the code, can build on them without further development.
Skills required
- Kinetic Request works without any specialist skills. For a custom theme, navigation or complex form components, experience with HTML, CSS and JavaScript helps, as does React or Angular.
- Kinetic Bridgehub and Filehub need development only for adapters that do not already exist. That work calls for a Java developer.
- Kinetic Task needs development only for handlers and functions that do not already exist. That work calls for a Ruby developer.
Training and implementation
One of our core principles is to teach customers to do the work themselves. We offer consulting and are glad to help with a first implementation, but the most successful projects we see are the ones where the customer’s own team extends the system afterward.
Professional services
Our services team works with your project managers and developers to build integrations and other functionality. Engagements range from a full implementation to a specific piece of work such as layout or theming.