Conditional Set "output" is wrong

[charlesh88]

Summary

When no data is present for telemetry in use by a Condition Set (CS), the set says it's outputting a default value (orange arrow), but it actually is not. Note that the Default condition is not hilited (green arrow).

LAD Table view of the Condition set shows that no data is available:

Adding the CS to a Display Layout as an alpha shows that no value is being output:

Expected vs Current Behavior

The CS should not erroneously report an output value, but instead should be blank or "---". CS views currently only output a value when they have an input, such as data. This makes sense: the CS needs an input to determine its output frequency.

Related Issues

• This behavior has side-effects on how Conditional Styling works.
• The pivoted LAD view of the CS itself is counter to how that control works in all other views: that view shows the output of the compositional children of the CS, not the output of the CS itself. Condition Set LAD Table "view switch" isn't consistent with other view types #5924 covers this problem.

Steps to Reproduce

1. Make or edit a CS and include one or more telemetry points that don't have any data currently. Give it at least one condition besides the default.
2. Save the CS, then nav away and back.
3. Observe: the CS reports an output of Default, but shouldn't.

Environment

• Open MCT Version: 2.0.5, 2.1.2
• Deployment Type: MMOC, /latest
• OS: any
• Browser: any

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

[shefalijoshi]

@charlesh88
What is the expected behavior for the following scenarios?

1. There is data for one or more conditions and the CS is working as expected highlighting the right condition, then the conditions with data incoming are deleted so that there are no more conditions with incoming data.
2. There were previously conditions that have now all been removed (leaving only Default).
   Should we highlight Default in these cases? or Should we fall back to '---'/empty?

[shefalijoshi]

Update with discussion:
The issue here is whether we should output anything at all if there is no input data/telemetry flowing into the condition set.
This discussion has not yet been closed.

[scottbell]

I was able to reproduce it. Looking into it now:

Showing_Default.mov

[scottbell]

@charlesh88 If you could please, let me know your thoughts on @shefalijoshi's scenarios. I'll look into the naive case first (no telemetry at all/ever).

[shefalijoshi]

@charlesh88 , @scottbell and @shefalijoshi Talked about this and the short term solution is to change the output of the condition set view to ---

[charlesh88]

Testing Notes

1. Make or edit a CS and include one or more telemetry points that don't have any data currently, or that has no telemetry in it. Give it at least one condition besides the default.
2. Save the CS and exit editing. Nav away and back to it and view it in browse mode.
3. Verify that the CS reports "---" as its output, and is not matching the Default (or any other) condition.
4. Use the Condition Set to conditionally style an element in a layout. Verify that after saving, navving away and back that the element is not using the Default style set by the CS.