Extended Value Selector- Problem update

[Former Member]

Hi,

We have an interface that contains two input fields that use the Extended Value Selector widget. One of the fields is dependent on the other i.e. when the field's value changes the possible values of the other are also updated.

Our problem is that the possible values of the second field are not updated when the user presses tab to get to the next field. When the user opens the extended value selector for the first time the values are not up to date. However, on the second attempt the values are correct.

It seems that the correct values are loaded, but not shown in the Widget. Does anyone know of a possible solution/workaround?

Cheers,

Jens

[Former Member]

Hi Jens,

Ideally, you populate the second field's EVS values on an "action". And unfortunately pressing tab or focusing on the field does not generate an event and hence they are not populated.

What's happening in your case is, when the user opens the second EVS, framework generates an auto event and a server round trip and then the values get populated for the second time.

As you say both the fields are input fields, make the user press enter in the first field and onEnter of this field, populate field2's EVS values.

Hope that helps.

Cheers,

Rajit

Message was edited by:

Rajit Srinivas

[Former Member]

Hi Rajit,

first of all thanks for your answer. I am not sure I was clear enough with the description of the problem. The use case of the problem is as follows:

1) User enters 0024 in field one

2) User presses tab

3) User opens EVS via F4 or via the mouse

3.1) Server roundtrip is made and values are collected (we saw this in the logs).

4) <b>The EVS is opened but with the wrong values</b>

5) User closes EVS

6) User opens EVS, again via F4 or via the mouse

7) <b>Correct values are shown.</b>

Note: Our logs show that the values are populated at point 3.1).

Pressing enter after point 1 does work, however because our application is used by many call center agents, who try to avoid as many key presses as possible, it is a problematic solution to enforce.

At present the values are checked later stage and an error message is shown, but we are wondering if there is a possibility to solve the problem programically and as unintrusive to the user interaction as possible.

Cheers,

Jens

[Former Member]

Hi,

Is your EVS dependended on the value entered in field one.

Ex: Country-> State.

If this is the scenario pl check that the new value is passed to the backend.

Regards

Ayyapparaj

[Former Member]

Hi Ayyapparaj,

the log entries show that everything in the backend is correct, only what is shown is wrong and inconsistant with these logs.

Cheers,

Jens