Skip to main content
Kinetic Community

Glossary

The Kinetic Task Glossary includes brief descriptions of commonly used terms as well as references to community pages with additional details.

Terms

ArsModels ArsModels is a library used for creating, retrieving, updating, and deleting records in Remedy.  It is most frequently used in the writing of Task handlers that interact with Remedy.  For more information about ArsModels, see the ArsModels reference guide.
Binding Variable Binding variable is a term used to refer to the dynamic values exposed within Kinetic Task (such as @results, @source, etc).  Binding variables always begin with the @ symbol and are most frequently used in the Kinetic Task Builder or referenced in the node.xml file of a task handler. 
Branch A branch refers to a collection of task nodes that share a common ancestor node.  The entire task tree is technically a branch (all nodes follow a path of execution that originates at the start node), however the term is more frequently used to discuss specific paths of execution.  For example, a start node may be linked to two other nodes where one connector progresses execution if the requester is a manager and the other connector progresses execution if the requester is not a manager.  In this case there is a branch dedicated to processing manager requests and a branch dedicated to processing non-manager requests.  Further, the branch processing manager requests may have branches of its own, such as a branch for processing high priority manager requests and a branch for processing low priority manager requests.
Connector  
Consumer A consumer is a small module, similar to a task handler, that can look up dynamic data and expose additional variables within a task tree.  Consumers are required for dynamic source roots and have two major functions.  The first function is to build a list of pre-defined variables available in the Kinetic Task Builder for a specified source group value (for example, the Kinetic Request consumer looks up the dataset, template attributes, and questions associated to the template referenced by the source group value).  The second function is to retrieve the pre-defined variable values for a specified source id value, which are then used by the task engine during tree processing (for example, the Kinetic Request consumer looks up the answer for a specific submission).
Defer  
Deferral Token  
Deferring Node  
Delegate System A delegate system is an application or system that the Kinetic Task engine can delegate work to.  This typically means that a task handler starts a process in another system and then defers, waiting for the application to complete the work and respond that the process is complete.  A common example of a delegate system is Kinetic Request when it is used for approvals and work items.
Dynamic Source Root A dynamic source root uses a consumer to retrieve the source data used in task trees for that source.  The data can then be referenced as binding variables available listed in the pre-defined variables menu of the task builder.  In general a source root should only be made dynamic if the source data is too dynamic or too complex for a data retrieval task handler to be practical.  For more information about source roots, including the differences between a standard and dynamic source root, see the Getting Started with Source Roots article.
ERB  
Exception  
Execution  
Handler  
Handler Categories  
Handler Pausing  
Instance  
Loop  
JRuby  
Join  
Junction  
KSL  
Node  
Node Message  
Node Parameters  
Node Results  
Node Visibility Node visibility refers to the "Visibility" option presented when configuring a node in the Task Builder.  The value of this property is not used by the task engine itself, and may have different effects depending on the source root associated to the Tree.  As an example, the Kinetic Request source root uses the visibility property to determine whether the task should be listed when viewing submission details.
Policy  
Policy Message  
Policy Rule  
Policy Type  
Pre-defined Variable  
Process  
REST REST is an communication style that utilizes simple, lightweight HTTP calls rather than more complex mechanisms associated with technologies such as RPC or SOAP.  Just about every language and environment has the ability to communicate of HTTP, and REST is intended to be simple enough that it can be consumed without the need for complex libraries or code.  For more information about the Kinetic Task REST API, see the Web Services (REST) api reference page.
Ruby  
Selection Criteria  
SOAP SOAP is a protocol that utilizes formatted XML "messages" sent over HTTP.  Kinetic Task offsers a SOAP based web service API mechnism.  For more information about the Kinetic Task SOAP API, see the Web Services (SOAP) api reference page.  For more information about SOAP, see http://www.w3.org/TR/soap/.
Source Application  
Source Group  
Source Root  
Standard Source Root A standard source root uses one or more task handlers to retrieve the source data used in task trees for that source.  The data can then be referenced as a return value of the data retrieval task handler.  If source root data is too dynamic or too complex for a task handler to be practical, it may be necessary to implement a dynamic source root.  For more information about source roots, including the differences between a standard and dynamic source root, see the Getting Started with Source Roots article.
Task  
Task Info  
Test Harness The test harness is a utility that allows task handlers to be validated and tested without needing to import and add them to a task tree.  This means that handlers can be tested independently and development changes can be made more swiftly.  For more information about the test harness, see the Test Harness resource page.
Tree  
Tree Pausing  
Trigger  
Trigger Message  
Trigger Results