Precise entry: Scenario

If an assembly is precise and the revision rule contains a precise entry, the assembly is configured according to that entry. However, if the assembly is precise and the revision rule does not contain a precise entry, the assembly is treated as imprecise. For example: You have an item called Part1 with two revisions, Part1/A is Working and Part1/B is also Working. A precise assembly Asm is created containing Part1/B. That is: Copy Asm |--Part1/B If User2 is denied read access to Part1/B and opens Asm in Structure Manager with an AnyStatus;Working revision rule, the system performs the following evaluation: The AnyStatus entry does not configure any revisions. The Working entry configures in Part1/B but access rules make this revision . Regardless of the setting of the PSE_check_read_access_for_Rev_Rule_entry preference, evaluation continues. The next revision is Part1/A, and access rules do not deny access to it, so the final result is Part1/A. If User2 then changes the revision rule to Latest by Alpha Revision Order, the system performs the following evaluation: The Latest by Alpha Revision entry configures in Part1/B but access rules make this revision . The system continues evaluation only if the PSE_check_read_access_for_Rev_Rule_entry preference is TRUE. The next revision is Part1/A, and access rules do not deny access to it, so the final result is Part1/A. You have an item called Part1 with three revisions, Part1/A is released with a TcReleased status, Part1/B is released with a TcBaseline status, and Part1/C is released with a TcReleased status. A precise assembly Asm is created with Part1/C. That is: Copy Asm |--Part1/C If User2 is denied read access for the TcReleased status and opens Asm in Structure Manager with a AnyStatus;Working revision rule, the system performs the following evaluation: The AnyStatus entry configures in Part1/C but access rules make this revision . The system continues evaluation only if the PSE_check_read_access_for_Rev_Rule_entry preference is TRUE. The next revision with status is Part1/B, and access rules do not deny access, so the final result is Part1/B. You have an item called Part1 with two revisions, Part1/A is released with a TcReleased status and Part1/B is working. A precise assembly Asm is created with Part1/A. That is: Copy Asm |--Part1/A If User2 is denied read access for status TcReleased and opens Asm in Structure Manager with a AnyStatus;Working revision rule, the system performs the following evaluation: The AnyStatus entry configures in Part1/A but access rules make this revision . The system continues evaluation only if the PSE_check_read_access_for_Rev_Rule_entry preference is TRUE. Because no other revisions have status, the next rule entry of Working configures in Part1/B. Access rules do not deny access, so the final result is Part1/B. If User2 changes the revision rule to Latest Working, the system performs the following evaluation: The LatestWorking rule contains a Precise entry, that configures the revision saved with the assembly, namely, Part1/A. Because access rules make Part1/A unreadable for User2, the final result is . The PSE_check_read_access_for_Rev_Rule_entry preference does not affect the result because the structure and the revision rule are precise.