Support > Installation Guide (R7) > Migration from R6 definition file to R7 repository
ja | en

I will explain how to convert Wagby R6 definition file to R7 repository.

Source (R 6)

Definition file

  1. IntroductionUpgrade the current Wagby R6 definition file to the latest version of R6 series.
  2. After that, build processing is done with Wagby R6.This last build state will be subject to migration.(Please have the definition file in the xls-model folder and make the last build in the R6 environment using this definition file.)

data

If you save the latest export file in the export folder (Wagby R6), it loads and transfers the value of "master model" included in the file.

(For the master model of R6, the value changed during operation is the latest value than the initial value described in the definition file.In order to migrate this, please copy the export file acquired by the production machine to the export folder of Wagby R6 to be migrated.)

This task is not mandatory.A suitable export file (a file containing the date and time prefixed with "data_".Exclude "data_init" and "data_build".) Can not be found, the initial value of the master model will use the value described in the definition file as it is.

Transfer destination (R 7)

I will return it to the state of the initial repository.

Please be careful:
If you change the model definition file (Excel) of R6 after migration, apply the R7 migration tool after performing the build process again at R6.

Double-click the migration tool "RepositoryMigration - XXXjar" included in the installed mag folder of Wagby R7 and execute it.(The XXX part contains the version number.The version of the tool that is shipped depends on the version of Wagby.)

Figure 1 Running the migration tool
The migration tool is a Java application.A file with the extension ".jar" can be executed by double-clicking on a computer on which Java is installed.
The migration tool (GUI version) requires Java 8 or higher.It does not work with Java 7.

Select "R6 to R7" as the conversion method.The source Wagby specifies the folder in which R6 is installed.It is not necessary to change the conversion destination Wagby.

After setting, press "start migration" button.

Figure 2 Conversion method and conversion source specification

When the migration is completed, a dialog like the one shown in Figure 3 will be displayed. After closing the dialog by pressing the "OK" button, select "Exit" from the file menu, or exit the tool with the close button of the window.

Figure 3 Migration completion message

In addition, if manual migration work is involved, a message like the one shown in Figure 4 will be displayed. Specific changes are specified in repositorymigration.log in the logs folder.Please correct according to the contents of "Manual migration work" below.

Figure 4 Message when Manual Correction is Required

Troubleshooting: Can not run

If you can not execute RepositoryMigration-XXXjar by double-clicking it, please try the following method.

  1. Open a Windows OS command prompt.
  2. Go to misc in the folder where Wagby is installed.
    cd misc
  3. Start it manually as follows.
    %JAVA_HOME%\bin\java -jar RepositoryMigration-X.X.X.jar

If you still can not run it please try reinstalling Java.Java 8 or higher is required.(It does not work in Java 7.)

The migration tool sometimes creates "data_R6template" in the export folder. This is the mail and form settings on Wagby definition file converted to template file format.

After building, import the files in this folder.Follow the procedure below.

  1. Execute importR6_db.bat included in the bin folder of the built application (wagbyapp).(For Linux OS, it is importR6_db.sh.)
  2. Start the application.
  3. Confirm the contents of the mail template and form template.Wagby definition file settings are templated.

Copy the template file

Information has been transferred to the "form template model" in the above procedure, but the body of the template file is not yet included.Follow the procedure below to copy.

  1. Confirm that the upload_dir / jfcreporttemplate folder of the built application (wagbyapp) exists.The contents immediately after migration are empty.
  2. Copy the template file prepared in R6's xls-report folder to this upload_dir / jfcreporttemplate folder.

After this, please test the form printing from the application.

If the form printing does not work well, please register the template file manually.For details, see "Form> Excel form - Detailed display> Definition method> Set up form templatePlease read.

The migration tool converts according to the following rules.

  • The master model of R6 is a choice model of R7.
  • All simple calculation formulas (time difference, birth date, padding) of R6 are replaced with expressions using functions.The behavior is the same.
  • The type "fixed value" of R6 has been abolished in R7.Instead, the expression is set to "Initial value".
  • The R6 "Model Reference - Display Multiple Items Concatenated" function is obsolete.Please do the same thing with expressions.
  • In R6's calendar view, it was possible to specify multiple items for title, place, person in charge, remarks.However, in R7, 1 setting = 1 item.Please do the same thing with expressions.
  • All "R6" (fixed) mail settings are changed to "mail template" method.
  • R6 "(fixed) form setting" has been changed to "form template" method.
  • The primary key item id of the account model (juser) of R6 has been abolished.Instead, the userid item becomes the primary key.
  • In R6 Excel list form printing, it was possible to specify 2 patterns "output only on screen" and "all output", but in "R7" it was only "all output".
  • Convert old formulas used in R6.6 Update 9 and earlier to current method.(It covers the arithmetic expression and the initial value formula.)
  • If juser's id item is specified as the display priority in the item referring to the juser model, it is converted to use the userid item which is the primary key of the reference model (juser).(Since juser's id item has been abolished)
  • In the item that refers to the juser model, if you have specified juser's id field as contents, expiration date, and narrowing item, replace it with the userid item.(Since juser's id item has been abolished)
  • System system models other than juser, jgroup, jnews are all replaced with the latest version of R7.With R6, modifications applied to the system model will not be migrated.

Other

  • In Wagby up to R 7.5.0, the project identifier is converted to "wagby".In Wagby after R7.5.1, the project identifier can be changed, so this conversion process will not be performed.

Model reference - Display multiple items by concatenation

In R6, there was description to concatenate multiple items to the content of model reference.However, in R7 this notation is abolished,Using expressions insteadWe recommend.

With the migration tool, only the first item is retrieved.(For example, if you described "empname + '(' + empid + ')'" in the setting field, the contents of the reference model will be "empname" by the transition.Please manually redefine this setting (using formulas) after migration.

Calendar view - specify multiple items for title, location, person in charge, remarks

In R6's calendar view, it was possible to specify multiple items for title, place, person in charge, remarks.However, in R7, 1 setting = 1 item.Please do the same thing with expressions.

Style specification to input field

In R6, style (CSS) was applied to standard HTML parts, but in R7Apply style to parts provided by DojotoolkitI began to do.Therefore, the display result may be different.Please check with your eyes as a precaution.

Naming convention of document output file name

In R6, it was possible to include an expression in the output file name.However, in R7, it was unified into "form template" method (prepared in R6).Therefore, the naming convention of the output file name is the form template method.

If you included an expression in the output file name, change the definition as follows.

  1. Add a hidden item of the character string type (and database non-saving item) to the model.In the calculation formula, let's generate the output file name.For example, prepare a hidden item outputfilename in the model dailyreport and describe the original expression so that the output file name can be obtained.
    ${name}+"_"+${currenttime}+"_"+${userid}
  2. In the form template definition after migration, describe the above item name and extension in the output file name.In this case, specify "Model name _ p." + Item name.
    ${dailyreport_p.outtpufilename}.xls
Figure 5 Setting up form template definition

Models whose migration is skipped

As of R7.3.2, the following models included in the "System" tab are used instead of the old version, but included in the new version.That is, it will be excluded from the migration tool.

However, the following models are excluded.That is, the definitions changed by the developer will be inherited (even after the transition).

  • juser
  • jgroup
  • jnews

the aboveOther thanWhen modifying the system type model of (eg example: menu system changed)Apply same fix manuallyplease.

System definition file

If the following system definition file included in the $ (DEVHOME) / env / xls-common folder of R6 has been changedApply same fix manuallyplease.

  • common-jfcjobschedule.xls
  • common-jfclicenseholder.xls
  • common-jfclockobject.xls
  • common-jfcmailtemplate.xls
  • common-jfcreporttemplate.xls
  • common-jfcrepository.xls
  • common-jfcworkflow.xls
  • common-jfcworkflow2.xls
  • common-jholiday.xls

Customization code

The migration tool does not handle customized code (Java, JSP, JavaScript, etc.). These files should be manually modified by the developer to the latest R7 code.

For details on how to fix the code, please contact Wagby Reseller.

Treatment of template data

It may be necessary to load mail templates and form templates.Detail is"Import template dataPlease read.

  • In R 7.0.2, the operation button of R6's master model is arranged in the menu.
  • Since R 7.1, the version number notation has been changed to 7.xx like the main body.We support migration of mail and form definitions from this version.In the transition of the account model (juser), the id item is now removed.(The userid item is substituted for the primary key.)
  • Beginning with R7.3.2, models in the System tab are now not used for migration, but now use the one shipped with this version.However, except juser, jgroup, jnews.In these three models, the definitions changed by the developer are migrated.
  • From R7.4.0, the function to acquire the initial value of the master model from the export file has been added.
  • In R 7.4.0, the project identifier is forcibly replaced with "wagby".With R 7.5.1, this forced replacement process is canceled.(Since the project identifier can be changed since R 7.5.1)

The difference from R6 is as follows.

  • Migrating the old definition file may cause the setting of the management processing menu to be incorrect.Example: "Statistics" function was provided in R6.7 Update 3.If you move the definition file older than that to the R7 repository, the "statistics information" icon will not be displayed in the management process menu setting field after migration.Therefore, you can not set the order and colors.
In order to cope with this problem, we recommend that you upgrade to R6.10 series, which is the latest version of R6 as much as possible, and then switch to R7.