WhereScape is pleased to announce that WhereScape RED 10.5.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.
A new scheduler upgrade wizard has been developed which streamlines the upgrade process and reduces the number of manual steps required during scheduler upgrades.
Authentication profiles are now created automatically when upgrading from a version of RED which does not include the advanced connect feature. Refer to the Upgrade on Windows guide for more information.
Metadata databases and DSN's for RED and the Azkaban Scheduler can now be created using the installation wizards, reducing the number of manual steps required during new installs. For more information refer to the metadata installation and scheduler installation guides.
A new scheduler profile maintenance wizard has been developed with an enhanced UI. For more information refer to the Scheduler Maintenance documentation.
The maximum number of projects and groups can now be configured, allowing for over 1000 projects and groups in a single repository. This can be changed on the Other Options window.
Increased the character limit on FROM/WHERE clause for views to 65344 characters.
When starting med.exe (RED UI) from a command line with all the required metadata connection elements provided, you can now provide and additional switch '--auto-connect' which will skip the interactive login screen to RED.
Added RED UI ODBC connection resilience, idle connections are tested before use and recovered if broken. Idle time before testing and test response time can be fine-tuned via user preferences. Visit the med.exe Client Command Line documentation for this and other available options.
RED's job plugin for Azkaban now accepts the legacy RED 9 script output protocol when executing stand-alone scripts via a scheduler job, this feature eases migrations to RED 10 by reducing script refactoring and testing.
The following changes have been implemented since 10.4.0.2
| JIRA | Release Note |
|---|---|
| RED-12100 | Authentication profiles are created automatically when upgrading from a version of RED without the Advanced Connect feature. |
| RED-11462 | Jobs stuck in the running state can now be aborted in the RED UI. |
| RED-12256 | On hold jobs are no longer retained when processing objects via the scheduler interactively. |
| RED-4786 | The maximum number of projects and groups can now be configured, allowing for over 1000 projects and groups in a single repository. |
| RED-5905 | Increased the character limit on FROM/WHERE clause for views to 65344 characters. |
| RED-12278 | Added RED UI ODBC connection resilience, idle connections are tested before use and recovered if broken. Idle time before testing and test response time can be fine-tuned via user preferences. |
| RED-12130 | Improved performance of object properties storage tab initialization when using a Teradata target. |
| RED-12285 | The Connection field 'Database Link Name' is now available to scripts as an environment variable 'WSL_LOAD_DBLINK' so that scripts can build the appropriate source SQL statements at run-time. |
| JIRA | Release Note |
|---|---|
| RED-10686 | New Scheduler upgrade workflow automating many of the manual steps that were required. |
| RED-12257 | The WhereScape RED metadata database and DSN can be automatically created using the RED Setup Wizard. |
| RED-12102 | The Scheduler metadata database can be automatically created during the Scheduler installation process. |
| RED-12103 | New RedSchedulerProfileMaintenance.exe for maintaining the Schedulers authentication profiles. |
| JIRA | Release Note |
|---|---|
| RED-12293 | Fixed a metadata insert failure when defining Reusable Transformations in RED 10. |
| RED-12274 | Fixed an issue deploying the default 3D entity types Dim View and Retro to RED, now these entity types are correctly mapped during deployment. |