Skip to content

Pleasanter Version Upgrade and Upgrade to Enterprise Edition

1. Conducting the Trial

The conditions for conducting a "Trial" are as follows:

License Status Trial Available Notes
Community Edition Trial not conducted Field extensions will be performed based on specified content
Community Edition During trial period Field extensions will be performed again based on specified content. Depending on the specified content, the extended fields themselves may be deleted, which may result in data loss
Community Edition Trial expired - Trial can only be conducted once
Enterprise Edition - - Trials cannot be conducted on Pleasanter upgraded to Enterprise Edition, regardless of license status

2. Upgrading Pleasanter Version During Trial Period

There are two methods for upgrading Pleasanter version during the trial period:

a. Using the installer
b. Using CodeDefiner

a. Using the Installer

  1. Execute the following command to install the latest installer:
    dotnet tool install -g Implem.PleasanterSetup 
    
  2. Execute the following command to launch the installer:
    pleasanter-setup
    
  3. You will be asked for the installation directory. If the default setting is acceptable, press Enter. Below is an example execution on Windows:
    Install Directory [Default: C:\web\pleasanter] :
    
  4. If there are no issues, enter "y" and press Enter:
    Shall I install Pleasanter with this content? Please enter 'y(yes)' or 'n(no)'. :
    y
    

    CodeDefiner will be called and will automatically switch to the trial option when field reduction is detected.
  5. To continue with the trial option, enter "y" and press Enter:
    Type "y" (yes) to continue the Pleasanter Extensions Trial process, otherwise type "n" (no).
    y
    

    If you select "n" here, a web browser will launch and display the trial information page.
  6. If the following is displayed, the version upgrade during the trial period was successful:
    <SUCCESS> Starter.TrialConfigureDatabase: Database configuration has been completed.
    <SUCCESS> Starter.Main: All of the processes have been completed.
    Setup is complete.
    

    If the following is displayed, the trial period has expired:
    <ERROR> Configurator. TrialConfigure: Trial period has expired. You can not rerun.
    <ERROR> Configurator. TrialConfigure: Database configuration canceled.
    

    The Enterprise Edition information page will open in a web browser, so please consider implementing Enterprise Edition.

b. Using CodeDefiner

  1. When upgrading Pleasanter during the trial period, execute CodeDefiner with the "trial" command as follows. The command below is an example for Windows:
    cd C:\web\pleasanter\Implem.CodeDefiner
    dotnet Implem.CodeDefiner.dll trial
    
  2. If you execute with the normal upgrade procedure ("_rds" command), the fields extended during the trial will be deleted, which may result in data loss.
  3. Perform the upgrade following the manual version upgrade procedure, and when executing CodeDefiner within the procedure, execute it with the "trial" command as described above.

For a list of CodeDefiner commands, please refer to here.

3. Increasing or Decreasing Extended Fields During Trial Period

If you want to increase or decrease extended fields during the trial period, follow steps 1 and 2 of "Setting up fields to add" in "Pleasanter Extensions Trial". When reducing the number of fields, the fields themselves will be deleted from the table, causing data registered in the extended fields to be lost. Always create a backup before performing field extensions.

4. Upgrading from Trial to Enterprise Edition

You can upgrade from during the trial period or after trial expiration to Enterprise Edition while maintaining extended fields. To perform the upgrade, follow these steps:

4-1. If the "/e" Option Was Not Used When Starting the Trial (100 classification fields were added)

  1. Execute steps 2 and 3 of the "Upgrade Procedure from Community Edition to Enterprise Edition" to upgrade to Enterprise Edition.
  2. Follow step "2. Edit and store Issues.json and Results.json" in the "Field Extension Procedure (ver.1.4.8 and later)". At this time, set "Class" to 100 in Issues.json and Results.json. Samples are provided below:
  3. Issues.json: Time limited table
    {
       "TableName": "Issues",
       "ReferenceType": "Issues",
       "Class": 100,
       "Num": 0,
       "Date": 0,
       "Description": 0,
       "Check": 0,
       "Attachments": 0
    }
    
  4. Results.json: Recorded table
    {
       "TableName": "Results",
       "ReferenceType": "Results",
       "Class": 100,
       "Num": 0,
       "Date": 0,
       "Description": 0,
       "Check": 0,
       "Attachments": 0
    }
    
  5. Execute CodeDefiner. Follow step "3. Execute CodeDefiner" in the "Field Extension Procedure (ver.1.4.8 and later)".
  6. Follow step "4. Verify field extension" in the "Field Extension Procedure (ver.1.4.8 and later)" and verify that the fields extended during the trial (Class001 to Class100) are displayed.

4-2. If the "/e" Option Was Used When Starting the Trial (Issues.json and Results.json were configured)

  1. Execute steps 2 and 3 of the "Upgrade Procedure from Community Edition to Enterprise Edition" to upgrade to Enterprise Edition.
  2. Follow step "4. Verify field extension" in the "Field Extension Procedure (ver.1.4.8 and later)" and verify that the fields extended during the trial (Num001, Date002, etc.) are displayed.

Supported Versions

Supported Version Content
1.4.15.0 and later Feature added