Platform Glossary

Anne Rosebery

  • Agent: The agent is a portion of the platform that sits inside the firewall to execute calls that must take place internally (handlers, bridges) for kinops systems that connect to on-prem systems.
  • API: API stands for Application Programming Interface. An API is a software intermediary that allows two applications to talk to each other.
  • Attribute: User defined metadata for Spaces, Kapps, Users, Forms, Categories, Datastore Forms, or Teams. Also sometimes used as the name for the defined values in a Bridge Model.
  • Bridge: A bridge is a configuration of a simple web application that connects to a data source to read information that can be used to populate data in submissions. The data source may be an external database or web application, or it may be for a specific Form or Kapp
  • (Bridge) Mapping: A bridge model mapping is where the bridge data source is mapped to the bridge model properties. This tells Kinetic Request CE how to get the raw data from the data source, and how to present it to the page when rendering the submission form.
  • (Bridge) Model: A bridge model is simply a type of object that is used in Kinetic Request CE forms that is populated from a data source using a bridge to read from that data source. The bridge model allows the object to be assigned properties with normalized names rather than using cryptic database column names, or some other naming convention known only to the developers of the data source application.
  • Bridged Resource: A defined use of a bridge within a Form.
  • Bridgehub: Bridgehub is the platform component that provides the connectivity between the front-end of the platform and other systems. This is what provides that multi-system integration in Request. There are bridges available today from everything from your local Request system to your racks at RackSpace, and all of the bridges come preinstalled and ready to configure with your account information for each of your integrations.
  • Bridges: provide way for your form builders to interact with a read-only interface to any system with an API in a low-code way. Only platform admins need to understand what connects to what and how to create the queries, and the queries only need to be set up the once to be used any number of times. And if the data source changes, the references in the individual items don't need to be updated, just the once central resource.
  • Bundle: Bundles provide the interface needed for building out an application. Bundles wrap the forms defined in the Management Author Console and extend functionality your organization needs to build an intuitive, engaging user experience. Bundles typically include items such as theming/branding, search, alerts, portals, and other widgets.

    Bundles use standard web technologies including HTML/JSP, CSS, Javascript, and can be developed using a text editor or IDE. The default bundle uses Bootstrap, but you can include any framework or library of your choosing.

    Bundles often need server-side access to information about the Kinetic Application including items such as form names, paths to resources, attributes, the authenticated user, etc. This is where the Bundle/Java API comes in. Bundle authors can embed information into their pages through a simple syntax and use helpers to format and present information as needed.

    Bundles are deployed to the Kinetic Request CE web application’s /app/bundles directory, located within a directory named for the slug of the Space where the bundle is to be used. For instance, a bundle for the the Acme space, which would normally have the slug value acme, would be located at /app/bundles/acme/{bundle-name}.

  • Bundle (javascript reference): Bundle is a helper object designed to be used in javascript applications. The bundle object provides a number of static methods that are automatically included with each request
  • Connector: The connection between two nodes within a workflow. May or may not contain logic. If logic is applied, the connector path is only followed if the statement evaluates to true
  • Datastore: Datastore Forms allow administrators to define and build referential datasets. These forms can be configured with compound (multi-field/property) indexes and unique indexes, which provide efficient query support for large datasets. Example datasets: Assets, People, Locations, Vendors, or Cities and States."
  • Datastore Submission: A datastore submission represents a submitted instance of a datastore form.
  • Filehub: Filehub is the platform component that stores and secures the files attached to Request forms. You can choose to store these files in several ways, including local disk and remote amazon drives.
  • Form: Administrators of the system can create end-user experiences that collect data using Forms. Forms are a collection of fields that collect data that end users submit (submissions). Forms can have multiple pages, and a variety of different field types (checkbox, radio button, text, etc..)
  • Handle: The last 6 characters of the full submission Id of a record. Provided as part of the record to allow for a more human readable identifier for the submission.
  • Handler: A handler is a small program that is able to perform a unit of work. It may take some input values, and usually returns one or more output values.
  • Identity: The identity object represents the user that is currently using the application.
  • Integration: Any connection between the platform and a third party system. This includes bridges, webhooks, and task handlers.
  • K function: The Kinetic JavaScript library revolves heavily around the K function, which is used as a selector for runtime objects such as the current kapp, form, or fields on the page. The results of this selection will be Kinetic API objects that can be interacted with.
  • Kapps: Kapps (Kinetic Apps) are a collection of Forms within the Kinetic Request CE System. Kapps have their own categories, webhooks, forms, and permissions. Typically a Kapp will represent a single end user experience. Example Kapps include a Service Portal or Work Order System.
  • KSL: Kinetic Security Language; A scripting language created for writing and managing security policies.
  • Memberships: Memberships are a relationship between a Team and a User.
  • Node: A representation of a unit of work within a workflow; a handler or routine.
  • Qualification: Qualifications represent search queries that can be used to return data from a bridge. Examples of Qualifications include All Active Employees, or Location by Site number. Qualifications are an abstract representation of a query so they only include a name, a setting for number of results (single or multiple), and any parameters

    Bridge Model Mapping Qualifications define how a Model Qualifications is map to a query for a target systems. Mapping Qualifications are typically made up of static search criteria and parameters that are passed when a search is executed.

  • REACT: A JS library used to build UIs; optimal for fetching rapidly changing data that needs to be recorded.
  • Request: Request is the platform component that allows you to build powerful and beautiful front ends for your customers. It contains a drag and drop form editor where you can easily construct the forms you wish to present your users, but also supports the complexities of multi-system integrations, multi-tenancy, and workflow integration on all it's components.

    You may also see this referred to as Request CE, Request Core Edition, CE, or Core Edition. The platform is built with a version of Request (CE) that is entirely our own creation, unlike our previous versions (RE or Remedy Edition) that relied on Remedy to be the platform.

    Request is the point of connection in the platform where Task, Filehub, Bidgehub, and Request itself all come together to provide the customer with the optimal user experience.

  • Routine: A routine is a tree without a specific source with defined inputs and outputs, that is available globally and can be used to build processes just like any handler
  • Security Policy Definitions: Security Policy Definitions allow administrators to secure the system in a very specific way. Security Policy Definitions have a Name, Type (Form, Kapp, Space, etc…) and Rule. The rule is a javascript expression that should return either true or false and is evaluated at run time when a resource is being accessed.
  • Space: A Space represents a tenant within the Kinetic System. Spaces are a collection of Users, Kapps, Forms and all other Kinetic Objects. No data in the Kinetic System is shared between Spaces.
  • Subform: A form/submission that is loaded into the current page
  • Submission: A submission represents an instance of a form that contains field values.
  • Submission Activity: Submission activities are a way to attach additional information to a Submission, typically with the purpose of exposing some details to the original submitter. Often they are used in a Kapps bundle in order to build up a “Submission Details” view.
  • Task: Task is the platform component that allows you to build and execute workflows. It contains a drag and drop workflow editor where you connect code snippets together to build your flexible and powerful workflows. It also contains the engine that runs to execute these workflows and handle errors, providing fast workflow processing and robust error handling for all your workflow needs.

    There are hundreds of these code snippets, called handlers, already built and available for use. These can connect you with everything from your local Request system to your AWS provisioning service and everything in between. Also, if you desired integration has an API but no handlers currently available, there are instructions available for you to be able to build your own.

    While Task can be used stand alone and is a powerful workflow engine without the rest of the platform, with the platform, it allows you to integrate that powerful workflow into your beautiful front end experience for an optimal user experience."

  • Teams: Teams are a way to group individuals within your organization that are working on common projects.
  • Tree: A tree is a collective process of small units of work called nodes that represent the usage of task handlers. Generally refers to processes that use a specific source.
  • Users: Administrators can create Users within the Kinetic system to distinguish between users of the system.
  • Webhook: A webhook is a user-defined HTTP callback to a third-party application that is fired when some predetermined action occurs. Data that corresponds to the action, such as a form being submmitted, will be sent to the webhook URL as an HTTP Post action.
  • Webhook Jobs: A webhook job is an instance of a webhook tied to a specific record (Submission, Form, User) that was created due to an action occurring on the record.
  • Workflow: A tree or routine. A process that does the work for a submission.