WhereScape is pleased to announce that WhereScape RED 10.2.0.0 is now available. Before upgrading, review the Important Messages when Upgrading from Earlier Versions for more information.

To review the Release Notes for older versions visit WhereScape Documentation.

New Features and Improvements 

Customizable Object Subtypes

Configure your Object Subtypes based on the existing object types in RED with the following configurable settings:

• Name
• Icon to appear in object trees and documentation
• Default Routine Templates for automated code generation
• Appearance in object trees

This feature is beneficial to customers wanting to differentiate between more object types and control the automation aspects based on those types. It's particularly useful in the case of Data Vaults where there are many object subtypes that can be configured in 3D but don't currently have a dedicated object type mapping in RED such as PIT and Bridge tables. This feature also allows setting specific icons for each object subtype which improves both productivity and look and feel.

Scheduler Improvements

Azkaban core and the RED plugin for Azkaban have been improved in this release to enhance the workflows when dealing with abnormal job runs.

Improved Azkaban/RED synchronization

Azkaban to RED metadata synchronization on aborted jobs has been improved, now when canceling jobs directly from Azkaban the RED job metadata is updated to match the external job state. This removes the need to run additional tasks via Azkaban to have the job removed from the 'Running' state in RED and allows further remedial tasks to be performed on the job run, as required, immediately following an abort.

Added support for cleaning up child processes on job cancellations

When a job is canceled directly from Azkaban an optional cleanup script is now triggered automatically by the presence of a host script object in RED matching a specific naming convention. This is beneficial to users who need to kill long running or abnormal jobs in the scheduler but ensure that the underlying child processes for the job are also killed to prevent further unwanted transactions on the source and targets involved in the task.
Job cancellations will now execute the RED metadata host scripts, if present, named:

• wsl_scheduler_job_kill_linux on Linux
• wsl_scheduler_job_kill_win on Windows

Improved job restart workflow

When manually marking a failed task as 'completed' in the RED Scheduler tab for an aborted job, then a restart on this job will now set the job run to 'Succeeded', provided there were no other failures in the remaining tasks to execute. This is useful when resolving a failed task externally and then later continuing the remaining tasks in the job, so that the job then appears as a successful completion in the metadata.

Migrating from Earlier Versions of RED

Note that due to the new PostgreSQL metadata and the external Azkaban-based Scheduler, there is no upgrade path from earlier versions of RED directly to RED 10. Suppose you are an existing customer of WhereScape RED on another metadata platform. In that case, migration tooling will become available soon after this release along with the rollout of procedure-compatible Enablement Packs for selected Target platforms.

WhereScape 3D Compatibility

This release of RED is compatible with WhereScape 3D 8.6.9.1 versions and up for 3D exports to RED but it is recommended to use the latest version 9.0.2.1 of 3D to provide all feature capabilities.

Customer Improvements

This release also includes the customer enhancements and support fixes listed in the following section .

Detailed Changes in RED 10.2.0.0

The following changes have been implemented since 10.1.0.2

 Improvements

•  

Issues