cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Enable Windchill search to support ‘pure’ latest iteration search when additional criteria is applied.

Enable Windchill search to support ‘pure’ latest iteration search when additional criteria is applied.

Current behavior: with latest iteration search is performed with State ‘In Work’ then all ‘In work’ objects are searched and later latest iteration filter is applied on it. If you search multiple objects, you will receive duplicated results (which would add up to a wrong search result).The system should be able to show only the real latest object (the “current”) and not the latest from all states.

So a "pure latest" search criteria have to be add to the search function in Windchill.

12 Comments
Tanzanite

This has drove us nuts.  I whole-heartedly agree.  It is different in PDMLink from Intralink 3.4 and lower.  If I put a criteria of latest objects at In Work then if the object is at 2.2 at Production Released but 2.1 is In Work then I don't want that object to display at all!

Newbie

Totally agree.  Multiple users have misunderstood search results, and costly mistakes were made. The actual functionality is different than users expect.  Practically all users depend on Advanced Search, and it is nearly impossible to explain this crazy functional issue to everyone.

Emerald I

It sounds like what you really want is a priority to the search criteria and then the ability to change that priority.

16.png

First filter for all lastest revisions, then filter for all latest iterations, finally filter for all 'Released' objects.

I think this might already have been fixed.

I have the following objects:

search example1.PNG

Part 1:

Versions A.1, A.2, A.3 = In Work

Version A.4 = Released

Part 2:

Versions A.1, A.2, A.3, A.4 = In Work

Version B.1 = Released

I searched for parts that are in the latest iteration and in the In Work state, and got the following results:

search example2.PNG

Note that Part 1 version A.3 was NOT included in the results, which is what the original post seems to be addressing.

Whether or not Part 2 appears is set using the "Latest Version Search" preference -- but that is dealing with revisions, not iterations.

(And technically, specifying latest iteration is unnecessary. By default, all searches are performed against the latest iteration. The Iteration criteria is only necessary if you're searching for a non-latest iteration.)

Emerald I

This is actually very concerning if it's no longer possible to locate an object where both Criteria are true.  What if you really meant: 1.) find all "in work" objects then 2.) filter this set by the latest one of each?  We do this today for "latest" + "released".  Just because something has been revised to "in work" doesn't mean I should stop seeing the "latest released" version.  Either we need a "pure" latest search (as the idea suggested), or we need to set the priority of the search order (search for "A" first, then filter this by "B", and so on).  If the latest release of Windchill really does change this functionality, then we are in serious trouble.  Latest released data needs to continue to remain available from search, even if there is newer unreleased data in the system.

So, for example:

"MyPart1"

A.1 = In Work

A.2 = In Work

A.3 = Released

A.4 = Released

A.5 = In Work

And you would want to search for the latest version of "MyPart1" that's in the "Released" state -- in other words, you want a search that would return MyPart1 version A.4. Is that correct?

One way to do it would be to search for Iteration=All and State=Released, but that search will return version A.3 and A.4. But I can ask the search team if they can think of a way that this might be handled.

Emerald I

Yes, this is how it works today (10.2 M020).  I want to make sure I don't lose that functionality.

rel1.PNG

rel2.PNG

Emerald I

What version are you testing on?  10.3?

Emerald I

By the way, I think this drives much more than just search.  If we have users who are only allowed to see objects that are released, they should still be able to find and display the latest version of those released objects in search, Creo View, structure browser, etc.

I was testing on 10.2 M030.

But you're ok -- this didn't go away. I think the difference is latest revision vs. latest iteration. Searching for a non-latest iteration is more complicated.

For example, I created "Part 6" with the following version history:

A.1 = In work

A.2 = In Work

A.3 = In Work

A.4 = Released

     (Revise)

B.1 = In Work

B.2 = In Work

     (Revise)

C.1 = In Work

C.2 = Released

     (Revise)

D.1 = In Work

D.2 = In Work

D.3 = In Work

A search for "Part 6" returns the following:

A.4

B.2

C.2 

D.3

Search for Part 6, Revision=Latest returns the following:

D.3 (In Work)

Search for Part 6, Revision=Latest, State=Released:

C.2 (Released)

-- Which is how you seem to be using it, and it continues to work as expected.

The potential problem would be in a use case where for some reason you iterated C.2 to C.3 and then put C.3 in the "In Work" state:

C.1 = In Work

C.2 = Released

C.3 = In Work

In which case, a search for Part 6, Revision=Latest, State=Released would return:

A.4 = Released

Which is likely exactly what you want!  But strictly speaking, the most recent revision of Part 6 to be in the Released state is version C.2. But since C.2 is now a non-latest iteration, it's ignored by Windchill search.

Community Manager
Status changed to: New Idea
 
Community Manager
Status changed to: Acknowledged