What's New in Kinetic Calendar 2.0 Jack Boespflug Kinetic Data

2 About Me  Jack Boespflug  Employee at Kinetic Data for 8 years  Member of the product development team for 6 years

3 Separation from Remedy

4  All Remedy forms and workflow have been removed  Nothing to install on the Remedy server

5 Separation from Remedy  Advantages:  Simplicity  Eliminate delays from other projects  ITSM implementation  Service Catalog implementation

6 Review of Calendar Terms

7 Calendar  A container that defines the types of events that will be displayed on the page.  Indicates what view to use on initial page load – Day, Week, Month  Example: Change Requests

8 Event Type  Term that describes the properties and details about the data it retrieves.  In simple terms it is a field mapping to a Remedy form.  A calendar consists of one or more event types.  Example: Scheduled Changes

9 Event  An entry from the Remedy form that was configured in the Event Type.  Displays in the day/time slot that represent the values from the field mappings.

10 Data Sources

11 Data Sources  A system that contains the data you want to display. – Examples: Remedy Exchange Sharepoint

12 Data Source Adapters  A data source adapter is a module that retrieves data from a specific type of system.  Each type of system requires an adapter

13 Data Source Adapters Remedy Remedy on Demand Exchange Sharepoint Kinetic Calendar Remedy Remedy on Demand ExchangeSharepoint

14 Data Source Adapters  Calendar 2.0 includes the following adapters:  Remedy  Supports Remedy server version 7.0+  Supports 64-bit JVM as it uses the pure Java API  Supports Remedy On Demand

15 Data Source Adapters  Calendar 2.0 includes the following adapters:  Microsoft Exchange  Supports Exchange Server  Requires Java 1.6+  Uses the Exchange web service

16 Data Source Adapters  Calendar 2.0 Adapters on Kinetic Community  Microsoft Sharepoint  Requires Java 1.6+  Uses the Sharepoint web service

17 Data Source Adapters  Advantages:  Connect to systems outside of Remedy.  Display information from multiple Remedy servers.  Display information from multiple systems.  Can be used without Remedy.

18 Summary of New Calendar 2.0 Terms

19 Data Source  A server or system that contains data  Example: Remedy ARS Server  Example: Microsoft Exchange Server  Example: JDBC Database

20 Adapter  A file that communicates to a specific data holding system, and transforms this data into Kinetic Calendar events.  Example: Remedy ARS Adapter, communicates to Remedy ARS servers  Example: Exchange Adapter, communicates to Microsoft Exchange servers

21 Connection (or Data Source Connection)  A configuration of an adapter that points to a specific system or end point. This includes not only the location (server name for example), but the credentials to access the system, and any other necessary information the system requires.  Example: Production Remedy Server – configured to point at the company's production Remedy server and login with specific credentials.

22 Configuration Changes

23 Configuration Changes  Calendar configurations are now stored as files on the web server.  Use the JSON open standard file format, making it easy to edit with a simple text editor.  Data Source connections are configured from a console to ensure all sensitive information is encrypted.

24 Example JSON Configuration Adapters configuration

25 Example JSON Configuration Calendar configuration

26 Event Colors

27 Custom Event Colors  Colors can be specified per event type. This color will be applied to all events when the event type is not filtered. et_incidents.json

28 Custom Event Colors

29 Custom Event Colors – By Value  Colors can also be defined for specific filter values et_incidents.json

30 Custom Event Colors – By Value

31 Click Handlers

32 Click Handlers  An action that runs when something is clicked – either an event that is displayed in the calendar view, or an open time slot in the calendar view.  Can be configured to open a URL, such as a Kinetic Request service, a Mid-Tier form, or simply another web page.  Can also be configured to execute a javascript function.

33 Calendar Click Handlers  Executed when an open time slot on a calendar is clicked.  Passes the date/time slot the user clicked. Example: Open a Kinetic Request form that collects additional information, and uses the task engine to create a new event in the desired location.

34 Event Click Handlers  Executed when an existing event is clicked.  Information about the event may be passed to the click handler, such as the event id. Example: Open an external system, such as Kinetic Request, to modify the event.

35  Example showing a URL with parameters  This example opens a Kinetic Request service, passing two URL parameters that the service item can utilize. Click Handler Example calendar.json

36 Themes

37 Themes  Provide unique branding for your pages – Calendar listing page – Calendar display page – Event display page – Error page  Same concept as Kinetic Request bundles

38 Theme Example – Calendar listing page

39 Theme Example – Calendar display page

40 Time Zones

41 Time Zones  Improved Time Zone support.  Support for daylight savings time (DST). Before – Offset from GMT VS Now – Olson Timezone

42 Time Zones  Ability to lock a calendar to a specific time zone.  Example:  A conference calendar that displays the times of all the events for the conference.  Events need to be displayed in the time zone where the conference is held, not the time zone where the user is viewing the calendar.

43 Time Zones – Example of fixed time zone calendar.json

44 Fixed Calendar Time Zone

45 Administration Console

46 Administration Console  Manage web application properties  Manage data source connections  Provides access to log files  Displays web server environment information  Reload calendar configurations

47 Administration Console - Configuration

48 Administration Console - Properties

49 Administration Console – Environment

50 Installation

51 Simplified Installation  Removed the InstallAnywhere installer  Simply deploy a war file to an existing Java web server  Advantages:  Install from any system, not just Windows  No registry changes  No Remedy objects to import

52 Summary

53 Summary – What's New  Separation from Remedy (no forms or workflow)  Support for multiple data sources (not just Remedy)  Event Type colors  Click Handlers  Better time zone support  Administration Console  Simplified install process

54 Kinetic Community  Resources and Documentation available on Kinetic Community. – community.kineticdata.com

55 Additional Resources  JSON file format – wikipedia.org/wiki/JSON – json.org

56 Contact Info Jack Boespflug Kinetic Data