Page History
WhereScape is pleased to announce that WhereScape RED 10.4.0.3 4 is now available.
This release of RED is compatible with WhereScape 3D 9.0 versions and up.
...
The following changes have been implemented since 10.4.0.32
Fixes and Improvements
JIRA | Release Note |
| RED-12090 | Implemented connection resilience for Application Deployment, added two new RedCli deployment args to control this new feature. New deployment args: ‘connection-timeout’ (time is seconds to wait for a connection, default=60) and ‘max-retry-count’ (max times to attempt reconnection during the deployment before failing, default 10) |
| RED-12266 | Fixed an issue affecting target Procedure based routine generation when metadata is on PostgreSQL 17 during 3D deployment to RED. |
| RED-12069 | Fixed an issue with 3D deployments to RED where the deployment would fail if there were no Load objects included in the deployment XML. |
| RED-12269 | Fixed RedDeploy issue with target mapping page for 3D created SQL Server target locations. |
| RED-12191 | Improved template engine performance in the following areas: Code generation from the RED UI, Application Deployment, RedCli Export All DDL command. |
| RED-12184 | Azkaban now updates the job stats for error warning and info counts, which allows the RED Scheduler tab to correctly signal job warnings. |
| RED-11982 | Improved RedCli error reporting when there are compilation errors for Procedure objects, these will now show as Target errors in the RedDeploy UI |
| RED-11409 | RED's plugin for Azkaban now creates unique file names within tasks to support generic Action Processing Scripts being run in parallel. |
Detailed Changes in RED 10.4.0.4
The following changes have been implemented since 10.4.0.3
Fixes
JIRA | Release Note |
| RED-12347 | Fixed a 3D export to RED issue where Named Targets; SQL Server, Oracle and Teradata were unable to be resolved during deployment. |
| Anchor | ||||
|---|---|---|---|---|
|
...