Skip to content

Shared options: data quality, conditions and visibility

Understand data-quality indicators, the behavior-specific meaning of Condition, and visibility options. Available controls depend on the behavior editor.

FeatureDocumentation revised: 2026-10-21

Feature: Shared options: data quality, conditions and visibility

Understand data-quality indicators, the behavior-specific meaning of Condition, and visibility options. Available controls depend on the behavior editor.

Data quality and display state

Data quality indicates whether Tag data is valid; process states such as running, stopped and alarmed are separate. In Script Text, select Use quality outline colors under Quality Override and set Good and Bad colors. State Color provides Follow data quality (border / hide), with an option to hide on bad quality.

What Condition means

Condition has a different role in each behavior. Use the table and the corresponding editor to configure it.

Scroll horizontally to view the full table

BehaviorRole of Condition
State ColorSelects an enabled TRUE or FALSE appearance. Enable FALSE in Apply result to apply it; false does not inherently stop display.
Script TextControls whether this text behavior executes.
Set Variable on Click / Write TagControls whether the user action executes; false skips it.
Move / Rotate / ScaleControls whether the geometry behavior applies; enter the numeric input separately in Source value or Rotation input.

Three visibility options

Scroll horizontally to view the full table

OptionTrigger and scope
Hide when quality is badHides on bad associated data quality, in display behaviors that expose this option.
Hide when disabledHides when the condition is false, for example in Set Variable on Click. Skipping an action does not otherwise imply hiding its component.
Hide outside range / Hide outside rotation rangeHides when Move / Rotate input is out of range. Scale currently has no such option.

Expressions and verification

For example, enter the expression below in Script Text Condition to evaluate its text only when the specified Tag has good quality. Replace the example name with your project Tag and verify both good and bad quality. Configure the corresponding Quality Override when a persistent quality indication is required.

  • Condition must return a Boolean immediately; do not use fetch, promises or timers.
  • Condition does not replace Mingcedar write permissions or equipment interlocks.
  • Move / Rotate / Scale currently have no separate Post Operations input.
Script Text → ConditionText
ReadTagQualityGood("PLC_LINE01.PUMP01.SPEED")

Click the image again or press Esc to close