8.01.00

April 2025

New Features

  • Patch notification:
     Users get notification of the latest patch under the notification panel and can apply the patch to the specific environment for reducing manual effort and ensuring consistent updates.  [SWCDMPC-4569]
  • Default Remedies column in Alarm table:
     The Remedies column is now available by default in the alarm table if the Knowledge Graph bundle is enabled. [SWCDMPC-3644]
  • Unification of alarm and rule events in graph:
     Graph and events API have been modularized to better log events on the graph database from different sources such as rules & alarms. [SWCDMPC-4639]
  • Unified graph database storage
    : Asset graph definitions are now stored in the unified project database instead of separate databases.  [SWCDMPC-4100]
  • Hierarchy upload in Asset Hierarchy page: 
    Bulk hierarchy creation in Unified Semantic Model Projects is now supported through file uploads. [SWCDMPC-4985]
  • The new catalog version
     introduces public and private workspaces. [SWCDMPC-3802]
    • Projects can now be linked to a private workspace using an access token, and project- or client-specific artifacts can be published or maintained separately.
    • The review and approval process is implemented within the workspace, and approved artifacts can be moved from the private workspace to the central workspace and can be cloned from the central workspace.
  • REST API Trigger in Rule Editor:
     The Rule now supports configuring a REST API within the rule editor, which can be triggered based on specified execution conditions.  [SWCDMPC-5071]
  • Microservice Plugin option in REST API:
     Users can now select a microservice as a plugin type, and the backend will save the microservice URL as the REST endpoint.  [SWCDMPC-5072]
  • Connection numbering in pipeline flow configuration:
    Connections between source and target components in the pipeline flow configuration are now numbered for better visibility and traceability.  [SWCDMPC-5701]
  • Git Target creation in Settings:
     Users can now create Git targets directly from the plugin settings. [SWCDMPC-3786]
  • Plugin version management:
     Now users can select and roll back increments for better version control.  [SWCDMPC-3789]
  • External portal for plugin artifact creation:
    An external portal has been introduced for creating plugin artifacts. [SWCDMPC-2394]
  • Drag-and-drop Kubeflow Pipeline creation:
     Users can now drag and drop Kubeflow components to create pipelines on the FTDM portal. [SWCDMPC-1626]
  • First or last data point retrieval:
    Rules can now retrieve the first or last data point within a configured time period. [SWCDMPC-5327]
  • Custom time storage for `last_day` rule function:
     When "CUSTOM" is passed to the `last_day` rule function, the retrieved data is stored at the configured custom time. [SWCDMPC-5328]
  • Default installation of Control Engine:
     The Control Engine is now installed by default as part of the iLens-Agent installation, ensuring seamless integration with edge module deployments.  [SWCDMPC-5122]
  • Writeback feature for Modbus server:
    Users can now write back rule output data from the platform directly to a Modbus Server, enabling bidirectional data flow. [SWCDMPC-4438]
  • Control Engine support for on-premises installation:
     The Control Engine now supports writeback functionality in on-premises installations, ensuring consistent behaviour across deployment models. [SWCDMPC-4445]
  • Gateway redundancy:
     A redundancy feature has been introduced for primary gateways. If the primary gateway (NUC/Diode) goes offline, secondary gateways will automatically take over data acquisition to prevent data loss.  [SWCDMPC-4450]
  • InfluxDB v2 support:
      A new data connector has been introduced to fetch time-series data from InfluxDB v2 and upload it to the platform’s time-series database. [SWCDMPC-6365]

Enhancements

  • Streamlined user and user role creation processes for better administration.
  • Added restriction on password length to enhance security.
  • An SSO user role is now created for new projects to manage access permissions for SSO-based roles.
  • New functionality highlights nodes eligible for deletion that enables bulk-delete operations for efficient graph management.
  • Enhanced alarm visualization now displays causal relationships, root causes, and recommended remedies in an interactive network view.
  • Added flexible filtering capabilities by both parameters and hierarchy levels to focus on relevant nodes and relationships.
  • Performance optimization implemented to improve custom app loading times.
  • Users can now be associated with RDBMS targets to improve access control.
  • Column headers in downloaded Excel reports are now frozen for easier navigation and better data visibility.
  • Unread MQTT notifications are now retained on the platform for a specified duration.

Fixed Anomalies

  • The user fails to select the empty asset model (without tags) in the asset creation page of the Unified Semantic Model project.
  • "Acknowledge All" functionality incorrectly acknowledges all open alarms, not just pending occurrences of specific Alarms.
  • The Asset Model module may permit the creation of rule templates with duplicate names, which can cause confusion.
  • Data not showing in Data Explorer:
     pushed data were not appearing in the Data Explorer page.
  • Device online but pipeline not deploying:
     In certain scenarios, channel pipelines failed to deploy even when the device was online.
  • Incorrect event start time:
     event Explorer showed events starting from 01-01-1970 05:30:00, causes wrong duration calculations.
  • Alarm notifications missing for some users:
     Triggered alarms did not notify all assigned users.
  • Data export issues:
    At certain scenarios, empty files were downloaded even when data was available in Data Explorer.
  • Unable to generate widget reports:
    some users can't generate Widget Reports.
  • Pipeline deployment failure:
    Newly created hierarchies in Graph Model projects prevented pipeline deployment.
  • Asset model cloning errors:
     Cloning an asset model caused duplicate parameters and prevented linking to equipment.

Known Issues

  • Patching feature:
    Once a patch is accepted by the user, the action cannot be reverted.
  • Alarms & Notifications:
    Duplicate alarm notifications for data repetition, "Acknowledge All" incorrectly affecting all alarms, alarm count mismatches, and delayed remedy population.
  • Event & Knowledge Graph:
    If many users work at the same time or there are multiple projects, some old connections may not close properly, the deleted events node doesn’t notify on a Graph setup screen as deleted, and when events, rules, and alarms are not configured with end event pairs, the system may not handle them correctly when ingesting into the knowledge graph.
  • Data & Asset problems:
     Asset Type not saving, AG Grid filtering issues, Data Mapping errors, and Modbus server data fetch failures.
  • UI & Usability Bugs:
     Node Action Menu overflow, disabled app title toggle not working, missing tooltips, incorrect hierarchy display, and invalid GraphQL data acceptance.
  • Documentation Gaps:
     Missing details on Execute tab, rule execution output, and rule history execution.
  • System & Workflow Errors:
    Audit log omissions, blank phone field for SSO users, and Live EPS widget data issues.
  • After deleting a project, the system may prevent the creation of a new user with the same username.

Known Limitations

  • Auto Patch feature:
    Currently supported only in Online environments.
  • Default Control Engine installation:
     Supported only on Windows and Ubuntu operating systems.
  • High availability or auto-scaling for graph database server.
  • Higher latency for events to appear on the platform when knowledge graph stack is installed. This is due to the slowness in ingestion of events to the graph database (Current measured throughput - 60 events/min).
  • Modbus Server Writeback feature:
    • Minimum writeback frequency is 10 seconds.
    • Bulk write operations for tags are not supported.
  • Entity deletion from Analytical Data Model screen:
     User cannot delete already created entities from new graphql upload. In current version it only removes the link to the existing nodes.
  • Catalog feature:
     Currently supported for Asset Model, Apps, and Dashboards with some limitations. After cloning apps and dashboards from the catalog, tag mapping and certain configurations will need to be updated manually.
  • The Unified Semantic Model project doesn’t support all the features supported by the fixed model.
  • The Knowledge Graph functionality is limited to the fixed model.
  • Hierarchy level access restriction is supported only at hierarchy levels. The unified semantic model projects list equipment but doesn’t support the access restrictions at hierarchy level.
  • The bulk upload feature supports creating hierarchies but doesn't allow editing or deleting existing ones.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal