WhereScape is pleased to announce that WhereScape RED 10.4.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.
Access the User Guide here.
WhereScape presents RED 10.4 a new version of RED. The features implemented in this version are mainly focused on enabling 3rd party integrations with external tools like GIT, but also enhances the UI and enables the ability to add scripted workflows based on the current context in the RED UI.
Workflow scripts, when defined, will appear in the context menu throughout the RED UI. When clicking on them in any context menu, the underlying script will be executed and provided with the complete object list contained by the context. This allows for integration scripts to be written that can perform actions on lists of objects, such as: creating deployment applications, checking items in and out of GIT, running external tests on the objects selected, exporting data to catalog tools, backing up scripts to disk and more!
The following changes have been made to support this new feature:
When deploying Objects with multiple Source Mappings via 3D Export to RED you can now control the merge behavior when updating existing Objects Source Mapping Sets. There is now a new option with three settings when deploying from 3D to RED.
Option: ‘Existing Source Mapping Sets will be’
This feature will be particularly useful to organizations with multiple development teams or projects affecting the same objects in RED, allowing them to deploy only the new Source Mappings that they have added and avoid deploying out-of-date changes to existing Source Mappings.
In addition to the major improvements above please see the following Detailed Changes section for the full list of customer fixes and improvements in this release.
The following changes have been implemented since 10.3.0.1
| JIRA | Release Note |
| RED-11947 | A new script category 'Workflow' has been introduced, these script types will show up in context menus and when executed provide the containing context to the script in a JSON format. |
| RED-11951 | Host Script Object names can now contain spaces and hyphens, this supports human readable display of Workflow scripts in context menus. |
| RED-11950 | Host scripts can now have individual icons set per host script type, particularly useful for Workflow scripts. New icons have been added to the installer for working with this feature. |
| RED-11957 | CheckIn/CheckOut feature will now trigger execution of a script, if present, to support GIT integrations. Add script names of wsl_workflow_checkin and wsl_workflow_checkout to enable this feature. |
| RED-11953 | Added new endpoints to the RED metadata service, objectsExportByName and jobsExportByName, that export metadata in a GIT friendly format. |
| RED-11959 | Deployment Application Creation via command line now accepts a specific set of objects to deploy based on a JSON structure that RED Workflow scripts produce. |
| RED-11955 | RedCli commands on script, procedure and templates now support an 'export-all' option, useful for GIT integrations. Additionally single export allows specifying a directory for auto creation of the filename and extension for the object. |
| RED-11759 | Updated the built in Java JRE version to openjdk 11.0.25 |
| RED-11556 | Added merge mode to application deployment for Source Mappings when deploying from WhereScape 3D |
| RED-11942 | Add Scheduler API environment variables to all script executions to support actions like releasing another job via scripts. |
| RED-12036 | Azkaban to RED metadata resilience feature now logs the failure reason during reconnection scenarios. |
| RED-11958 | RED UI now accepts the Scheduler Script Output Protocol as well as the traditional script output protocol. |
JIRA | Release Note |
RED-11641 | Fixed Azkaban Unsupported Object Type error when scripts have [TABLEOWNER].TABLE_NAME references to Retro Objects. |
RED-12029 | Fixed issue where Windows and Linux loads were going through legacy load methods through the UI. |
RED-12028 | Prevent legacy GetKey function popups for dimensional models. |
RED-12054 | Teradata TPT Routine Load Table setting now exposed via templates. |
RED-12043 | Fixed issue where bulk regenerate load scripts fails for Named Targets when load type is not Script Based Load. |
RED-11932 | Fixed Azkaban NullPointerException when running loads from Windows or Linux source connections. |
RED-11974 | Fixed issue where interactive processing via scripts could fail with "<work_dir> contains an incorrect path" in some repositories. |
RED-11887 | Fixed issue with remapping Filegroups during application deployment with RedCli |
RED-11994 | RedDeploy and RedCli now transfer relationships metadata to to RED from 3D exports. |
RED-12004 | Table properties Update/Custom Type drop-downs now default to the correct type, script or procedure, based on the assigned default template type. |
RED-11935 | Fixed RedSetupWizard Target Connection page auto-scrolling issues. |
RED-12015 | Fixed UI issues when converting existing Facts to Partitioned Facts in RED 10.3 |
RED-12016 | Fixed issue where Optional Create Clause was not persisted for Load table objects. |
RED-12047 | Vulnerability fix in Azkaban for CVE-2024-53677 |