Product: Mingcedar CONTROL

Event records: query, trace, and export | Mingcedar

Location: Configuration Center → Event Records (event:view permission). The default scope is User operations and the initial period is the last 30 days. Search, outcome, and record-scope filters apply to loaded records.

Published 2026-10-25T12:48:42.630221358Z Updated 2026-10-25T12:48:42.630220627Z

<div class="manual-doc-article manual-doc-article-section"><h2 id="event-records">Operating guide: Event records: query, trace, and export</h2>

Trace operations by time, actor, subject and outcome. Query event records, alarm history and trends separately.

<h3 id="events-query">1. Select the query scope</h3>

<p>Location: Configuration Center → Event Records (event:view permission). The default scope is User operations and the initial period is the last 30 days. Search, outcome, and record-scope filters apply to loaded records.</p>

<ol>

<li>Select a time range such as the last 24 hours, with start no later than end.</li>

<li>Choose User operations for user configuration/login, System activity for background work, or All when needed.</li>

<li>Set Record Source to Operation or Login and, when relevant, Event Type and Write Channel. Outcome includes Completed, Recorded, Not completed, Partial, In progress, and Unconfirmed.</li>

<li>Enter an actor, action, or subject in Search and click Query.</li>

</ol>

<p class="doc-step-result"><strong>Expected result</strong> Matching records show time, outcome, action, actor and summary.</p>

<div class="doc-step-troubleshooting"><p><strong>If the result differs</strong></p><ul>

<li>No records: relax narrow filters and check record scope and timezone. If loaded rows do not match but more pages exist, continue loading before concluding the record is absent.</li>

</ul></div>

</article>

<h3 id="events-write-trace">2. Trace a runtime write</h3>

<p>Trace an existing Runtime Write record through its request, outcome, and current Tag value.</p>

<ol>

<li>Choose Runtime Write as Event Type.</li>

<li>Select the channel used, such as Custom Page, PPT Runtime, Integration Script, or Runtime Popup.</li>

<li>Narrow the time range, search by Tag or actor, and open Details.</li>

<li>Compare request target, requested value, summary, and Items not completed. If a command identifier is present, compare it with the caller’s result.</li>

<li>Inspect the current value in Tag Test separately; later operations may have changed it.</li>

</ol>

<p class="doc-step-result"><strong>Expected result</strong> Check the request, outcome and field state separately. Recorded does not mean succeeded.</p>

</article>

<h3 id="events-export">3. Load more records and export</h3>

<p>Export collects records using the active query criteria. Batch size is not the total number of records in the selected period.</p>

<ol>

<li>While browsing, scroll to load more records or click Load next page. Export independently collects matching records for the current criteria; you do not need to load every list page first.</li>

<li>Review the range and filters, then click Export records.</li>

<li>Wait for completion and inspect the downloaded file’s times, subjects, and record count.</li>

<li>If the browser export limit is exceeded, split the query by time and export each interval. An interrupted or cancelled export does not produce a complete file.</li>

</ol>

<p class="doc-step-result"><strong>Expected result</strong> Check file scope and export status. Retention policies determine record availability.</p>

</article>

</div>

<strong>Figure 1: Query Event Records</strong>

<p>The top bar has search, scope, outcome, source, event type, write channel, and time filters. Loaded records appear below with Query and Export actions.</p>

</figcaption>

</figure>

</div>