no way to undo a "New Revision" to a whole assembly

[kjohns101]

If a user revises a whole assembly and the ECO is then cancelled, there is no way to back out of it without an existingbulk delete function. In intralink all the objects atany statecould located and be deleted in part or in whole. This becomes a real mess if the assy contains instances of family tables, also whilean administrator is attempting to delete these objects, userscan beadding them to their workspaces because they are the latest by default. This requires these objects to be removed from their workspaces andnow arecorruped.

[avillanueva]

Yes, the items need to be removed from the ECO before they can be
deleted. This removes the record of there being a new revision on that
EC but you are deleting it anyways so I guess its what you have to do.
I would leave a text note there. FT's do complicate things. As far as
the workspaces, there is an option to remove items from workspaces (in
the conflicts when it fails). The workspace should just download the
latest when the delete is done. So long as the modifications to those
deleted items were not significant, it should be ok with the previous
revision.

[SteveVinyard]

Yeah deleting is a pain but the system is FAR better at handling this via lifecycle adjustment instead of a deletion. It doesn't always fit the business needs etc but maybe just do an administrative set-state on the objects to "OBSOLETE" state and make sure users don't have view access to anything obsolete. It doesn't always fit but is worth a try.

Steve Vinyard
Application Engineer

[cid:image001.gif@01CB2341.F39CD860]

[kjohns101]

The goal is to remove this "latest" iteration, set state will just leave
the objects in the system as latest and unauthorized, the last Released
state must be remain to be the latest or it knocks all users out of date -
yes?

Kevin Johnson
PDMLink- Pro/e Administrator
Instrumentation Laboratory
Bedford, Ma 01730-2443
781-861-4561 Office
781-266-7168 Cell

[ira.winston]

Kevin & All, This article (and video) discuss one solution to the "Revise First" issue you have noted regarding PDMLink. Some users want to "Revise Later" when they are sure the ECO will go through or when they have explored multiple design variations.

[SteveVinyard]

You can use the lifecycle to basically “remove” the objects in question (assembly and drawings) from the users environment. Set State on them to an “Obsolete” state that users do not have read access to and viola…when they perform a search for the latest version of that object they will only get the latest version that they can see…hence they won’t see the obsolete object.

That’s just one method and surely not a magic bullet but it’s worth a try and wouldn’t require you to wrestle with all of the other factors that come into play when trying to delete something.

You will also have to set “Allow revise of non-latest revisions=yes” in the preference manager as well.


Another option would be to set “Allow revise of non-latest revisions=yes”….then revise the previous “good” revision over the top of the existing bad one. After that, go and do a set state on the garbage revision to obsolete. I’m just throwing out some ideas that might or might not work for your situation.




Steve Vinyard
Application Engineer

[cid:image001.gif@01CB2358.13FDB780]

[bfrandsen]

Kevin,
Choose Actions-> Delete on the top level assembly. Use the collector to
populate the delete actions table view and use the delete all iterations
option. Use the proposed overwrite option from the Event Manager if
objects are also added to workspaces.
If objects are not added to baselines, ECOs, PR, checked out, etc., this
will do the job. Otherwise you have more work to do.

It is not as straight forward as in Intralink, I agree on that. But
Windchill's database is also much more integral than Intralink ever was
and this stuff keeps you from corrupting your data.

/Bjarne



kevin johnson <kjohnson@ilrd.com>
14-07-2010 16:59
Please respond to
kevin johnson <kjohnson@ilrd.com>


To
Steve Vinyard <->
cc
"Villanueva, Antonio" <->,
"-" <->
Subject
[solutions] - RE: no way to undo a "New Revision" to a whole assembly






The goal is to remove this "latest" iteration, set state will just leave
the objects in the system as latest and unauthorized, the last Released
state must be remain to be the latest or it knocks all users out of date -
yes?

Kevin Johnson
PDMLink- Pro/e Administrator
Instrumentation Laboratory
Bedford, Ma 01730-2443
781-861-4561 Office
781-266-7168 Cell