Where Used Collector for Mass Change should only collect latest Revision

[jfocke]

Where Used vs. Object Collector

• The Where Used table considers the configuration specification defined in the filter criteria. That means, if latest is defined as criteria, only parent assemblies in LATEST will be displayed
• The affected object collector in Change Tasks does consider the configuration specification criteria concerning the collected objects. This leads to collecting also non latest objects
• In use cases e.g. mass changes (replacements) a potential high amount of wrong (non latest) data would be collected. In order to being able to perform the mass change, users would need to revise the collected objects (if the parts are already released). This results in error messages and the user has to identify and finally to remove the non latest parts from the affected objects table

As the current system behavior has been classified as Enhancement, I am requesting it as a Product Idea. I am aware of workarounds like using the Where Used Table, selecting, copying and finally pasting them all into the change task, nevertheless the object collector is such a helpful and supporting tool so that an improvement regarding the described behavior make it even more efficient.

[BjoernRueegg]

Thanks for the idea! I've struggled on this problem too. Especially user are revising the wrong assemblies too often.

It also could help to see an icon, if the part is the latest revision and iteration. I've developed a such a datautility, but it needs some performance and can only be added to customizable tables. If the tables would be configurable to add some other columns, this could also be a solution.

[jfocke]

Hi , thanks for your Feedback. There are several places where the System behaviour  is like described in the product idea. Your example is showing results from the Advance search? If so, in our  project the same Question came up some days ago. In the advanced search you could verify if the behavior of the Advanced Search along with a specific Report Template within the “Related Object Search” fits your needs. This gives you the possibility to add something like a subquery to your search criteria which is filtering  “Latest Revision Only”.  But here again, this has an Impact on the Performance same like your  datautility

[BjoernRueegg]

@jfocke This is just a screenshot. I actually developed the utility for the data package to show if the package contains the latest revision and iteration. And as tooltip I show the state and display identifier of the newest iteration of the latest revision. But since it is registered for the versioned object, it also it's available in other tables.

[GregoryPERASSO]

+1

Same behavior when collecting ProcessPlans or Operations in MPMLink.

It should be fixed for all types of Structured/Versionned Windchill Business Objects ...

Where used should use Filter Criteria  to be able to collect real LATEST or any other type of filter like effectivities etc ...

regards