Value Help/Value Selector behavior on WebDynpro 7.0 different from WD 6.4

[Former Member]

Problem:

During the conversion of our applications from Web Dynpro 6.4 to 7.0, it was identified different behaviors in the same applications deployed in 7.0 that did not happens at 6.4.

If you have more than 1 “Value Help”, fill then with invalid values, press a “Value Help” and select a valid value, the validation of all “Value Help” are done and error messages are showed.

It happens too if “Value Help” are filled with invalid values and you and press a “Submit” button even with its action set as “Without Validation”.

Any one knows if this is a bug or if there is a correction ?

If not, how to keep the same behavior without change the application (simplest way) ?

Thanks in advance...

[Former Member]

Answer,

- It is not a bug, SAP in WebDynpro 7.0 SAP had deliberately changed the behaviour of validating actions

- Until now, no way to keep the same behavior without change the application.

Below, SAP answer:

>>

"In 7.0 SAP had deliberately changed the behaviour of validating actions

because we had the opinion it would be better to show the message as

early as possible (considering AJAX design in mind). The behaviour of

the application doesn't change at all, in fact. Another reason for this

change was the following scenario. If we would check errors on the

client some time in the future, the behaviour would be consistent for

the end user regardless whether the messages arise in the client or in

the server, because they're displayed immediately after the problem is

recognized. With the old style(640) the client had only been allowed to

show the messages when the user triggers a validating action. This

behaviour is quite altbacken i.e. old-fashioned especially when

considering Ajax.

As this was an intentional design change in 7.0 by SAP, We do not plan

to revert this.

The major reason is to show the message as early as possible. We also

have in mind that in the future we might have validation code on the

client (well, perhaps not in the browser) which definitely will show themessage very early. Non-validating actions were merely intended for

activities like cancelling a selection or Previous in wizard-like

applications where the invalid input does not matter any longer."

<<

Best regards.