Product: Mingcedar Scan SCAN
Select the project and confirm how results are saved | Mingcedar Scan
Select a compatible .ap* project, .zap* archive, or its directory. If the directory has several top-level candidates, one is chosen automatically; verify the resolved full path before scanning.
<div class="manual-doc-article manual-doc-article-section"><h2 id="workspace">Step 2: Select the project and confirm how results are saved</h2>
Confirm the project source before scanning. Save a result session for later review, or choose a file location when exporting the current result.
<div class="doc-card-list">
<article class="doc-card">
<h3 id="workspace-item-1">Supported project sources</h3>
<p>Select a compatible .ap* project, .zap* archive, or its directory. If the directory has several top-level candidates, one is chosen automatically; verify the resolved full path before scanning.</p>
</article>
<article class="doc-card doc-card-warn">
<h3 id="workspace-item-2">Project-source requirements</h3>
<p>Keep the project or archive at a stable local path and retain an original backup. Opening an older version invokes TIA upgrade functionality; use a project copy or archive when migration is needed. Do not move, synchronize over, or edit the project during scanning.</p>
</article>
<article class="doc-card">
<h3 id="workspace-item-3">Save and load result sessions</h3>
<p>Sessions save results, configuration, and review state. Loading or restoring a session marks its addresses as unverified. You can filter or export review lists; communication import requires a fresh scan and rule review.</p>
</article>
<article class="doc-card">
<h3 id="workspace-item-4">Choose the export location when exporting</h3>
<p>The desktop workspace does not require an output directory before scanning. Choose the Excel, CSV, or JSON destination when selecting Export Current Result. Batch CLI output uses <code>outputDir</code> in its configuration.</p>
</article>
<article class="doc-card">
<h3 id="workspace-item-5">Behavior after the project path changes</h3>
<p>Project paths are normalized to full paths. Changing the path resets tree selection and clears results; rescan before filtering or exporting.</p>
</article>
<article class="doc-card">
<h3 id="workspace-item-6">Project path during an active scan</h3>
<p>Project-path controls are disabled during scanning and restored on completion or cancellation. Verify the project name and full path in the completion status before review.</p>
</article>
</div>
</div>