2. What’s New in Kinetic Task 3.0 Ben Christenson

3. 3 About Me  Ben Christenson  Employee at Kinetic Data for 13 years and a member of the Product Development team for the past 7 years  One of the primary architects and developers for Kinetic Task  Longest trip away from 7 month old daughter Charlie

4. 4 About You  Who here uses Kinetic Task?  What are you using it for?  What would you like to be using it for?

5. 5 What was Kinetic Task?  Packaged with Kinetic Request  Workflow automation engine 1. Accepts input from Kinetic Request 2. Leverages “task handlers”

6. 6 What is Kinetic Task 3.0?  Packaged with Kinetic Request and independently  Workflow automation engine 1. Accepts input from any data source 2. Leverages “task handlers”

7. 7 What’s New In Kinetic Task 3.0  Opened up to allow any external source to start a task tree  Source Roots  Tree Management  Kinetic Security Language (KSL)  Pure Java!  What has improved?  Installation  Consoles  API

8. 8 What’s New: Source Roots  Source roots  Initiate a task process  Provide data used by the process  Examples:  Kinetic Request  ITSM Incident  Salesforce  Oracle Identity Management What’s New Source Roots Tree Management KSL Pure Java! What’s Improved Installation Admin Console Task Management Console API

9. 9 What’s New: Source Roots  There are two types of source roots  Standard: task handler provides tree data  Dynamic: “consumer” plugin provides tree data  Differ in what is available in the Task Builder menus

10. 10 What’s New: Source Roots  Standard  @source[‘Name’]  @source[‘Group’]  @source[‘Id’]  @results[‘Start’]  Dynamic  @answers  @dataset  … (Dynamic) (Standard)

11. 11 What’s New: Source Roots  When should a dynamic source root be used?  Already available (Kinetic Request, Kinetic Survey)  Dynamic source bindings  When should a standard source root be used?  Anytime else

12. 12 What’s New: Source Roots  Preparing a source root 1. Write task handler (or consumer) to retrieve information 2. Configure source root to start task processes 3. Register the source with Kinetic Task StrategyExample API CallOracle Identity Management remote task Remedy FilterCreate KS_TSK_Seed record when an Incident is created PollerNon-modifiable system

13. 13 What’s New: Source Roots

14. 14 What’s New: Tree Management  Previously used Request for Management*  Tree Management Console  Open task builder  Edit/Delete  Import/Export * Kinetic Request will continue to manage its trees. What’s New Source Roots Tree Management KSL Pure Java! What’s Improved Installation Admin Console Task Management Console API

15. 15 What’s New: Tree Management

16. 16 What’s New: Tree Management  New Term: Source Group  Categorization of trees for a given source  Different source roots, different source group  May be “composite”  Examples:  Kinetic Request: ACME Catalog > VPN Access  Remedy: KS_SAMPLE_Incident

17. 17 What’s New: KSL  Kinetic Security Language  Access control strategy  Same technology as task connectors  Used by Task 3.0 to restrict API access What’s New Source Roots Tree Management KSL Pure Java! What’s Improved Installation Admin Console Task Management Console API

18. 18 What’s New: KSL  Origin of KSL  Need to restrict access to certain resources  Wanted to avoid managing users in yet another place  Few clients want to secure things in the same way  Generic “No access” messages aren’t helpful  So how does it work?

19. 19 What’s New: KSL  Define policies (name, rule, message)  Rules are evaluated like a task connector  Messages are evaluated like a task parameter  Apply policies to a resource  A resource may have multiple policies  Evaluate Policies  When a resource is accessed, evaluate each applied policy

20. 20 What’s New: KSL Sample Rules Restrict to an IP range Restrict using secret token Restrict by time of day

21. 21 What’s New: KSL  Benefits  Flexible – can hook up security to Remedy, AD, or anything else  Messages – can be verbose or terse  Portable – easy to reuse, or share on Community  Where will you see KSL in the future?  Restricting access to console functionality  Kinetic Request service items  Kinetic Calendar private calendars

22. 22 What’s New: Pure Java!  Removed dependencies on the JNI  Fully 64bit compatible  Does not require any.dll/.so files  What does that really mean? What’s New Source Roots Tree Management KSL Pure Java! What’s Improved Installation Admin Console Task Management Console API

23. 23 What’s New: Pure Java!  Task runs on anything  Even a Mac!  Simplified install  No environment changes

24. 24 What’s Improved: Installation  Self-installing.war file replaces installer executable  Installs on new systems  Upgrades existing systems  Skips current systems  Configurable data directory  Install or upgrade in less than 5 minutes with a running Tomcat What’s New Source Roots Tree Management KSL Pure Java! What’s Improved Installation Admin Console Task Management Console API

25. 25 What’s Improved: Installation

26. 26 What’s Improved: Admin Console  Removed logging tab in favor of direct links:  Manager Log  Engine Log  Environment Log  Worker Logs (zip)  All Logs (zip) What’s New Source Roots Tree Management KSL Pure Java! What’s Improved Installation Admin Console Task Management Console API

27. 27 What’s Improved: Admin Console

28. 28 What’s Improved: Task Management Console  Modified to support multiple source roots  New Feature: List recent executions Remember, Kinetic Request executions can be searched by KSR. What’s New Source Roots Tree Management KSL Pure Java! What’s Improved Installation Admin Console Task Management Console API

29. 29 What’s Improved: Task Management Console

30. 30 What’s Improved: API  Existing API used to create deferral triggers  Expanded to support start triggers  Used to trigger source root tree executions What’s New Source Roots Tree Management KSL Pure Java! What’s Improved Installation Admin Console Task Management Console API

31. 31 What’s Improved: API  Three options  Web Services (SOAP)  REST  Remedy Form (KS_TSK_Seed)  Same methods for each option  Create Start  Create Deferred

32. 32 What’s Improved: API  Create Start - Initiates a task process  Example: Start the task process to handle a new incident ParametersValues Source Name Remedy Source Group KS_SAMPLE_Incident Source Id INC00000001 Tree Name User Created Results Message

33. 33 What’s Improved: API  Create Deferred - Updates or completes a deferred task  Example: Completes a deferred approval node ParametersValues Action Complete Token AG005056960051rJQmUQPmxIWAUXYJ Results Approved MessageRequest approved by Ben Christenson on March 1st.

34. 34 Summary  Handlers don’t change, Trees don’t change  Dirt simple installation  Now provides automation for any data source  Add a new source root in three simple steps  Kinetic Security Language (KSL)  Powerful new strategy for security policies  Increased adoption in all Kinetic products

35. 35 Conclusion  Questions?  Contact Information:  Ben Christenson  ben.christenson@kineticdata.com  651.556.0937