Mingcedar

Product: Mingcedar Studio DESIGNER

Shared options: data quality, conditions and visibility | Mingcedar Studio

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

Published Updated

<div class="manual-doc-article manual-doc-article-section"><h2 id="shared-options-quality-border-active-post-operations">Feature: Shared options: data quality, conditions and visibility</h2>

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

<div class="doc-card-list">

<article class="doc-card">

<h3 id="shared-options-quality-border-active-post-operations-item-1">Data quality and display state</h3>

<p>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.</p>

<ul class="doc-related-links">

<li><a href="/en/ppt/manual/script-text/">Script Text</a></li>

<li><a href="/en/ppt/manual/state-color/">State Color</a></li>

</ul>

</article>

<article class="doc-card">

<h3 id="shared-options-quality-border-active-post-operations-item-2">What Condition means</h3>

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

<p class="doc-table-hint">Scroll horizontally to view the full table</p>

<div class="doc-table-scroll" role="region" aria-label="What Condition means" tabindex="0"><table class="doc-reference-table">

<thead><tr><th scope="col">Behavior</th><th scope="col">Role of Condition</th></tr></thead><tbody>

<tr><th scope="row">State Color</th><td>Selects an enabled TRUE or FALSE appearance. Enable FALSE in Apply result to apply it; false does not inherently stop display.</td></tr>

<tr><th scope="row">Script Text</th><td>Controls whether this text behavior executes.</td></tr>

<tr><th scope="row">Set Variable on Click / Write Tag</th><td>Controls whether the user action executes; false skips it.</td></tr>

<tr><th scope="row">Move / Rotate / Scale</th><td>Controls whether the geometry behavior applies; enter the numeric input separately in Source value or Rotation input.</td></tr>

</tbody></table></div>

</article>

<article class="doc-card">

<h3 id="shared-options-quality-border-active-post-operations-item-3">Three visibility options</h3>

<p class="doc-table-hint">Scroll horizontally to view the full table</p>

<div class="doc-table-scroll" role="region" aria-label="Three visibility options" tabindex="0"><table class="doc-reference-table">

<thead><tr><th scope="col">Option</th><th scope="col">Trigger and scope</th></tr></thead><tbody>

<tr><th scope="row">Hide when quality is bad</th><td>Hides on bad associated data quality, in display behaviors that expose this option.</td></tr>

<tr><th scope="row">Hide when disabled</th><td>Hides when the condition is false, for example in Set Variable on Click. Skipping an action does not otherwise imply hiding its component.</td></tr>

<tr><th scope="row">Hide outside range / Hide outside rotation range</th><td>Hides when Move / Rotate input is out of range. Scale currently has no such option.</td></tr>

</tbody></table></div>

</article>

<article class="doc-card doc-card-warn">

<h3 id="shared-options-quality-border-active-post-operations-item-4">Expressions and verification</h3>

<p>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.</p>

<ul>

<li>Condition must return a Boolean immediately; do not use fetch, promises or timers.</li>

<li>Condition does not replace Mingcedar write permissions or equipment interlocks.</li>

<li>Move / Rotate / Scale currently have no separate Post Operations input.</li>

</ul>

<div class="manual-code" data-code-language="text"><div class="manual-code-toolbar"><span>Script Text → Condition</span><span class="manual-code-tools"><small>Text</small><button type="button" data-copy-code data-copied="Copied" data-failed="Select and copy the code" aria-label="Copy code: Script Text → Condition">Copy code</button><span class="manual-code-status" role="status"></span></span></div><pre tabindex="0" class="docs-code-block shiki github-light" style="background-color:#fff;color:#24292e" tabindex="0"><code><span class="line"><span>ReadTagQualityGood("PLC_LINE01.PUMP01.SPEED")</span></span></code></pre></div>

</article>

</div>

</div>