Search for Latest AND Released without Advanced Search?

[pcnelson]

Our users dont like the extra stepsto get to the Saved Searchto search for the Latest + Released objects. We routinely change designs while the previous design is still in production, so Manufacturing still needs to see the last Released object but when an object is Revised it drops out of the Simple Search "Latest" criteria. That then requires going to a Saved Search that looks for bothLatest and Released. Is there someway to streamline the search, such as make the Saved Search the standard Simple Search? Any way to make a shortcut maybe? Or add the specific Saved Search to the drop down menu for Seach? Thanks for an input.

[DonSenchuk]

Create a group for Released only objects. Add users to this group that only want to see Released objects.

Use Policy Manager to create a policy that restricts that group so that it only sees Released objects. Any object that is not in a state of Released will then be omitted from the search results, even when using a basic search. No saved searches necessary.

(Unless they sometimes want to see Latest Released, but other times they want to see objects in a revised state, then it's just users being difficult.)

In Reply to pete nelson:

Our users dont like the extra stepsto get to the Saved Searchto search for the Latest + Released objects. We routinely change designs while the previous design is still in production, so Manufacturing still needs to see the last Released object but when an object is Revised it drops out of the Simple Search "Latest" criteria. That then requires going to a Saved Search that looks for bothLatest and Released. Is there someway to streamline the search, such as make the Saved Search the standard Simple Search? Any way to make a shortcut maybe? Or add the specific Saved Search to the drop down menu for Seach? Thanks for an input.

[RandyJones]

On 02/07/13 13:29, pete nelson wrote:
>
> Our users dont like the extra steps to get to the Saved Search to search for the Latest + Released objects.  We routinely change designs while the previous design is still in production, so Manufacturing still needs to see the last Released object but when an object is Revised it drops out of the
> Simple Search "Latest" criteria.  That then requires going to a Saved Search that looks for both Latest and Released.  Is there someway to streamline the search, such as make the Saved Search the standard Simple Search?  Any way to make a shortcut maybe? Or add the specific Saved Search to the
> drop down menu for Seach?
>
To add a saved search to the drop down menu (Windchill 9.1 M070) steps:

1. as wcadmin create the search and save it
2. as user select the "Search:" link to take you to the search page
3. select "Customize..." from the "Saved Searches" menu
4. select the saved search(es) you want to show and set them to Show

This has to be done for each user. I am not aware of a Site level way of of doing this.

>   Thanks for an input.
>
>
> ----------


--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
   Fax: 785-667-2695
------------------------------------------------------------------------

[sdrzewiczewski]

On the customize saved search table, if you right click on the saved search name, you can bookmark that link and it's a direct link to that search. This is extremely useful for users. (Doesn't work after 9.1)

Steve D.

[pcnelson]

In Reply to Stephen Drzewiczewski:

On the customize saved search table, if you right click on the saved search name, you can bookmark that link and it's a direct link to that search. This is extremely useful for users. (Doesn't work after 9.1)

Steve D.

Thanks Stephen, that would be a great solution! I should have mentioned that we are 10.0, rats... So PTC took away great functionality when it "upgraded".

[pcnelson]

In Reply to Don Senchuk:

Create a group for Released only objects. Add users to this group that only want to see Released objects.

Use Policy Manager to create a policy that restricts that group so that it only sees Released objects. Any object that is not in a state of Released will then be omitted from the search results, even when using a basic search. No saved searches necessary.

(Unless they sometimes want to see Latest Released, but other times they want to see objects in a revised state, then it's just users being difficult.)

Don, If I understand your suggestion correctly that is what we currently have, with the addition of "Latest" set in preferences. I think the trouble is that inthe heirarcythe search looks first to the "Latest" filter rather than at the Policy Manager first and then apply the preference setting. If the user is in a Released only group and the latest revision happens to be Development the search stops there and doesnt show them the Released object that is just before the Latest. If A.1 is Development and A.0 is Released they dont getto see that A.0 exists. Does that explanation make sense? Thanks for your help.

[DonSenchuk]

If that's what you're seeing there is something wrong with the policy
setup. The "hierarchy" doesn't apply them in that order. It simply makes
sure to show the latest object that is Released. That's the way the
Policy settings have always worked.



If the group that only wants to see Latest Released has the correct
policy applied, they will see nothing but the Latest Released objects
when doing a basic search. Remember that you have to set up policies for
the other, non-Released states that deny that group the ability to Read.
(I typically just deny everything on each non-Released state.) If you
just set up a single policy to read Released objects, by default you are
not denying the ability to read non-Released.

[DonSenchuk]

In that case, I can only confirm it works properly in 10.1 M020.

[tmcnaney]

This was corrected in Windchill 10.0 M030 and 10.1 F000.

https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS31715

There was another related issue corrected in 10.0 M040 and 10.1 M020 if you are using Index search (SOLR):

https://www.ptc.com/appserver/cs/view/solution.jsp?n=CS68845