1.1
1.1.0-funcrel
Note
This release (and all previous releases):
- are not compatible with a migration to CAST Imaging ≥ 3.5.x.
- are not compatible with a migration from CAST Imaging Viewer 2.x where multiple tenants are in use.
The command-line "Compatibility Inspector" tool (provided with the extension) has been discontinued. In its place, both the backup tool and migration tool now include a "reportonly" option that generates compatibility reports (in the same way as the "Compatibility Inspector" without performing actual backup or migration operations. These reports are saved to a specified file using the "validationreport" option. See the documentation.
New Features
| Summary | Details |
|---|---|
| New batch file and configuration file for enterprise mode v2 backup | A batch file called "Cast_Node_V2_Backup_Enterprise.bat" has been added to improve usability: it reads properties specified in the configuration file "backup.conf" and launches "Console-Node-V2-Backup-Enterprise.exe" accordingly. See the documentation. |
| Check on backup timestamp | When migrating Console v2 Enterprise, the timestamp of the provided backup is now compared with the last modification date on the application schemas. If the backup is older than the last modification, then the application is excluded from the migration. |
| Check only option for CAST Console v3 Migration | The migration batch ("Cast_Imaging_V3_Migration.bat") can now be run in "test" mode via the addition of the argument "reportonly" to the command-line (e.g: "Cast-Imaging_V3_Migration.bat reportonly"). Only checks are run and no migration is performed. The report ise saved to a file specified through option "validationreport" in "migration.conf". See the documentation. |
| Support for custom persistence data schema name for CAST Imaging v3.2 | If your CAST Imaging V3.2 installation uses custom schema names instead of the default "analysis_node" and "admin_center" schemas, the "migration.conf" file now supports new options to specify these custom names: "v3nodeschema" and "v3admincenter". These options can be used ONLY when also using option "legacy". See the documentation. |
| Support for custom persistence data schema name for CAST Imaging V3.x (x>=3) | If your CAST Imaging v3.3 or later installation uses a custom schema name instead of the default "control_panel" schema, the "migration.conf" file now supports a "v3controlpanel" option to specify the custom schema name. Note that the this option cannot be used in conjunction with the "legacy" option. See the documentation. |
| Migration from Console v2 to CAST Imaging v3.3 and newer now supported | Migration to CAST Imaging 3.3 and later versions is now the default behavior. Migration from Console v2 to CAST Imaging 3.2 remains supported via the new "legacy" option available in the "migration.conf file. See the documentation. |