Known Issues
This section outlines the currently identified issues and limitations that may affect the functionality or performance of the system, along with any available workarounds or planned resolutions.
Certain Lightweight Representations (PVZ Files) are Not Indexed Due to Specific Conditions
The following lightweight representations are not indexed due to specific conditions related to the CAD geometry or their associations with WTParts:
• Empty or skeleton parts—If the lightweight representation has no CAD geometry (empty part/skeleton part), then it is not indexed.
• Missing PVS Links—Lightweight representations with missing PVS links are not indexed.
Compare Parts In Group and Compare Two Parts Pages Show a Maximum of 100 Change Notices
On the Compare Parts in Group and Compare 2 Parts pages, the Add to Existing Change Notice action displays a maximum of 100 change notices. You may not see all available change notices if the total exceeds this limit.
Checked-Out Part Temporarily Disappears from the Search Parts Results During a Check-In
A checked-out part will not appear in the search results. If a part is checked out after the search results are generated, it will be excluded from the compare parts report.
This issue affects only the user who performs the check-out or check-in. Other users can still view the part on any page during this time.
Localization Impact
• Some strings, such as the Duplicate Part Search launch point, may not be localized. This is a known issue and will be addressed in a future update.
• The AI Parts Rationalization Plugin UI supports only browser-side localization settings; Windchill-side settings are not supported.
Advanced Search—User Criteria with Apostrophes
When a display name contains a single quote or apostrophe, such as in the name D’Costa, it prevents successful user searches in the Advanced Search criteria and affects the Duplicate Part Search UI. To avoid these issues, do not use apostrophes in display names.
NullPointerException in Windchill Shell on Replica Server
On the Replica Server, the Windchill shell throws a NullPointerException upon startup.
Replica server starts successfully, exception has no functional impact.
Viewable Mismatch When Viewable Is Republished After Windchill Backup
When the part PartBothViewableMismatch_51-A.4 is the latest version and iteration, and its viewable is republished after the Windchill backup time (time_1). As a result a data mismatch occurs between the restored Windchill database and the AI Part Search Index. Following is the observed behavior:
• Windchill DB (after restore of the time_1 backup): Displays the part at iteration A.4 with the old viewable.
• AI Part Search Index DB: Contains the part at iteration A.4 with the newly republished viewable.
• Plugin UI: If the part is available in any group of duplicate parts, it is based on the new viewable available in AI Part Search Index DB.
A temporary inconsistency occurs between the restored Windchill database, the AI Part Search Index database, and the plugin UI. As a result, the viewable displayed in the plugin UI may not match the viewable stored in Windchill after the restore.
The inconsistency is corrected when the part is iterated or revised with a viewable in Windchill, when viewables are republished, or when a reindexing operation is performed.
Duplicate Part Display When a Newly Created Part Inherits Master ID and Object ID After Windchill Restore
After restoring Windchill to a backup point (time_1), a new part, for example PartWC24_New (A.1) may be created. This new part may then be assigned the same master ID and object ID as an existing part originally created and indexed after the backup, such as PartAIIndex11_New (A.1). This ID reuse leads to inconsistencies between the Windchill DB, the AI Part Search Index DB, and the plugin UI.
The observed behavior is as follows:
• Windchill DB (after restore of the time_1 backup): The new part (PartWC24_New) is created after the restore but is assigned the same master ID and object ID as PartAIIndex11_New (A.1).
• AI Part Search Index DB: PartAIIndex11_New A.1 exists in the index and it has same master id and object id of PartWC24_New A.1.
• Plugin UI: If PartAIIndex11_New (A.1) was part of any cluster/group computed before the restore, then PartWC24_New will appear in the same cluster/group in the UI because it shares the same identifiers But the similarity was derived based on the viewable of part PartAIIndex11_New (A.1).
This causes a temporary mismatch where PartWC24_New appears in clusters belonging to PartAIIndex11_New.
This is considered a rare use case. The issue will be resolved when:
• The part undergoes runtime indexing (it will be reindexed automatically), that is the part is iterated or revised with a viewable in Windchill.
• Viewables are republished
• A reindexing operation is performed
 |
Once a new AI Search is performed, the system will display correct and updated clusters based on the latest indexed data.
|
Change Objects Are Created on the Latest Part Version
Change objects (such as Change Notices, Problem reports, Change Requests) are always created on the latest version of a part, even if they are initiated on an older version.
If you create a change notice on an indexed part version A.3, and the part is iterated to a later version (such as A.5) before the change notice is processed, the change notice is created on A.5 instead of the original version A.3 on which it was initiated.