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.
To move from classic calendar view to modern calendar view, follow the procedure below.
Next, I will explain the details.
Convert classic calendar view to modern style definition.Please do the following correspondence.
After changing the definition, we will do the build process.
After building, make settings to read the old data using the migration tool.
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)
A command prompt is displayed, as shown in Figure 3.
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.)
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
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 target model ID - date the date item in classic format (old) - time 1 start time item in classic format (old) - time 2 end time item in classic format (old) item - datetime 1 modern format ) Start date and time item - datetime 2 End date and time item in modern format (new) Item
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.
|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.
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, see "Correspondence when changing model definition> Conversion from classic calendar to modern calendarPlease read.
Launch the application that made use of modern calendar view.
"Import / export screenSelect the target model of the old data 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.
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).
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.
I will do a full build.A new XSLT script for modern calendar view is created.