Message
Route part occurrence with wrong permission group or approval status.
Severity
High.
Detailed Description
All the route part occurrences in the database should belong to the same Permission Group or Approval Status of the associated features. The software attempts to synchronize them such that these objects are in the same Permission Group or Approval Status. When they are not in same Permission Group or Approval Status, it can break the software and un-necessary connections get created, causing confusion.
Possible Cause
In a particular workflow, the software was not handling this situation correctly, hence introducing this problem. This problem has been identified and fixed in the Version 4.1 SP3 version.
Possible Impacts
You might not be able to delete the features/runs.
Two part occurrences that are adjacent to each other might not have connections between them. Hence they may not have proper connection items (such as welds, and so on) in some cases.
What You Should Do
The software has been modified to automatically detect this situation and to recover from it. The next time the object is subject to modification, the problem is fixed correctly, provided the person who modifies the object has permission to all necessary objects (parts and features). An example is when you change one or more temperatures to cause a re-computation in the software. This re-computation fixes the problem automatically.
If, in the above example, the problem does not resolve itself, you must manually fix the objects by modifying the Permission Group or Approval Status of the objects.