1.1
1.1.4-funcrel
Note
This release:
- is compatible with a migration to CAST Imaging 3.2.x-funcrel, 3.3.x-funcrel, 3.4.x-funcrel and 3.5.x-funcrel. See the documentation.
- is compatible with a migration from CAST Imaging v2 where multiple tenants are in use for storing "viewer" results.
Resolved Issues
| Customer Ticket Id |
Details |
| 56277 |
Fixes an issue where the migration failed during the backup stage for applications whose name contained a special character (simple quote mark). |
1.1.3-funcrel
Note
This release:
- is compatible with a migration to CAST Imaging 3.2.x-funcrel, 3.3.x-funcrel, 3.4.x-funcrel and 3.5.x-funcrel. See the documentation.
- is compatible with a migration from CAST Imaging v2 where multiple tenants are in use for storing "viewer" results.
Resolved Issues
| Customer Ticket Id |
Details |
| 56079 |
Fixes an issue causing the error: "You have no access to this application. Please contact your administrator." when selecting some applications post-migration. This affects applications that were imported directly into CAST Imaging Viewer V2, and whose name contains blank spaces. |
1.1.2-funcrel
Note
This release:
- is compatible with a migration to CAST Imaging 3.2.x-funcrel, 3.3.x-funcrel, 3.4.x-funcrel and 3.5.x-funcrel. See the documentation.
- is compatible with a migration from CAST Imaging v2 where multiple tenants are in use for storing "viewer" results (see "Support for multi-tenancy (domain/tenant synchronization)" below).
Resolved Issues
| Customer Ticket Id |
Details |
| 55639 |
Fixed an issue causing the "Console" migration to fail when the "Neo4j" migration had not yet been completed. This situation is valid when "Neo4j" is not used, therefore the tool now allows the "Console" migration to continue instead of failing, and provides a warning. |
1.1.1-funcrel
Note
This release:
- is compatible with a migration to CAST Imaging 3.2.x-funcrel, 3.3.x-funcrel, 3.4.x-funcrel and 3.5.x-funcrel. See the documentation.
- is compatible with a migration from CAST Imaging v2 where multiple tenants are in use for storing "viewer" results (see "Support for multi-tenancy (domain/tenant synchronization)" below).
New Features
| Summary |
Details |
| Support for domain/tenant mapping |
Support has been added for migrating from CAST Imaging v2 where domain/tenant mapping has been enabled (option "synchro.domains.imaging.enabled" where application results are stored in different domains/tenants). See the documentation for more information. |
Feature Improvements
| Summary |
Details |
| Free disk space check |
A check has been added to ensure that the destination disk contains enough free disk space to accept the unzipped shared/delivery/deploy archive files when performing the restore action. |
| Perform important checks as early as possible in the process in order to improve performance |
Several validation checks (v3 contains no applications, available disk space, and multi-tenancy options) previously ran after the time-consuming application schema checks. These checks have now been moved to the beginning of the migration process, enabling early termination if any validation check fails. |
| Reduce disk space usage when possible |
An update has been added that ensures that if a user uses an option that does not imply copying the shared/delivery/deploy folders, then the shared/delivery/deploy archive files will not be extracted from the main archive, therefore reducing overall disk space usage. Previously the archive files were systematically expanded whether needed or not. |
Other Updates
| Internal Id |
Details |
| IMAGMIG-74 |
A check has been added to the migration process to detect duplicate applications (i.e. the same application name in more than one tenant) in CAST Imaging viewer v2. When this discrepancy is detected, the migration is aborted and an error message explains what is required before the migration can continue. See the documentation. As a direct result of this change, two new mandatory parameters have been added to the backup.conf file (for the backup step): "apikey=" and "GATEWAY_HOMEPAGE_URL=" - both for the CAST Console v2 installation. See the documentation. |
| IMAGMIG-73 |
A check has been added to the migration process to detect unauthorized characters in domain names in CAST Console v2 (i.e. characters that are not permitted in corresponding tenant names in CAST Imaging v3). The migration tool detects this discrepancy and prevents replication to the target CAST Imaging v3 instance (when the IMAGING_DOMAIN_SYNCHRO_ENABLED option is enabled). See the documentation. |
| IMAGMIG-72 |
A check has been added to the migration process to compare the status of the domain/tenant mapping feature in the target CAST Imaging v3, and the presence (or not) of domains and corresponding tenants in the v2 installation. In certain situations as described in the documentation, the migration process will be aborted to ensure consistency. |
| IMAGMIG-63 |
Fixes a technical issue where v2 related paths stored in an internal schema table were not updated to match the paths used in v3. |
| IMAGMIG-8 |
Ensures that a direct migration from 3.2.x-funcrel - 3.5.x-funcrel is supported. |
| IMAGMIG-55 |
Resolves an issue where the extraction of shared/delivery/deploy folder archives failed when the archives contained file paths exceeding 260 characters. |
Resolved Issues
| Customer Ticket Id |
Details |
| 55003 |
Fixes incorrect syntax used in the Cast_Imaging_V3_Migration.bat resulting in an error when the batch is used. |
1.1.0-funcrel
Note
This release (and all previous releases):
- are not compatible with a migration to the forthcoming 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. |