...
- TextView versus InputField-ReadOnly
- For text fields that will always be read-only, developers should use TextView (not InputField-ReadOnly).
- For text fields that will sometimes be editable but under other conditions read-only (e.g. HSA Details screen), developers would prefer to use InputField-ReadOnly.
- For screens that have a mix of field types, group things accordingly. Keep TextView together or InputFields together for better visual user experience. Try not to alternate or mix types.
- For confirmation screens and button order, follow the SAP standard of ordering the buttons in order of "Yes/No".
- For pop-ups that contain variable length texts ..... develop your own custom view.
- For Search Helps, see rule Accessibility rule #14 above.
- Layout choices: Matrix, Flow, Grid, or Row.... Matrix and Grid seem to be the leade
- UI Element formatting - details on formatting click here
- When launched, WDA applications should launch in a new, chrome-less window. Browsers' Back button has been disabled SAP.
- Need to verify with SAP any plans to enable Back button
- Need to re-visit when apps are incorporated into SAP Portal.
- Replace the "Home" link at the top of each WDA application page. Use the more accurate text "Close" rather than "Home".
- The Close link should be positioned in upper right hand corner of the app, just after the Help link.
- Separate Help and Close links by setting vGutter property in each to medium.
- Tables and ALV handling (findings based on NW 7.02)
- See Carolyn's notes on Automatically calculating totals, Javascript errors, multiple UI elements in single cell, focus within dropdown list.
...