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


Minor bug fixes that were discovered in v3.1.1, and enhancements to the tree builder. This version is compatible with Kinetic Request v5.1 (with applied Task 3.0 compatibility package, available here) and other external data sources.


Remedy AR Server v7.0.0 or greater
Web Application Server

Java Servlet Container (Servlet spec 2.4, JSP spec 2.0)

  • Examples
    • Tomcat 5.5+

    • WebSphere 7.0+ 

    • WebLogic 9.0+

Java Java 1.6.0 or greater - either 32-bit or 64-bit

Change Log

Bug Fixes:

  • KT-282, Incorrect binding on task builder menu for Kinetic Request.
  • KT-365, A handler cannot be in two categories, and cannot have multiple handlers or groups.
  • KT-424, Consumer management is not cluster aware.
  • KT-492, Connectors that fail are processed terminatively.
  • KT-528, Loop tails break when processed terminatively.
  • KT-596, Tree export mangles new line characters.
  • KT-597The handler info type was not being updated if it was changed when the handler was imported to overwrite an existing handler.
  • KT-598, The ArsModels library fails when retrieving records from a join form without a Modified Date (6) field.
  • KT-599, The ArsModels library fails when an entry is deleted as part of create/modify workflow.
  • KT-603, The engine adapter should chunk through instance records if the Remedy server max records on getEntry limit is returned.
  • KT-640, Tree export doesn't escape variable substitution in strings.
  • KT-642, Update the task builder to v4.0.0 to resolve several bugs
    • KT-368, Line breaks in connector expressions are being removed.
    • KT-641, When using IE > 9, new nodes do not get saved with the tree.
  • KT-647, Display messages are not working after handler file import.
  • KT-649, The time zone is being detected correctly because the value is being stored with a leading and trailing space.
  • KT-650, Security fix.
  • KT-651, Prevent caching of trees on the tree configuration console.
  • KT-652, Security fix.
  • KT-653, Security fix.
  • KT-654, Security fix.
  • KT-655. Security fix.
  • KT-656, Security fix.
  • KT-657, Turn off auto complete for password inputs.
  • KT-658, Change sensitive input fields to password type.
  • KT-659, Security fix.
  • KT-660, Remove unnecessary fields from setup screens.
  • KT-661, Move the admin user properties to a separate form.
  • KT-662, Default the admin user name, and add placeholder text for the pasword.
  • KT-663, Trim leading/trailing whitespace from selection criterion field.
  • KT-664, API Access policy rules is misspelled.
  • KT-665, Change the Utilities Create Trigger handler to not be a system control handler, as multiple bugs exist because it is a system control handler.
  • KT-666, The ArsModels library should not log queries matching more than the Remedy server max records on getEntry limit on WARN level.
  • KT-667, Remove console appenders from the log4j.xml configuration file.
  • KT-669, Cannot overwrite tree on import when using IE8 or IE9.
  • KT-670, Task handlers with apostrophes in the description cause errors in tree builder when using IE8.
  • KT-678, Instances created in parallel threads are not accessible once process is joined.




Download the installation package and extract to a temporary directory.  Then follow the instructions in the installation guide.



If you are going to use Kinetic Task with Kinetic Request 5.1.x and haven't already applied the Request 5.1/Task 3.0 Compatibility Pack, you will need to install it after you've upgraded Task to version 3.1.2.  Instructions can be found here.


Deploying the Web Application - Using Tomcat as an example

  1. Download and unzip the install package.
  2. Stop the Tomcat service on your web server.
  3. BACKUP your existing kineticTask directory located at <tomcat_home>/webapps/kineticTask.
  4. Copy the kineticTask.war file from the extracted install package and paste it into the <tomcat_home>/webapps directory.  If you are using WebSphere or WebLogic, instead use the .war/.ear file in the associated subdirectory, which includes configuration items specific to those servers.
  5. Clear the cached JSP files.
    For Tomcat, delete the entire <tomcat_home>/work/Catalina/localhost/kineticTask directory.
  6. Delete the existing web application located at <tomcat_home>/webapps/kineticTask.
  7. Restart Tomcat and the web application archive will automatically deploy.


Running the Web-based upgrade application


  1. Open a web browser and log into the Web Admin Console.  The Admin Console's address will be something like http://<webserver>:<port>/kineticTask/AdminConsole.  You will see the following screen: 
  2. Click Continue.


  1. Enter your Remedy server connection information and click Continue



  1. Click Continue when prompted to upgrade.


  1. Click Continue to confirm that you want to upgrade.


  1. Wait while the application is being upgraded. 

  1. Click Continue once the Remedy portion of the upgrade is complete to launch the Task Admin Console.



  1. Click the Edit Properties button.



  1. Update the application properties accordingly.  The properties are listed below by section.

Note: all fields marked with an asterisk (*) are required.

Application License

  • Application License - the Kinetic Task License key that was provided to you by Kinetic Data


Remedy Server Settings

  • Server Name -  the name of your Remedy server.  This should either be the server’s DNS name or IP address.  The value you enter here must match the value used to generate the Kinetic Task licenses.

  • TCP Port - the Remedy server’s TCP Port.  If your Remedy server uses portmapper, enter 0.

  • Username - the Remedy user name that the task engine will use to log in and process tasks.

  • Password - this password for the aforementioned username


Kinetic Task Engine Settings

  • Enable - check this box to enable the task engine and display other settings for it.
  • Sleep Delay - the number of seconds the task engine will wait between checking for new triggers to process.  This value is only used if the Max Threads setting is set to 0.
  • Max Threads - indicates the number of worker threads the task engine will use to process triggers. If set to 0, the task engine will only use one worker thread in a synchronized manner, meaning it will process all the triggers with one worker thread, then sleep for the specified duration as indicated by the Sleep Delay parameter, then wake up and process the new triggers. If this value is set higher than 0, that many worker threads will be available to process triggers simultaneously. More threads require more memory and higher CPU utilization.
  • Query Limit - the maximum number of triggers that will be processed during each wake cycle. If there are more triggers than the value of the query limit, the remaining triggers will be processed in future wake cycles.
  • Query - allows the user to customize what trigger records are selected by a specific engine. This is typically only applicable in multiple task engine environments.
  • Cache Handlers - allows the task engine to cache the task handler files in memory. Changes to the task handler file will not be applied until the web server is restarted. This provides a performance improvement over loading the task handler file every time it is needed.
  • Outgoing Mailbox Unique ID - used to identify a specific Remedy mailbox to use when generating system emails. This value corresponds to the 'Unique Identifier' field on the AR System Email Mailbox Configuration form. If this value is left blank, the default outgoing mailbox will be used.
  • Notify Process Owner - tells the task engine to send an email to the process owner when an error occurs with that process tree. The process owner is configurable for each task process tree by clicking the 'Configure' button in the Task Builder, and configuring the email address in the Author field.
  • Notify System Owner - tells the task engine to send an email to the system administrator when any error occurs in the task engine. When selected, a text input field will appear that will accept an email address, or a comma separated list of email addresses.


Default Logging Settings

  • Log Level - determines what level of detail the information is written to the log file.  The values are listed in order of detail from least (Off) to most (All).  A higher detailed value provides more logging information, but is also more resource intensive on your server.
  • Max Log Size - The logger is configured as a rolling file appender, which means that when the log file reaches the max size limit, it will be closed and a new file will be started.  This prevents the file from growing too large, and allows administrators the ability to delete old log data without having to stop the web server.


Configuration Administration Credentials

  • Config Admin User - the configuration administrator username.  The default value is admin.
  • Edit Password - check this box to display the Admin Password field so that you can update it.
  1. When you have finished updating the properties click the Update Properties button to save them.

  2. You should see a green confirmation message letting you know that the properties have updated successfully.
  3. That's it.  You're done with the upgrade.


Don't forget to install the Kinetic Request 5.1/Task 3.0 Compatibility Pack if you will be using Task 3.1.2 with Request 5.1.x, and haven't already applied it.