Converting Version 1.5.x to Version 2.0.x

Usage

Use the section below to describe how to implement the solution. Code or screenshots should be used here.

The 2.0 version of Kinetic Calendar is strictly web based, including the text files that configure what is displayed per calendar. This is very different from the Remedy based dialogs from previous versions.

Thankfully, the breakdown of the dialogs for the "old" version of Kinetic Calendar is similar to the new version. While you can't just cut and paste, you can relate the two.

The most basic configuration for a calendar is two files, calendar.json and et_eventName.json. These correspond to the Calendar Properties dialog, and the Calendar Event Type dialogs from the 1.5 version.

Calendar Configuration

Use the section for an example of the how to use the solution in this section.

The calendar.json file is the easiest to configure from version 1.5 to version 2.0. If the calendar is similar to one already created for version 2.0 it may be easier to copy an exiting calendar.json into your new calendars directory.

Sample version 1.5 Calendar Properties dialog:

Sample version of the calendar.json file:

Here are the directly related fields (V1.5 to V2.0):

Calendar Name => name

Web Name => id

Description => description

Status => status

Display Page => displayPage

Default View => defaultView

Visible in Web Listing => visibleInListing

Calendar 2.0 doesn't use Remedy permissions (Visibility & Viewer Group), so those fields are left out. The encoding is also removed. Manager Notifications are also not incorporated into the 2.0 version.

Event Configuration

In version 1.5 of Kinetic Calendar, there were four types of events, Default, Custom, Other Calendar, and Filtered.

In version 2.0 there is only one file, that covers both Custom and Filtered. Being able to have multiple events json files, means that you can just add another file (copy it from the other calendar) to add another calendars events to yours. The Default event type is not included in version 2.0, because that stored data in a specific Kinetic Remedy form, and the new version does not import anything into Remedy.

Sample 1.5 Calendar Event Type Dialog (this dialog is the same for both Filtered and Custom events):

Sample event json file:

They look very different, but just like the calender file, there are many one to one similarities.

Here are the directly related fields (V1.5 - V2.0):

Name => name
Status => status
Source Form => source|configuration|Form
Description Fields => source|coreMappings|Description
Event Name Field => source|coreMappings|Name
Time Begin Field => source|coreMappings|Start
Date Begin Field => source|coreMappings|Start
Date End Field => source|coreMappings|End
Qualification => source|configuration|Qualification

The qualification can stay the same, with two changes. First, the entire qualification is enclosed within double quotes. Second, each double qute that is part of the qualification needs to be escaped with a backslash (). For example:

'Status' = "In Progress" AND 'Type' = "Server"

becomes

"'Status' = "In Progress" AND 'Type' = "Server""

Calendar 2.0 does not use the following fields, URL field (see click handlers above), Duration, and the Source option.

There are two other dialogs that are part of Filtered events for version 1.5.

Display Fields for the Event:

Here are the direct mappings from V1.5 to 2.0 for this dialog (only one):

Output Format => detailsPage (almost always left at the default - "/themes/default/event.jsp",)

All fields listed under the Selected Fields table will be listed under detailMappings. Field Label|Selected Field is the same as "Field Label": "Database ID"

Filter Fields for the Event:

Here are the direct mappings from V1.5 to 2.0 for this dialog (only one):

Default Filter Field => defaultFilter

Individual fields to filter on are set in the Filter Mappings section of the json. The name equals the Field Label and the Selected Field is set with the value. It is a database id like the display field above. You can normally get the database value from the table of values in V1.5 for use in the json. Otherwise you will need to go to Developer Studio to get the values you need.

New fields in V2.0
There are a few fields in V2.0 that are not in the V1.5 dialogs.

"color" will set a default color for the event. Otherwise it is chosen from a standard array.

"connectionName" refers to a specific connection setup on the Kinetic Calendar Administration Console.

source|coreMappings|id refers to a specific unique id fr the record (normally field 1 - the request ID).

source|filterMappings|values refers to colors that you can assign to the different filter values.