Data360 Govern Product Announcements

 View Only

Data360® Govern patch applied to the PROD environment on April 24, 2026.

  Thread closed by the administrator, not accepting new replies.
  • 1.  Data360® Govern patch applied to the PROD environment on April 24, 2026.

    Posted an hour ago
    Edited by Product Communications an hour ago
    No replies, thread closed.

    April 24, 2026

    D360 Govern – Patch Notice

    Abstract 

    Precisely announces a patch release for Data360® Govern applied to the PROD environment on April 24, 2026.

    Overview of Features and Functionality 

                                                                                                               

    ID

    L3

    Release Notes

    MON-825

    L3REQ-77346

    Fixed an issue where clicking a data profile bar to view historical values over time had no effect. The timeseries graph now displays correctly when multiple data profile records exist for an asset and the data profile dates fall within the last year.

    MON-811

    L3REQ-78189

    Fixed an issue where valid assets were wrongly excluded in self-referencing relationships. This prevented creating multi-level hierarchies in the UI (though it worked via API). The filter now works correctly for same-type relationships.

    MON-20

    L3REQ-52824

    Fixed an issue that caused "Score Changed" workflows to be incorrectly triggered for assets with inactive scores. Workflows will now only start when a score is active.

    MON-727

    L3REQ-77634

    Fixed an issue where previous role holders remained visible after moving an asset to a different domain. Old ownership entries are now correctly removed.

    MON-135

    L3REQ-73624, L3REQ-76541, L3REQ-78190, L3REQ-73066, L3REQ-78355, L3REQ-74166

    Improved asset, relationship, and rule result processing, both in real-time and batch operations.

    MON-744

    L3REQ-77643

    Fixed an issue where adding a reverse relationship between same-type assets deleted the original relationship. Both directions are now preserved.

    MON-959

    L3REQ-79940

    Fixed an issue where filtering by object type in the Change Log returned empty results. The filter now correctly returns matching records.

    MON-848

    L3REQ-77634

    Added a Policy column to the Ownership tab to distinguish entries from multiple policies with the same role and condition, resolving confusing duplicate owner display.

    MON-858

    L3REQ-78399

    Fixed an issue where newly assigned ownership was not visible until the page was refreshed.

    MON-733

    L3REQ-77793

    Fixed an issue where the Impact dropdown showed only the default value. All available options now display correctly.

    MON-849

    L3REQ-77457

    Improved performance when exporting hierarchy assets (Models and Policies).

    MON-826

    L3REQ-78491

    Fixed an issue where role search in the Add Security Policy dialog did not return all matching policies in the list.

    MON-901

    L3REQ-79853 
    L3REQ-79855

    Fixed an issue where URLs embedded in HTML fields and fields with <> characters failed to export to Excel correctly. The Excel third party library has been updated.

    MON-805

    L3REQ-78443
    L3REQ-77391

    Enhanced the modal dialog when creating or updating roles under Administration > Security > Roles and Policies. Asset Type Overrides more clearly outlines the permissions that apply and provides an improved view of selected asset types.

    MON-898

    L3REQ-78530

    Tags have been restored on global search result cards.

    MON-874

    L3REQ-78808

    Fixed an issue where editing a datetime field shifted the value by -2 hours. Timezone conversion now works correctly.

    MON-1229

     

    The getAsset API now returns dates in ISO format (YYYY-MM-DD HH:MM:SS) for better consistency and easier integration with other systems. For example: 2020-07-16 09:56:46

    MON-1267

    L3REQ-81356

    Fixed an issue where duplicate dataset rows appeared in search results when a search term matched multiple tags on the same dataset.

    MON-1244

    L3REQ-80984

    Fixed an issue where updating a reference asset used as a lookup did not refresh the displayed value on the asset or asset type.

    MON-1495

    L3REQ-81985

    Fixed an issue where relation lookups froze or flickered during interaction. Custom theme row selection colors now work correctly.

    MON-1464

    L3REQ-82655, L3REQ-82296

    Added an "Uploaded By" field to the bulk upload information screen so you can see who initiated each bulk load operation.

    MON-1457 

    L3REQ-82287

    Fixed an issue where the Rebuild Display Values process would set the display value of Reference List Items to the default display format: "Code" regardless of the actual Display Format of the Reference List Type. This caused list fields to display incorrectly on assets.

    MON-1413

    L3REQ-82293

    Fixed an issue where this option did not remain selected: "Apply this measure to all assets, using the first matching condition group to determine measure weight". After choosing this option, the system automatically reverted to: "Only apply this measure to assets that match a condition group."

    MON-1406 

    L3REQ-82655

    Fixed an issue that caused a mismatch between the bulk load action list displayed in the user interface and the type list used by the bulk load POST endpoint in Swagger. previously, the Swagger Bulkload API type dropdown was still showing old options and missing the new Group Membership and Group Management bulkload types. All new bulkload types are now available in the Swagger UI.

    MON-64

    L3REQ-73960

    Added Counter field type support to the "Field from Relationship" configuration. Previously only the Name field appeared in the dropdown when configuring a field from a related asset with a Counter type field.

    MON-1516

     L3REQ-82771

    Fixed an issue where the status badge failed to display in some cases. The status badge now displays if either the API Name or Field name is "status". If both are present, the value from the Field name is used.

    MON-1508

     

    L3REQ-82669

    Fixed an issue where an "Object reference not set to an instance of an object" error occurred when using a custom bulk upload template to load datasets. Custom templates that worked previously now load successfully without errors.

    MON-1505

     

     L3REQ-82296

     

    Added a "Note" section to the bulk upload information screen to allow you to include contextual notes alongside each bulk upload operation.

    MON-1460

     

    L3REQ-82332

     

    Fixed an issue that caused repeated errors when opening the Profiling tab for assets with profiling enabled. The Profiling tab now loads correctly without errors.

    MON-1424

     

    L3REQ-82336

     

    Restored the bulk upload screen to its original landscape layout. A recent change had switched it to a cramped portrait view, causing readability and usability issues.

    MON-1414

     

    L3REQ-81868, L3REQ-82282, L3REQ-82296

     

    Added a new Tag Management action to the bulk upload feature, allowing you to bulk append or remove asset tags via Excel. The template includes Asset ID and tag fields for the selected asset type. Tag removal only removes asset–tag references, actual tag definitions are preserved.

    MON-1404

     

    L3REQ-82157

     

    Fixed an issue where the status badge would no longer display if the Status field's display name was changed from the default "Status". The badge detection now correctly checks the field type rather than relying on the display name match.

    MON-1292

     

    L3REQ-81310

     

    Fixed a performance issue where user groups with a very large number of members (2500+) failed to load in the tab view and were only viewable in the details panel. Pagination and member listing now work correctly for large groups.

    MON-1557

     

    L3REQ-82565

     

    Fixed an issue where workflows with the "Item Changed" trigger and "value changed" conditions did not initiate when you updated the specified field value.

    MON-1539

     

     L3REQ-82913

     

    Fixed an issue where uploading rules via bulk upload created duplicates instead of updating existing rules when you configured Rule ID as the key field.

    MON-1521

     

    L3REQ-82631, L3REQ-82525

     

    Fixed an issue where Asset Ancestry displayed incorrect lineage information when you changed filters.

    MON-1000

     

    L3REQ-80235

     

    Fixed an intermittent issue where the "Add" button for adding conditions on an HTTP response conditional transition was disabled. The button is now enabled and functional when configuring conditional workflow transitions.

    MON-766

     

    L3REQ-77861

     

    Fixed two issues with tag bulk load processing. Tag values are now validated correctly during bulk load, and new tags are added to the appropriate tag type for the field instead of being placed under the General tag type.

    MON-1606

     

    L3REQ-80984

     

    Fixed an issue where updates to Reference List items were not reflected on some assets when required fields had been introduced after those assets were created. Reference List updates now apply correctly in these cases.

    MON-1600

     

    L3REQ-83234

     

    Fixed an issue where a deleted user still appeared in the resource/tag suggestion list despite being removed from the Users administration. Deleted users are no longer returned as tagging resources.

    MON-1546

     

    L3REQ-82979

     

    Fixed a case-sensitivity issue in bulk upload where using a different letter case in an asset name could create a duplicate record instead of updating the existing asset. Asset name matching is now handled case-insensitively during bulk upload.

    MON-1422

     

    L3REQ-82334

     

    Fixed a display issue in the UAT environment where certain fields were showing an error instead of their actual values. Asset Path and Reference List fields now show the correct information as expected.

    MON-959

    L3REQ-79940, L3REQ-81553

    Fixed an issue where filtering the Change Log by the Object field could show no results, even when matching records were available.

    The filter now works correctly and displays the expected results.

    MON-1584

    L3REQ-79978

    The Security Owners API now supports filtering, allowing you to query owners by role, group, resource, rule, override status, and more - with support for AND/OR logic across multiple conditions.

    MON-1433

    L3REQ-66554

    Fixed an inconsistency in the Relationships API response that caused integration failures with Data360 Analyze. Integrations using the built-in Data360 Govern paging configuration will now work seamlessly without requiring manual workarounds.

    MON-1581

    L3REQ-82282

    User can now use a tag's unique identifier (UID) in place of the tag name when bulk uploading tags. This makes bulk tag uploads more reliable and flexible, particularly in environments where tag names may change or contain special characters.

    MON-1641

    L3REQ-83683 

    Fixed an issue where date field values appeared blank on the asset list view, even though the correct value was visible on the asset details page. Date fields now display consistently across all views.

    MON-1657

    L3REQ-83185, L3REQ-83838, L3REQ-83566

    Fixed an issue where pasting a screenshot or image into a rich text (HTML) field on certain asset types would cause a save error. You can now paste images into rich text fields without interruption.

    MON-745, MON-818, MON-1532

    L3REQ-77686

    The Data Quality (DQ) score for a rule is currently displaying inconsistent values across different sections of Data360 Govern.

    On the Asset Definition page, under the Scoring tab, the DQ Score is shown as 100%, whereas the Information panel calculates it as 99.98%.

    Similarly, in the Relationship tab, the Information panel displays the DQ Score as 99.9%, while the Score badge shows it as 100%, creating a discrepancy.

    In the Asset List panel, the score for an individual asset is displayed as 100%, whereas the Information panel reflects a DQ Score of 99.9%.

    Similar inconsistencies may exist on other screens as well. These will be addressed in upcoming releases.

    MON-1493

    L3REQ-82468 

    The Role editor screen has been updated to allow setting a default role when "AvailableToAll" is not selected and requires non-zero override permissions. The button now lets users save the role without needing to select the default permission.

    Performance Improvement

    1. Previously, promotion also added the asset's tag. Now, tags are not included in promotion.
    2. Group Membership was previously treated as a User/Group action. Now, Group Management and Group Membership are separate.
    3. When uploading Model or Policy assets, parent assets must exist before creating child assets. Previously, both could be uploaded together.

    Known issue 

    When completing workflow assignments in bulk (e.g., 1000 assets), the assignments remain incomplete even after the user marks them as done.
    Workaround : Completing the assignments individually via API or User interface.

    Complete fix on this will is planned for upcoming release

    Availability 

    The patch will be applied to Data360® Govern PROD environment on April 24, 2026,

    This release includes important performance improvements, overhauling the ingestion of assets, relationships, rule results, and other items to provide much faster data processing and updates, whether in real time or in batch.  Additional features are detailed in the release notes.

    This is the final step following the Feb 18 release and patches to DEV/UAT earlier this year.

    The Production rollout is scheduled for Friday, April 24, starting in the evening (EDT), and you might see some slowdowns in PROD, like pages loading slowly. 

    We recommend that all users prepare by reviewing the release documentation. 

    Minimum Requirements 

    Please refer to the Data360® Govern product documentation available in the Precisely Help Centre for details.

    If you would like technical assistance, please contact the Precisely Global Support team at Precisely Support. 

    Product documentation is available in the Precisely Help Center at help.precisely.com.