Can we have a POLL for UI element Enhancements proposal as in WDJ Forum

Question

Dear Moderator
Can we have a POLL where we can suggest  UI element/Functionality enhancements in WDA  like the one we have in Web Dynpro Java Forum.
This can be useful for next releases of Web Dynpro ABAP.
Thanks
Abhimanyu

Answer 1

Some more.
6) Currently if we have Cell Variants, they have to be bound to context for the key values of corresponding cell editor.
If the key value doesnt match to any of the cell editor keys, application dumps saying invalid key. Instead of dumping, can there be a default editor, incase the key doesnt match?
7) ALV loosing the lead selection, when the view layout has sort order.
     - I understand that this is required up on certain context changes like rebinding complete data. However most of the times, we want to re-select the previous lead selection before ALV Refresh had reset it.
     As this happens inside Modify view of ALV, unless otherwise we use explicit Refresh, there is no other option.
     Is it possible for ALV to throw an event if the ALV services like Sort has lead to any context changes like Lost of Lead selection?
8) Search helps:
This requirement came from many users. Users would like to have custom search helps with in DDIC Search Help.
This can be any popup for performing search not just another DDIC search help. I am not sure but I think this is possible with Screen programming but not in WD.
Also more control is required to handle to F4 or Simulate F4, i.e. for example, to throw the same DDIC Search help if the user hits Enter.
The major functionality that users will miss, if they other search helps like OVS or Custom Search help, is the Personal Value List (PVL). Can we have some WD interface methods, that will help to enable/disable PVL with these custom search helps
9) Mandatory attributes check:
The current WD utilities mandatory attribute check method, does not return all the mandatory attributes for that View and context.
Also it works on lead selected data. Assuming there are hundreds of elements in context (for an ALV/Table), and the detail view has some mandatory attributes, this check has to be done every time for each and every lead selection.
Also, most of the times, the child node data changes based on parent node data. In these situations we will need all the mandatory attributes upfront and required checks has to be executed.
It will help a lot if the mandatory attributesto are passed back by the WD Utilities method once it calculates.
Thanks,
Anand
Edited by: Anand Nidamanuru on Dec 11, 2009 10:10 AM