|
WhereScape is pleased to announce that WhereScape RED 10.7.0.0 is now available.
This release of RED is compatible with WhereScape 3D 9.0 versions and up.
| Before upgrading, review the Important Messages when Upgrading for more information. |
Go to https://www1.wherescape.com to see available product versions and release notes for older versions.
Log into the WhereScape Support Portal to access downloads.
Batch Application creation via the med.exe command line is now fully headless and no longer interacts with the Windows Desktop.
This enables execution within CI/CD and DevOps pipelines using non-interactive services (e.g., the RED Scheduler).
Additional changes:
Improved the Scheduler Installation and Upgrade process by adding additional validation checks and remediation of configuration ensuring users can get up and running with ease.
Post-load scripts & procedures are now automatically generated during the 3D Export to RED process. UI configured column properties are also included when Exporting from 3D to RED.
Updated script execution behavior in the RED UI:
Previously, interactive script execution used ANSI encoding, which caused inconsistencies between the RED UI and the Scheduler. This could lead to execution failures when scripts contained accented or non-standard characters.
The RED Scheduler Plugin for Azkaban has been aligned with this behavior and now also adds a BOM to PowerShell scripts executed on Windows.
The following changes have been implemented since 10.6.0.0
| JIRA | Release Note |
|---|---|
| RED-11028 | Batch Application creation via the med.exe command line is now fully headless. |
| RED-11309 | Data Warehouse tables (excluding Load tables) can now be sourced from multiple RED Connections that reference different databases within the same target platform. Previously, this capability was limited to SQL Server-based RED Target Connections; other platforms would fail during update procedure execution. |
| RED-12391 | Added validation checks to ensure the Windows service user can perform DPAPI encryption during scheduler installation. |
| RED-12386 | Added validation checks for the Windows service 'Log On As A Service' right during scheduler installation. |
| RED-12385 | Added validation checks for the Windows service credentials provided during scheduler installation. |
| RED-12389 | Added validation checks for the Executor Server Port provided during scheduler installation. |
| RED-12390 | Added validation checks for the Web Server Port provided during scheduler installation. |
| RED-12387 | Added validation checks for the Installation Location provided during scheduler installation. |
| RED-12388 | Added validation checks for the Job Work Directory provided during scheduler installation. |
| RED-12392 | Added validation checks for the Scheduler Dashboard & Scheduler REST API URLs provided during scheduler installation. |
| RED-11675 | Object limits in Deployment Applications have been increased from 5,000 to a theoretical max of 100,000 objects, however beyond 10,000 objects deployment duration can become impractical. |
| RED-11804 | It is now possible to delete multiple source mappings in one go. |
| RED-11843 | The script and template type can now be determined using the RedCli. |
| JIRA | Release Note |
|---|---|
| RED-10864 | Post-load scripts & procedures are now automatically generated during deployments from WhereScape 3D or another WhereScape RED repository. |
| RED-11625 | UI Configured Column Properties values are now correctly exported from 3D to RED. |
| RED-12311 | The scheduler Installer can now upgrade Azkaban when the existing service user is different to the logged in user. |
| RED-11805 | Adding or removing Projects via drag and drop has been improved to remember the state of the object tree and allow the user to confirm actions before continuing. |
| RED-11967 | Improved Red Setup Wizard handling of Auto Execute files in Enablement Packs. |
| RED-12276 | Improved the RedCli 'Connection Modify' command so that modifications to a connection's default template settings no longer resets other settings. |
| RED-12415 | Resolved an issue when browsing extensible sources where tables with the same name in different schemas incorrectly displayed a combined set of columns from both tables. |
| RED-12396 | Updated script execution behavior in the RED UI: - All script files are now written to disk using UTF-8 encoding by default. - PowerShell scripts executed on Windows now include a Byte Order Mark (BOM), ensuring compatibility with PowerShell 5.x. |
| RED-12145 | When creating Load tables on a Teradata target, the storage property MultiSet is now set to TRUE, restoring consistency with earlier RED versions. |