Skip to main content

IMPORTANT - Product End of Life Statement - IMPORTANT

Request RE, Survey, and Calendar 1.5 Support Ending December 31, 2020
Contact Kinetic Data Support with Questions
Kinetic Community

Application Architecture

  1. Last updated
  2. Save as PDF
There are two different ways to think about the design of Kinetic Survey and Kinetic Request.  The first is to look at how the individual elements interact that make up templates and service items.  The second is a view from the individual answers, and how they relate to individual surveys and requests.

Service Item/Survey Template View

Main forms with a brief description:

KS_SRV_SurveyTemplate – Details on the individual templates or service items

KS_SRV_ContentsElementHTML – Generated HTML code for the pages in the individual templates or service items

KS_SRV_SurveyQuestion – Question details

KS_SRV_SurveyQuestionChoice – Values for list choices

KS_SRV_Manager – Dialog form for Survey Author Console

KS_RQT_Manager – Dialog form for Service Catalog Console

KS_SRV_ElementDialog – Question and other page element dialog for both templates and service items.

KS_RQT_Task – Holds information about tasks related to service items.

Survey/Request Answers View

Major forms with a brief description:

KS_SRV_CustomerSurvey_base – Instance of this form is generated for each survey/request.  It holds all the attributes and basic data for each survey/request.

KS_SRV_SurveyAnswer – Individual survey/request answers.

KS_SRV_SurveyResult – All the answer viewers, and instance Ids for the individual answers.

KS_SRV_CustomerSurveyResults_join – Also known as “The Flattener”, this form has information from the base record, the template, all the answer viewers and the attributes.

Two main reporting forms:

KS_SRV_CustomerQuestionAnswerResults_join

KS_SRV_CustomerSurveyQuestionAnswerJoin

Kinetic Task Forms

Major Forms of the Task System

KS_TSK_Instance – One record created for each node on your task tree, per request submission. Holds both the return and deferred variables.

KS_TSK_Trigger – Records created in this form can both start a task tree process and restart a task process from a deferred node/instance.

KS_TSK_Trigger_Lock_join – Used to stop multiple Task Engines from processing the same tree instance.

KS_TSK_Tree – Holds the Task Tree which is represented as an XML string. It is related to a template by the Association ID.

KS_TSK_Def – Holds a Task Handler and relates to its authentication information. There is an attachment field that holds the imported handler.

KS_TSK_Exception_Handler – Every error/exception thrown by the system is recorded in this form. They are also viewable from the Task Management console.

Activity

Continue to Activity Four, review the application forms.