Search behavior....
Feb 20, 2013
10:10 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Feb 20, 2013
10:10 AM
Search behavior....
In 9.1 and 10.0 (pre m040 apparently), you could have a preset search (say, to set latest revision, latest iteration and filename blank), click the search, enter the necessary data (in this case filename), then execute the search. Now, the search is automatically executed as soon as you click the search link (which searches for, in this case, every object). Not earth shattering as the search can be stopped (or edited...), but that seems like a bad decision. User searches always executed immediately (that kind of made sense). It seems like we'd want preset searches that can be filled out without having to, in essence, begin and then halt a search to edit the criteria. Or, as suggested in one of the calls, click the little edit icon. Which is not horrific, but definitely more concentration.
So, just out of curiosity, am I alone on this (thinking that we should be able to create a published search with "settable" criteria prior to actually searching)? It also seems odd this would be a core/central change that was made across builds (though it does impact the next release, 10.1.....and beyond).
<insert snarky=" comment=" about=" ptc=" here.......i=" won't=" as=" i'm=" not=" responsible=" for=" a=" gargantuan=" jee=" system=">
Brian
See:
So, just out of curiosity, am I alone on this (thinking that we should be able to create a published search with "settable" criteria prior to actually searching)? It also seems odd this would be a core/central change that was made across builds (though it does impact the next release, 10.1.....and beyond).
<insert snarky=" comment=" about=" ptc=" here.......i=" won't=" as=" i'm=" not=" responsible=" for=" a=" gargantuan=" jee=" system=">
Brian
See:
Labels:
- Labels:
-
Other
4 REPLIES 4
Feb 20, 2013
10:46 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Feb 20, 2013
10:46 AM
On 02/20/13 08:10, Brian Krieger wrote:
>
> In 9.1 and 10.0 (pre m040 apparently), you could have a preset search (say, to set latest
> revision, latest iteration and filename blank), click the search, enter the necessary data (in
> this case filename), then execute the search. Now, the search is automatically executed as soon
> as you click the search link (which searches for, in this case, every object). Not earth
> shattering as the search can be stopped (or edited...), but that seems like a bad decision. User
> searches always executed immediately (that kind of made sense). It seems like we'd want preset
> searches that can be filled out without having to, in essence, begin and then halt a search to
> edit the criteria. Or, as suggested in one of the calls, click the little edit icon. Which is
> not horrific, but definitely more concentration.
>
> So, just out of curiosity, am I alone on this (thinking that we should be able to create a
> published search with "settable" criteria prior to actually searching)?
>
9.1 M070 here. We have several of these saved searches in which the searcher enters data such as a
parameter value and then selects the "Search" button in order to actually perform the search. This
is the behavior I expect. The 10.0 M040+ behavior you are describing does not fit my expected search
behavior.
> It also seems odd this would be a core/central change that was made across builds (though it does
> impact the next release, 10.1.....and beyond).
>
> <insert snarky=" comment=" about=" ptc=" here.......i=" won't=" as=" i'm=" not=" responsible=" for=" a=" gargantuan=" jee=" <br="/>> system>
>
> Brian
>
> See:
>
> In 9.1 and 10.0 (pre m040 apparently), you could have a preset search (say, to set latest
> revision, latest iteration and filename blank), click the search, enter the necessary data (in
> this case filename), then execute the search. Now, the search is automatically executed as soon
> as you click the search link (which searches for, in this case, every object). Not earth
> shattering as the search can be stopped (or edited...), but that seems like a bad decision. User
> searches always executed immediately (that kind of made sense). It seems like we'd want preset
> searches that can be filled out without having to, in essence, begin and then halt a search to
> edit the criteria. Or, as suggested in one of the calls, click the little edit icon. Which is
> not horrific, but definitely more concentration.
>
> So, just out of curiosity, am I alone on this (thinking that we should be able to create a
> published search with "settable" criteria prior to actually searching)?
>
9.1 M070 here. We have several of these saved searches in which the searcher enters data such as a
parameter value and then selects the "Search" button in order to actually perform the search. This
is the behavior I expect. The 10.0 M040+ behavior you are describing does not fit my expected search
behavior.
> It also seems odd this would be a core/central change that was made across builds (though it does
> impact the next release, 10.1.....and beyond).
>
> <insert snarky=" comment=" about=" ptc=" here.......i=" won't=" as=" i'm=" not=" responsible=" for=" a=" gargantuan=" jee=" <br="/>> system>
>
> Brian
>
> See:
Feb 20, 2013
10:56 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Feb 20, 2013
10:56 AM
I found this annoying as well when we moved to WC 10.1. What we found was when saving the search, go into the "Advanced Options" and then in the "Set Required Attributes" set Number (or whatever the attribute may be) as a required attribute then it will behave the same as before when selecting the search name to perform a search.
Steve
Steve
Feb 20, 2013
11:15 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Feb 20, 2013
11:15 AM
Awesome, thanks, Steve. I hadn't ever seen the required criteria. Works like a champ. I wonder why PTC didn't mention that little setting. Very helpful.
I appreciate it!
Brian
I appreciate it!
Brian
Feb 24, 2013
02:46 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Feb 24, 2013
02:46 PM
What about this scenario?
I want to create one search that includes several different possible Criteria. However, the user could use any one, a few or all of them. I also don't want it to start the search automatically. I want the user to pick on the saved search, enter the info in only the criteria they want THEN perform the search. The problem is if I set one of the attributes as Required then the user can't use that saved search if that required criteria is not what they are looking for.
Has anyone set up a "template" search for many possible Criteria where it doesn't start the search automatically? I don't think it's possible but can't hurt to ask.
Steve G
I want to create one search that includes several different possible Criteria. However, the user could use any one, a few or all of them. I also don't want it to start the search automatically. I want the user to pick on the saved search, enter the info in only the criteria they want THEN perform the search. The problem is if I set one of the attributes as Required then the user can't use that saved search if that required criteria is not what they are looking for.
Has anyone set up a "template" search for many possible Criteria where it doesn't start the search automatically? I don't think it's possible but can't hurt to ask.
Steve G
