Skip to main content
Kinetic Community

Resources

This page provides the Documents related to Kinetic Task
Topics
  • ArsModels is a Ruby library for creating, retrieving, updating, and deleting records in Remedy.  It is generally used for writing Task Handlers that interact with Remedy.
  • Identity stores are databases or directories that store user and group information.  By default, Kinetic Task stores user and group information in its own local database.  Most organizations have some type of directory service that already contains their user and group information.  Using the appropriate identity store authenticator, Kinetic Task can use the information held in these external stores rather than having to duplicate the information within Kinetic Task.
  • The Kinetic Task ARS Shim application allows Remedy ARS to initiate communication to the Kinetic Task engine.
  • This page includes multiple samples of Kinetic Security Language (KSL) policy rules and messages that can be used within Kinetic Task.
  • The Parameter Value Reporter gives the ability to search all the trees within a Kinetic Task instance and return the parameter values of a handler(s). A user defined keyword will be entered and this utility will search all the trees. If a node contains the keyword, this utility will record the parameters and its values, creating a CSV file.
  • This page includes links to various resources that are helpful in learning and understand Ruby, the language used in Kinetic Task tree connectors, node parameters, and handlers.
  • The Test Harness is a utility that allows you to test task handlers without importing them into your task environment and adding them to a task tree.  This way handlers can be tested independently and changes can be made more swiftly.
  • In Kinetic Task v3.2 and v4.0 we removed the ability to use erb tags (embedded ruby tags) in connector expressions. The Tree Converter is a utility that does its best to automatically convert the connector expressions it can. It essentially scans every tree in the Task environment and scans each connector to see if it matches certain patterns it can convert.  Connectors that match these patterns can be converted automatically. For connectors that do not match, it provides a way to define the replacement expressions and update them in batch without going into each tree and making modifications.