Data360 Govern Product Announcements

ID

L3

Release Notes

MON-1009

 L3REQ-79978

Added a custom filter to get specific users

MON-1164

L3REQ-78721

Large list field dropdowns in asset editors now use lazy loading, fetching values on demand rather than all at once on page load. This applies to asset list fields that require permission checks, where the volume of entries was the primary performance bottleneck.

MON-1249

 L3REQ-80572 

The Bulk Loader now correctly processes and persists field values from the load file, including complex multi-line or special-character content such as SQL expressions, without truncation or corruption.

MON-1000

L3REQ-80235 

The Add button now correctly enables when configuring conditions on conditional transitions, allowing users to add HTTP response-based conditions without interruption.

MON-1250

L3REQ-81214

The tag input handling has been updated to correctly support accented and special characters, ensuring Synonym tags can be saved regardless of the character set used.

MON-766

L3REQ-77861

Tag values are now validated during bulk load, and new tags are correctly assigned to the tag type defined on the field, ensuring data integrity and consistency with manually added tags.

MON-968

L3REQ-79936

The workflow form editor now correctly identifies and opens the selected HTML field for editing. Form deletion logic has also been corrected to accurately evaluate whether any fields are still referenced as transition conditions before blocking deletion.

MON-1381

L3REQ-78765

The DQ score calculation logic has been corrected to ensure that business assets linked to technical assets accurately reflect the same DQ score history derived from the underlying DQ rule results.

MON-983

L3REQ-78530

Users without the required permissions are prevented from adding, removing, or modifying restricted tag types, reducing the risk of unauthorized changes to governed metadata.

MON-1422

L3REQ-82334

Certain Asset Path and Reference List fields were incorrectly showing Error instead of their actual values. This has been resolved - all fields now display correctly as expected.

 MON-1621, MON-1381

L3REQ-78765

Issue fixed for Data Quality score history

• Business Assets now correctly display Data Quality score history in line with their associated DQ rule results.
• Score history is consistent between Technical and Business Assets.

MON-1651

L3REQ-83688

When viewing parent assets, you will now see accurate ownership information for child assets listed in the Children tab, eliminating the need to navigate into each child asset individually to verify ownership details. 

MON-1630

L3REQ-77686

DQ scores displayed in Govern will now be consistently rounded and accurately reflect true quality results. Scores that are not truly 100% will no longer be misrepresented as perfect scores due to rounding artefacts. 

MON-1632

L3REQ-81278

Governance Scores will now be calculated correctly for assets where field values are implicitly set via defaults - particularly relevant for assets created through the API where optional fields are omitted but carry a default value.

MON-13

L3REQ-69680

The workflow engine now correctly handles "Field Change" tasks when an "Add Item" workflow is initiated from an Asset Type context, preventing the unidentified code error.

MON-61

L3REQ-54807

Previously, workflow assignments could only be in one of two states: Pending or Complete. This release introduces the Warning status to provide better visibility into non-critical issues during workflow execution.

• Warning - Triggered when a workflow step completes but with a non-blocking issue, such as:
  • No valid recipients found for an Email Activity

MON-528

L3REQ-75643

The User Administration API now updates the username in sync with the email address when an administrator changes a user's email, ensuring login continuity.

MON-806

L3REQ-78530

L3REQ-81974

Administrators can now control which users are permitted to add tags to assets, based on the tag type.

MON-930

L3REQ-79610

When performing bulk workflow form submissions (e.g., assigning actions to large numbers of assets), you will experience significantly improved reliability and performance, with no more timeouts or unresponsive behaviour under high load.