Auto suggest behavior for af:query component LOV fields.

Hi,
I am new to ADF development and need help on implementing auto suggest behavior to the LOV fields generated by af:query component. For inputList and inputCombo.. fields we can add af:autosuggestbehavior tag to enable this. How do we enable the same for af:query generated LOV fields.
Regards,
C.R

Thanks Timo for such a quick response.
JDev version we are using is 11.1.1.6.0
Unfortunately, we have gone too far with the AF:Query and Everything else is working apart from Auto-Suggest on AF:Query. Now will take a lot of time to implement and test. Also, users will have to spend considerable time to test it again.
Thanks and Regards,
Satya

Similar Messages

Problem using Auto Suggest Behavior

Hi all,
I am using Jdeveloper 11.1.1.2 and ADFBC.
I want to implement auto suggest behavior and I am following the steps on: http://www.oracle.com/technology/products/jdev/howtos/autosuggest/explaining_autosuggestbehavior.htm
When I am writing a partial string on the component I don't show auto suggestion and if I click on the button on the right of the component (the lens for finding records) I see a panel search with all the fields of my VO.
It is a normal behavior I have a warning in the auto suggest component when I write #{bindings.myField.suggestedItems}?? I don't find it under bindings using the expression builder.
Where am I wrong?Any suggestions?
Thank you
Andrea

Sorry,
after the tag validator I have:
<af:autoSuggestBehavior suggestedItems="#{bindings.myAttribute.suggestedItems}"/>
When I am writing something on the inputText of myAttribute I have this error:
Target Unreachable, 'DescrizioneTecnica' returned null.
Stack trace:
javax.el.PropertyNotFoundException: Target Unreachable, 'myAttribute' returned null
     at com.sun.el.parser.AstValue.getTarget(AstValue.java:88)
     at com.sun.el.parser.AstValue.invoke(AstValue.java:153)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at oracle.adfinternal.view.faces.el.InternalELObject.autoSuggest(InternalELObject.java:134)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Can I use a OID rule for a Query SQL Lov of BIP?

Hi. Can I use OID data (rules) for a query sql lov in BIP? Ex. filters users/store.
Thank you.
R.

Hi,
I didn't look at the example, but if you want to secure your application then you should use container managed security. Read this .
Anyway, you could add this before return "good"; in your login_action()
FacesContext.getCurrentInstance().getExternalContext().getSessionMap().put("username", user);Then, you can access this from anywhere in the application by using #{sessionScope.username}.
Pedja

Safari 5.1 strange auto-reloading behavior for tabs in the background

hi guys.
I have been encountering this strange behavior recently. I had thought it could be something wrong with my system, until yesterday i upgraded my Safari for Windows to the v.5.1 on a Windows XP laptop, and found the same issue. Now i guess I can be quite certain this is a safari issue.
System info:
1. Macbook Pro 17", OSX 10.6.8, 64bit boot (i have 8GB RAM).
2. Safari (Mac) is the lastest version (as updated by the Auto update), run in the default 64bit mode.
3. The windows machine is an old Thinkpad T60 with Windows XP Pro SP3. The Safari for windows is Safari 5.1 (7534.50), also updated by auto update.
4. I have not installed any Safari extensions/plugs that feature an auto-reloading -- as such behavior was never seen before i upgrade to Safari 5.1
Since i mostly work on mac the mac has been kept most updated. But the windows machine which i use now and then, i don't update everything very frequently. And the earlier Safari 5.0 worked fine without the current issue.
Symptoms
1. Let's say I have 1 Safari window open with 5 tabs, and I have been working on the 4th tab for a while, and left the other 4 tabs "idling" in the background.
2. And then i want to switch to another tab: click on that tab, and that tab will come to the foreground while being automatically refreshed.
3. It looks to me this behavior happens after the inactive tabs have been idling longer than a certain period of time - then if you switch to them, they will be switched to and in the same time auto-reloaded. But I still don't know how long it needs for the "idling" before an auto-reloading "threshold" is triggered.
4. In the beginning this was just on the Mac Safari (and i hadn't updated safari on the windows). But after I updated safari for WIN yesterday, i found the same behavior today.
5. I checked all the Preferences settings and didnt find any option that indicates this behaviors.
Guys. any ideas? anyone have the same trouble? Thanks a lot guys. This is really annoying.

Carolyn Samit wrote:
I'm running Safari 5.1 / SL v10.6.8 on one Mac with Glims installed and I never have a problem with tabs auto reloading. You might want to give it a try.
It's free!
http://www.machangout.com/
Once the software is installed you can access the settings from Safari / Preferences - Glims.
If you don't like the software you can use their uninstaller here.
Hi Carolyn thanks a lot for the idea.
The weird thing is... after i tried to uninstall and re-install a few apps the "auto-loading" behavior disappeared ... guess something was interfereing with safari 5.1...
But thanks for recommending Glims. I took a quick look at the website and it looks great. will do some more research before i start using it. Thanks for the recomm!

Disable collapse for af:query component

Hi All,
Can anybody please tell me how to disable the collapse feature of the af:query component? I basically want it to be expanded every time.
Thanks

Hi,
As your requirement it no need to disabled,and cannot disabled using provided attributes but you can set disclosed attribute to false.
See for more
http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e12419/tagdoc/af_query.html

Af:query component added field not removed when remove icon is clicked

I have an af:query component on a popup dialog. In advanced mode when I add a field, the new field appears in the searchRegion followed by a red X remove icon. If I subsequently click that remove icon, the query refreshes, the red icon is gone, but the newly added field still remains. The query component is linked to a standard VO query executable in the bindings. There is no custom processing of the value, model, queryListener or the queryOperationListener. In all other respects the query component works fine. The only problem is a newly added field not being removed when the remove icon is clicked. Here's how the component is setup (an added wrinkle is that the query component is hosted in a Declarative Component, so that makes this code a little harder to decipher).
Does anyone know where I should start looking for this? Hopefully I don't have to implement my own queryOperationListener.
JDev version is Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923
--- snippet from the page fragment ------
<af:popup id="frmsLstPU" contentDelivery="lazyUncached">
<af:dialog id="d1" type="ok"
styleClass="AFStretchWidth" resize="on"
stretchChildren="first" contentWidth="840"
contentHeight="480"
title="#{UnifiedResourceBundle['FORMSLIST.DIALOG.TITLE']}">
<idmkr_adf:Correspondence_Formslist_Query idmkr_query_model="#{bindings.FormVOFlatQueryCriteriaQuery}"
idmkr_table_binding="#{viewScope.FormsListBacking}"
idmkr_table_model="#{bindings.FormVOFlatQuery1}"
idmkr_bindings="#{bindings}"
idmkr_resourcebundle="#{preferences}"
idmkr_printStreamBean="#{viewScope.FormsList}"
id="cf1">
</idmkr_adf:Correspondence_Formslist_Query>
</af:dialog>
</af:popup>
-- snippet from the Correspondence_Formslist_Query declarative component ------
<af:query id="qryId1"
headerText="#{UnifiedResourceBundle['FORMSLIST.QUERY.SEARCH.TEXT']}"
disclosed="true"
value="#{attrs.idmkr_query_model.queryDescriptor}"
model="#{attrs.idmkr_query_model.queryModel}"
queryListener="#{attrs.idmkr_query_model.processQuery}"
queryOperationListener="#{attrs.idmkr_query_model.processQueryOperation}"
resultComponentId="::resId1" displayMode="default"
styleClass="AFStretchWidth"
rows="4" maxColumns="2"/>

I have changed the contentDelivery from "lazyUncached" to "immediate" and the same problem occurs. Thank your for your suggestion.

Set view criteria on af:query choice LOV field

i have an af:query. one of the fields is a choice. the LOV for the choice come from a VO. i need to set view criteria for the query for the LOV for the choice. that is, the query for the values of the choice requires view criteria.
moreover, that search criteria is only known by the view. because the hooks for the choice are set up entirely in the model, i don't see how it would ever be possible to use values from the view to define the query for the LOV for the choice.
any ideas?

Assuming that you can have a method at the AM level that sets the viewCriteria for your VO, you can drag this method to the page flow to be executed before you go into the query page - this will set the right condition for the list that needs to populate the LOV.
Then the query component can use that VO as an LOV like this:
http://blogs.oracle.com/shay/2009/12/adf_query_with_parameters_and_1.html

Wild Carding with Record Search - Auto Suggest Behavior

I have a property by name searchTerm which is enabled for wild card record search. When I am doing a wild card search passing bbay* to ERecSearch , it is not auto correcting to baby and returning no results, whereas when I send bbay to Endeca, it is automatically auto correcting to baby.
Please let me know why is this different behavior noted. Do we not expect them to auto correct even when we use wild carding. Please throw some light on this and how can this be achieved

As Pradeep said, auto-correction is one of the linguistic features that isn't supported for wildcard searching (along with stemming, thesaurus, snippeting and phrasing). One approach is to do a "cascading search", so execute a search without wildcarding first (and getting spell-correction, did-you-mean, stemming etc.), and if you don't get any matches then re-submit as a wildcarded search. This is also useful as part of a larger part number matching strategy.
Michael

Selectively required not working for af:query component

Hi Experts,
one small issue.
I have a search form and the user is supposed to enter atleast one criteria before clicking on search.
So I opened the View Criteria and marked validation as "Selectively Requried" on all the criteria conditions in the group.
When I open the page, I see ** infront of every field and error is coming properly when I click search without entering any values
Problem is even if I enter few or all the values also, still error comes saying atleast one is required.
Am I missing anything?
or is there any programmatic way of doing the same?

I am new to ADF ... but what i have observed is that in case the View Criteria involves search in various levels also (for e.g. Master-Detail or Master-Detail-Detail) , then at least one attribute from each level is required, if they are marked as Selectively required.
The error message clearly tells you which attribute(s) is required. sometimes it may say Attrib1 is required or any one of Attrib1, Attrbi2, Attrib3 is required. Either I am missing something and doing it all wrong. Or it may make some sense. But still dnt understand the reason.
Would appreciate, if somebody can throw some light on how the double asterisk(** ) behaviour i.e. Selectively Required, when search involves various levels ?

af:query component "Add Fields" clarification

Hi, in the advanced mode of <af:query> using the "Add Fields " function , duplicate fields(same search field can be added multiple times) can be added. Is this a bug or a feature. Where can i refer the doc to confirm this . Thanks.

I don't know that the documentation specifically says anything about this. [url http://download.oracle.com/docs/cd/E14571_01/web.1111/b31973/af_query.htm#BGBCHFEF]here is one piece of documentation.

Auto suggest behaviour copononent is not working

Hi All,
We migrated our application from JDev 11.1.1.3 to 11.1.1.5.
we have a input text with LOV feild in a popup, and the feild has auto suggest behavior,
<af:inputListOfValues id="inputListOfValues3"
popupTitle="Search and Select: #{bindings.Dica.hints.label}"
value="#{bindings.Dica.inputValue}"
label="#{bindings.Dica.hints.label}"
model="#{bindings.Dica.listOfValuesModel}"
required="#{bindings.Dica.hints.mandatory}"
columns="30"
shortDesc="#{bindings.Dica.hints.tooltip}"
autoSubmit="true"
valueChangeListener="#{backingBeanScope.Bean.dIcaChangeListener}"
searchDesc=" ">
<f:validator binding="#{bindings.Dica.validator}"/>
<af:autoSuggestBehavior suggestedItems="#{bindings.Dica.suggestedItems}"/>
</af:inputListOfValues>
it worked well in 11.1.1.3, but after moving it to 11.1.1.5, the auto suggest behaviour stopped working, but found no error in the log. LOV is working good, Value change listener is also working well.
Please advise.
Thanks...

Yes, I did that, but no result. we have similar components in the same page itself with auto suggest behaviour and input LOV, for those auto suggest behaviour is working good. But this particular feild is in a popup, that might be the reason.

Error implementing Auto Suggest Behaviour (JDeveloper Tutorial)

Hi,
I'm using JDev 11g R2 on Mac OSX. In the JDeveloper Tutorial "Developing Rich Web Applications with Oracle ADF", Part 3, Step 3, I don't get the "Insert Auto Suggest Behavior dialog box", so I used the property inspector to enter "#{bindings.JobId.suggestedItems}" in the "SuggestedItems" property.
When I run the application, and type a value in the JobId, I get the error:
suggestedItems="#{bindings.JobId.suggestedItems}": Method not found: 0.suggestedItems(java.lang.String)
I checked the bindings in "query.jsf", and they're all set.
Does anyone have an idea what could be wrong?
Kind regards,
Philip

The tutorial (http://docs.oracle.com/cd/E18941_01/tutorials/jdtut_11r2_55/jdtut_11r2_55_3.html) suggests that you can drag and drop the auto suggest behavior onto the JobId. But you cannot.
By default, the JobId item is not created as an element that can accept an auto suggest behavior. The source for the item should resemble:
            <af:inputComboboxListOfValues id="jobId1Id"
                                          popupTitle="Search and Select: #{bindings.JobId1.hints.label}"
                                          value="#{bindings.JobId1.inputValue}"
                                          label="#{bindings.JobId1.hints.label}"
                                          model="#{bindings.JobId1.listOfValuesModel}"
                                          required="#{bindings.JobId1.hints.mandatory}"
                                          columns="#{bindings.JobId1.hints.displayWidth}"
                                          shortDesc="#{bindings.JobId1.hints.tooltip}">
                <f:validator binding="#{bindings.JobId1.validator}"/>
                <af:autoSuggestBehavior suggestedItems="#{bindings.JobId1.suggestedItems}"/>
            </af:inputComboboxListOfValues>However, when the form itself is dropped onto the page, the JobId is created as a selectOneChoice.
This seems to be an error with the tutorial (http://docs.oracle.com/cd/E18941_01/tutorials/jdtut_11r2_55/jdtut_11r2_55_2.html).
Edited by: Dolphin on Sep 29, 2012 2:37 PM

Need to implement auto suggest with multiple select in a input text field

Hi,
Jdev Ver: 11.1.1.4
My requirement is to create an input field where i can provide auto suggest and user can enter multiple email ids. It is similar to current "To" field while composing a mail in Gmail.
Problem:
I have implemented input box with auto suggest. For the first entry it works fine. when i enter 2nd value(i have used ',' (comma) as separator and handled it in 'suggestItems' bean method to take sub-string after comma for providing the suggestion) , after selection.... the first value get lost. So at a time only one value is selected in the input text.
Input text:
<af:inputText label="Names" id="it21" rows="2"
columns="50" simple="true"
valueChangeListener="#{VisitBackingBean.visitMembersInputBoxCL}"
binding="#{VisitBackingBean.visitMembersInputBox}">
<af:autoSuggestBehavior suggestItems="#{VisitBackingBean.onSuggest}"/>
</af:inputText>
Bean Method:
public List onSuggest(FacesContext facesContext,
AutoSuggestUIHints autoSuggestUIHints) {
BindingContext bctx = BindingContext.getCurrent();
BindingContainer bindings = bctx.getCurrentBindingsEntry();
String inputNamevalue = autoSuggestUIHints.getSubmittedValue().trim();
if(inputNamevalue.contains(",")) {
inputNamevalue = inputNamevalue.substring(inputNamevalue.lastIndexOf(",")+1).trim();
//create suggestion list
List<SelectItem> items = new ArrayList<SelectItem>();
// if (autoSuggestUIHints.getSubmittedValue().length() > 3) {
OperationBinding setVariable =
(OperationBinding)bindings.get("setnameSearch");
setVariable.getParamsMap().put("value",
inputNamevalue);
setVariable.execute();
//the data in the suggest list is queried by a tree binding.
JUCtrlHierBinding hierBinding =
(JUCtrlHierBinding)bindings.get("AutoSuggestName_TUserROView1");
//re-query the list based on the new bind variable values
hierBinding.executeQuery();
//The rangeSet, the list of queries entries, is of type //JUCtrlValueBndingRef.
List<JUCtrlValueBindingRef> displayDataList =
hierBinding.getRangeSet();
for (JUCtrlValueBindingRef displayData : displayDataList) {
Row rw = displayData.getRow();
//populate the SelectItem list
items.add(new SelectItem(rw.getAttribute("UsrUserName").toString().trim() +
"<" +
rw.getAttribute("UsrMailId").toString().trim() +
">",
rw.getAttribute("UsrUserName").toString().trim() +
"<" +
rw.getAttribute("UsrMailId").toString().trim() +
">"));
return items;
Please suggest how can i achieve the mentioned functionality.

Hi,
doesn't work this way as the suggest list returns a single value. You can actually use the existing values as a prefix to the new value in which case the suggest list would look a bit odd. Beside of this all you can do is to create a user lookup field with auto suggest and once a name is selected, update another field with the value returned from this action
Frank

Customizing af:query component?

Hello friends,
Is it possible to customize af:query component. For example i need to move "search", "reset","save" buttons to the toolbar of the component and change the background of the toolbar. Also i have a request to hide that "+/-" thing which make able user to collapse or disclose af:query form.
Is it possible or only way to achieve this is to create my own search mechanism - what i can imagine could take a while?
thanks in advance

Hi,
as far as color coding goes, you can use skinning for this. Look for "af:query component" in http://download.oracle.com/docs/cd/E15523_01/apirefs.1111/e15862/toc.htm
This should also allow you to hide the +/- icons. However, it does not allow you to move buttons
Frank

Tabular form (select list Query based LOV)

Hi all,
I have this situation:
a tabular form with two "select list (query based LOV)" fields.
The first one must affect elements in the second one. And so the second query based LOV field should has a "where attr1 = first_list_selected_value" in the query.
Is this possible ? Could you show me some advices ?
thanks in advance.

OK, thank you.
But maybe I wasn't too clear.
I need cascading LOV for each row of my tabular form.
I have a EMP tabular form
select
"ROWID",
"EMPNO",
"ENAME",
"JOB",
"MGR",
"HIREDATE",
"SAL",
"COMM",
"DEPTNO"
from "#OWNER#"."EMP" I need a Select List for DEPTNO for each record of table. After set a value, the second "Select List" for ENAME should be affected automatically.

Auto suggest behavior for af:query component LOV fields.

Similar Messages

Maybe you are looking for