Description
The "Engine Time" field on the BPM engine detail view is hidden entirely when the engine's time could not be retrieved (e.g. the engine is unreachable), instead of indicating that the value is unavailable. The same happens for the "Engine Time" column in the engines list — the cell is simply left blank.
This makes it impossible to distinguish "engine time not fetched / engine unreachable" from "this field doesn't apply to this engine" — the UI gives no indication that something failed.
Steps to reproduce
- Configure a BPM engine with an unreachable Base URL (e.g.
http://localhost:8052/engine-rest, nothing running on that port).
- Open "BPM engines" list.
- Open that engine's detail view (General tab).
Actual behavior
- In the engines list, the "Engine Time" column is empty for the unreachable engine (see attached screenshot:
local2 and local rows).
- In the engine detail view, the "Engine Time" field is not shown at all for the unreachable engine (see attached screenshots: compare
BPM Engine, which has the field, with local2, which doesn't).
### Expected behavior
When the engine's time cannot be retrieved, the "Engine Time" field/column should remain visible and clearly indicate that the value is unavailable (e.g. a placeholder text or an error/warning state), rather than disappearing.
Impact
Users cannot tell whether an engine's time is simply not shown by design or whether the engine connection actually failed — the missing field looks like normal UI, not an error state.
Description
The "Engine Time" field on the BPM engine detail view is hidden entirely when the engine's time could not be retrieved (e.g. the engine is unreachable), instead of indicating that the value is unavailable. The same happens for the "Engine Time" column in the engines list — the cell is simply left blank.
This makes it impossible to distinguish "engine time not fetched / engine unreachable" from "this field doesn't apply to this engine" — the UI gives no indication that something failed.
Steps to reproduce
http://localhost:8052/engine-rest, nothing running on that port).Actual behavior
local2andlocalrows).BPM Engine, which has the field, withlocal2, which doesn't).When the engine's time cannot be retrieved, the "Engine Time" field/column should remain visible and clearly indicate that the value is unavailable (e.g. a placeholder text or an error/warning state), rather than disappearing.
Impact
Users cannot tell whether an engine's time is simply not shown by design or whether the engine connection actually failed — the missing field looks like normal UI, not an error state.