Windchill Revision Issue

Question

I want to see if anybody has an aswer for my below issue:

I believe a setting in Windchill was overwritten on our last software upgrade allowing this to happen because this was never an issue in the past. To add to this, our admin person handling Windchill issues is no longer at the company. So I am trying to stumble through this.

Here is the issue:

Two users have the same file in their workspace. The file revision is A.1 User #1 bumps the rev to REV 1.1, makes changes and checks in the file into the Windchill Cabinets. User #2 (who still has the rev A.1 in workspace) now shows an out of date symbol in thier workspace for this file. User #2 makes modification to the A.1 and checks in the file as A.2 into the Windchill Cabinets. The system allowed this and didn't prevent the check in for an out of date file. The system is allowing separate sequential check in of Alpha revision and Numeric revisions- even though the icon in workspace showed out of date.

Reviewing the Revision/Iteration history shows: (earliest on top) Shows in chronological order

A.1

1.1

A.2

If a third person (User #3) opened the file - pulling what the system says is the latest Revision/Iteration - it pulls the 1.1

This issue only happens when two or more people have the same revision/iteration in workspace and one person bumps the file across the numeric/alpha threshold. It doesn't happen say from A to B or from 2 to 3. Only if going for example from D to 1 or 0.5 to A.

And you guessed it - we know this is happening because we had to untangle a big mess - and since duplicated it as a test.

Any ideas?

Thank you,

Clint

GregoryPERASSO · Answer

Hello Clint,I'm not familiar with Revision schema where we can switch from Numeric to Alphabetical or vice versa.But with the OOTB Alphabetical schema, windchill allow to modify a part from A.1 to A.2 by a user1,even if a user2 have already revised in B.1 and is checked out and working on ... each revision is a "standalone" workable instance. It permit , notably if you work with Config management (dated, lot, serial number effectivities ...) to work in "parallel", on future enhancements of your product and control the release to production by effectivitiesthe "absolut latest" is the B.1. But the "good" revision for a specific need depends of a ConfigSpec (filter criteria) (for example lot 1, or serial number 1-1000)In Workspace, you've got 2 columns indicator : one is the "aboslut latest", the other is depending of the config spec you use ...if you don't want this behaviour, you have to set some transitions and accesrules for example, to deny Revise for a non Released (ie lifecycle state) part, and deny checkout of a Released part.regardsGregory

Sign up

Please use your PTC eSupport account.

Welcome to the PTC Community

Please use your PTC eSupport account.