We use two rules for bumping revisions. One bumps the secondary revision
character when changing the life cycle state from Released to WIP (e.g. the
revision goes from C to C.1) and the other bumps the primary revision
character when changing the life cycle state from WIP to Released (e.g. the
revision goes from C.1 to D).
We are now considering enabling the "Enforce File Locking per Lifecycle
State" feature of Productstream 4.5. But this will lock a revised model file
just as the revision is being updated in the item associated with it. So we
will not be able to check out the model to copy the new revision from the
item to the model. Consequently, the released revision will not be reflected
in the drawing.
Has anyone working this way figured out a work around? Or, ideally, has this
workflow been improved in Productstream 5?
Sincerely,
Michael