Highlight flows that have had their runtime configuration changed

Description

When flows have their configured components changed this change does not take effect until the flow is restarted. There is currently no way of identifying flows which have had their configuration changed, but have yet to be restarted. A simple "*" next to the flow would suffice.

Its possible that the configuration changes can be compared with stop/start changes in the system-event audit to ascertain which ones have been changed and flows not restarted.

Environment

None

Workaround Description

None

Assignee

Unassigned

Reporter

Jeff Mitchell

Labels

None

Trac ticket

None

milestone

None

Workaround Exists

None

Components

Fix versions

Affects versions

Priority

Major
Configure