Why is "Latest Working" revision rule not loading the latest revision of a component?
Solution
Make sure it is not due to this situation:
This component had revision 01, 02 and 04 being released, and an unreleased 03 revision; when using the out of the box revision rule "Latest Working", it functions as such:
Teamcenter runs thru these options when deciding which revision of a component to open:
Precise
Working()
Has Status(Any Release Status, Configured Using Released Date)
Teamcenter examines the component, and sees it has multiple revisions, so it checks if the assembly is set to Precise. If not, it checks if any of the revisions are "working", meaning they have no status (not released).
If it sees a "working" revision, it will load that revision, or the newest if more than one working revision exists. If all revisions are released, it will then load that particular released revision, based on the released date/time.
As seen from the above example, Teamcenter/NX was loading the "working" revision, even though there was a higher revision that was released. Now, even if the user were to release the older 03 revision, it would continue to be loaded, since it would have the most recent released date/time.
Notes and References
Hardware/Software Configuration
Platform: INTL64
OS: window
OS Version: 1064
Product: NX
Application: NXMANAGER
Version: V11.0.2
Function: FILE_OPEN
Ref: 001-9287345