Define what is missing
Distinguish a package that is not available for download, an installation that did not complete and an installed item that is not visible in the intended selection. Record the application and module where you expected it, rather than describing all three as a missing library.
Identify the exact package and component requested by the authorized workflow. Do not select a similar item to complete a case, and do not copy a colleague's unidentified library folder into a managed production setup.
Documented installation and release boundaries
exocad's Library Manager wiki describes selecting packages, installing them, waiting for the download/installation status to reach 100 percent and restarting the software to use recently installed libraries.
The official CAD library directory targets the latest software version and warns that older-release and legacy-package applicability may differ. Its manual-download route has license/upgrade requirements. These statements do not prove that a specific package is eligible, installed in the intended application or available in every region.
Diagnostic sequence
Compare the official package identity and date with the requested component and installed release. Record whether the documented installation reached completion. Coordinate a software restart with the administrator after work has been saved and the restart is authorized.
Reopen the intended application and inspect the specific selection. If the item is still absent, provide the supplier with the package, release, module, completion observation and expected selection. Ask for applicable installation guidance rather than changing paths or removing other packages based on guesswork.
| Check | Evidence or next decision |
|---|---|
| Expectation | Package and component; intended product/module and selection. |
| Acquisition | Official source, package date and supplier applicability. |
| Installation | Observed status and authorized restart; no credentials in worksheet. |
| Outcome | Exact item visible or absent; supplier question and held decisions. |
A bounded investigation example
Hypothetical example: the download list reports completion, but a designer looks for a component in another installation. The note records both application identities and asks the administrator to confirm the managed target. No claim is made that completion in one application proves installation in another.
When the item becomes visible, continue the component-identification and receiving review. Visibility answers a software availability question; it does not demonstrate that the physical scan body matches, the component fits or the proposed manufacturing route is approved.
Limitations and Louie validation
Louie validation pending — unverified locally. Louie/admin must observe Library Manager completion, application restart and the exact expected selection in the installed release. Supplier confirmation is needed for older/legacy packages or uncertain entitlement. A visible item is not physical fit or Pristine workflow validation.
The worksheet is blank and contains no patient data or executable settings. Examples are hypothetical, not tested Pristine cases. Actual prescriptions, applicable manufacturer instructions and responsible approvals govern design and production.
Source notes
Official sources checked October 6, 2026. Dates and document scope are identified below. A current source check does not establish installed-release applicability or tested Pristine compatibility. Worksheets and hypothetical examples are original editorial guidance.
Prepared by Pristine Dental Design · October 6, 2026.