Support > Import and export function utilization guide (R7) > Import data of classic calendar view into modern calendar view

Since R7.6, the modern calendar view function has been added. Here, we will explain the procedure to migrate registered data in the former calendar view (classic) to modern calendar view. R7.6

To move from classic calendar view to modern calendar view, follow the procedure below.

  1. Export the current data.
  2. Open Desinger and change its definition.
  3. Perform build processing.
  4. Use the migration tool so that old data can be read.
  5. Start the application and read the old data.
  6. After reading the data, do postprocessing.

Next, I will explain the details.

Convert classic calendar view to modern style definition.Please do the following correspondence.

  1. Delete three items corresponding to the "date" "start time" "end time" of the classic method.
  2. Change the display format to "modern".For the modern method, add two items corresponding to "start date and time" and "end date and time".Both are date and time type."Title" "person in charge" "place" "remarks" can be reused.Add items corresponding to "URL" and "all day" as necessary.

After changing the definition, we will do the build process.

After building, make settings to read the old data using the migration tool.

Start-up

The migration tool is in the misc folder where you installed Wagby.The file name is CalendarConverterCUI.jar.Here, we will explain how to use in Windows OS.Please use the console when operating on Linux/Mac OS X.

Enter "cmd" in the "Start menu> Search program and file" column and execute it.(FIGS. 1 and 2)

Figure 1 Start menu
Fig. 2 Execute "cmd"

A command prompt is displayed, as shown in Figure 3.

Figure 3 Command Prompt
You can also execute "command prompt" directly without going through the start menu.

When the command prompt starts, move the current folder with the cd command.The destination is Wagby installation folder \ misc.(Please read the installation folder properly.)

Fig. 4 Changing the current folder

Execute CalendarConvert.jar included in this folder with the java command.When executed without parameters, a help message indicating usage is output as shown in Fig.

java -jar CalendarConvert.jar
Figure 5 Run CalendarConvert.jar and check the help message

How to use

Use the following format.(Although it carries out a line feed to make it easier to read, in fact it is input on one line.)

java -jar CalendarConvert.jar 対象モデルID 
  -date クラシック形式(旧)での日付項目
  -time1 クラシック形式(旧)での開始時刻項目
  -time2 クラシック形式(旧)での終了時刻項目
  -datetime1 モダン形式(新)での開始日時項目
  -datetime2 モダン形式(新)での終了日時項目

Here is an example.

java -jar CalendarConverterCUI.jar schedule -date sdate -time1 stime -time2 etime -datetime1 begindate -datetime2 enddate

In this example, the object model is "schedule", and the items sdate, stime, etime in classic format are converted into the items begindate and enddate in modern format.

Usage items Classic modern
date sdate -
Start time stime -
End time etime -
Start date and time - begindate (= sdate + stime)
End date and time - enddate (= sdate + etime)

When the command is executed, it is output as follows on the screen.

Figure 6 Result of CalendarConvert.jar execution

This command generates a special conversion script during the import process.(In this example it will be a file called schedule.xsl.) This script replaces the old format item when using the classic calendar view with the new item for the modern calendar view.

For details of the conversion script, please read "Conversion when changing model definition> Conversion from classic calendar to modern calendar".

Launch the application that made use of modern calendar view.

Select the target model of the old data from the "Import/Export screen" and import it.At the time of importing, the conversion script is applied and the date and time of the old data are read for the new data.

Figure 7 Importing a schedule model exported in Classic Calendar view

By the procedure so far, the target data model (schedule model in this example) is replaced with old data items when importing.However, as it is, importing new data items defined for modern calendar view can not be done this time.I will try to read the old item.

Use one of the following procedures to restore the modified script (XSLT file).

Manual correspondence

The original script is wagbyapp \ webapps \ wagby \ WEB-INF \ export \ conf \ importxsl \ schedule.xsl.bak.Rename this to schedule.xsl to get back to original.

Automatic correspondence

I will do a full build.A new XSLT script for modern calendar view is created.