This document summarizes major improvements and fixes introduced in the PlatformManager release version.
|
Version |
1.95.0 |
|
Release date |
In this document:
New Features and Improvements
|
Improvement Description |
|
|---|---|
|
Integrated a static XML analysis stage into the analysis pipeline that generates structured JSON reports based on a configurable, version-controlled ruleset. |
PFIM-9817 |
|
The IM Update Assistant now features an enhanced user interface that distinguishes between automatic and manual code modifications, requiring user acknowledgment for manual changes before proceeding with the update. |
PFIM-9773 |
|
A new Environment field has been introduced across instances, partitions, and integrations to categorize environments by purpose, such as production, testing, or development. |
PFIM-9685 |
|
Introduced monitoring for project locks and pending messages in Event Orchestration to ensure timely identification of processing delays. |
PFIM-9662 |
|
Enhanced event routing transparency by adding runtime logs to identify workflows that were skipped when multiple active processes were waiting for the same event. |
PFIM-9643 |
Fixed Issues
|
Bug Description |
|
|---|---|
|
Partition entities incorrectly route to the integration flow instead of the partition export flow, causing code analysis to fail with a "No project path found in extracted files" error. |
PFIM-9838 |
|
The Code Analysis tab fails to display results. |
PFIM-9835 |
|
The advanced filter in the New Data Download tool fails to function correctly, as date fields display a time-only picker and certain value input fields remain greyed out. |
PFIM-9832 |
|
IntegrationManager instances remain stuck in a requested stop state and fail to automatically restart when the scheduled shutdown window is too short, resulting in a state mismatch between the system and the user interface. |
PFIM-9829 |
|
The daily report fails to generate and send via email when encountering empty sub-aggregations in the data source, despite the activity log incorrectly reporting a successful configuration save. |
PFIM-9826 |
|
The system fails to save or deploy advanced filters when a column's default Boolean value remains unchanged during filter creation. |
PFIM-9783 |
|
The IntegrationManager instance health status incorrectly displays as Responding instead of Warning when no routes are deployed, due to the UI reflecting outdated daily snapshots rather than live state. |
PFIM-9163 |