Condition Sets fail to correctly evaluate if no telemetry exists for given parameter

Summary

Condition sets do not show any state, not even default status, until telemetry is received. Also, condition sets do not evaluate "is defined" or "is not defined" until telemetry is received. In both cases, this applies any telemetry in the condition set, not just the relevant telemetry for the condition.

Expected vs Current Behavior

Expected behavior is condition sets should indicate default status when telemetry has not been received. Therefore, implementation is as follows.

• Leave condition sets as they are. They will continue to be event-driven on receipt of telemetry
• Modify conditional styling logic to always apply default styling on load
• Allow conditional styling AND static styling, which will be applied when no telemetry has been received
• Add some verbiage to the condition set editor to make it clear that rules only execute on receipt of telemetry.

Steps to Reproduce

1. create a condition set with low frequency telemetry and create a condition the telemetry "is not defined"
2. conditionally style an object in a display, using the conditional set
3. style the default status with a red background
4. style the condition status with a greed background
5. define a static style with a blue backgroun
6. save the display
7. Expected behavior is background is blue, when telemetry is received the background turns to red, but currently you cannot set a static style and default style (red background) will not apply

Environment

• Open MCT Version:
• Deployment Type:
• OS:
• Browser:

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information