LastStateChangeTime field of alert/incident should be updated whenever there are changes in the custom or default schema attributes

Requirement:

Currently, in Netcool, the StateChange field is updated either based on pre-defined field updates or whenever there are changes to any schema field. However, as we transition towards AIOps, we have observed that updates to the StateChange field are missed even when important fields are modified. Updates are currently triggered by changes to default fields such as acknowledged, suppressed, severity, and state for alerts, and priority, title, description, and owner for incidents.

A specific issue has been identified where, when an alert is promoted to an incident, the lastStateChangeTime of the alert is not updated. It is necessary for the lastStateChangeTime field of the alert to be updated whenever the alert is added to an incident.

The requirement is as follows:

1. Update the lastStateChangeTime of an alert whenever it is added as part of an incident.
2. Update the lastStateChangeTime of an alert when it becomes part of any correlation.
3. Update the lastStateChangeTime of an alert whenever any custom field or default schema field is modified.
4. Update the lastStateChangeTime of an incident during any custom field or schema field updates.

Benefits:

By implementing these updates, automations can be built to ensure every alert update is sent to an external system. The lastStateChangeTime field can be used as a reliable indicator to track these changes. If the lastStateChangeTime is not updated upon schema field changes—especially during critical events such as when an alert becomes part of an incident or when a custom field changes—there will be delays or missing updates in real time. Currently, updates may only occur when pre-defined fields are modified, which can result in incomplete or delayed information flow to external systems.