Add to Workspace collector enhancement

[gdesantis]

Description of problem:

When objects are added to workspace via the collector all selected objects are filtered together.  For our business we need library parts to always be added as latest, not As-Stored or Released.  This causes massive add to workspace conflicts forcing any number of lengthy work arounds for the user. Who simply wanted some assemblies added to a workspace. Instead the designer is bombarded with conflict after conflict, many times the only solution is to remove offending objects and their children one by one (which is an unacceptable method to resolve)

Proposed solution:

Add the ability in the "filters" to set ATW criteria by multiple contexts. This would allow a user to add to workspace all design objects with one set of rules (perhaps "As Stored") and a second set of library parts with another set of rules (Latest).  This will eliminate most conflicts allowing a user to quickly ATW.

[dhermosillo]

Gary, don't forget to vote up your own idea.

[ChristopherLewi]

This kind of 'different rules for different peices' is affecting us but in a different way. It would save some time if we could have 'latest' for 'our' stuff (because we're working on it) and 'latest-completed' for components from our extended team. I don't know yet how we would define 'our' but it would have to be below the container level for it to make full sense in our business.

[gdesantis]

Christopher, is the latest-completed objects State RELEASED? if so you can use the standard ATW collector filters

[gdesantis]

Any other admins interested in this?

Please vote.

[SteveShaw]

Gary,

In your use case you have zeroed in on an issue of library components being out-of-date when as-stored is later retrieved by your users.  Of course, I can see this happening on occasion but by your description this seems to be a frequent situation.  How often does your business modify and update its library components to cause this problem?  What types of changes are being made?  I would have assumed that library components remain fairly static (not iterated or revised very often), meaning that the same version that you assembled into your design and checked-in (now part of the as-stored configuration) would likely be the latest or released version in your system and thus retrieved using the as-stored configuration later on.

Obviously, today its not possible to apply different rules to different types or based on different locations, hence your post.  The first rule is applied to all dependents if it can't be resolved it falls back to the next rule, and so on.

[gdesantis]

Against my objections, we update and add to our standard library parts extremely often.  I was hoping a collector enhancement would do the trick.  The work around I give my users is to simply open the Drawing or Assembly directly from the search result(s), allowing Windchill to deal with conflicts automatically.  This seems to be working.

[SteveShaw]

Can i assume that these standard parts are family tables?

[gdesantis]

yes sir, Family Tables.  We actually have 2 libraries, the one for fasteners etc, Nuts and bolts etc, and one for our company standard parts. Our company standard are not all FT.

G

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.