...
- Application Help will be stored primarily in Hermes (http://kb.mit.edu)
- When linking to help in Hermes use the Short link, e.g. http://kb.mit.edu/confluence/x/2gTn not the Full link
- This is to protect against the article / title changing in the future which affects the Full link but not the Short link.
- Launch application help window a smaller, less overwhelming window (50% sized) with no ‘chrome’ (no navigation menu, no status bar at bottom).
- Here’s the ABAP code:
lv_url = 'http://kb.mit.edu/confluence/pages/viewpage.action?pageId=3902416'. "change url to your app-specific help page
lo_window = lo_window_mg->create_external_window( url = lv_url
modal = abap_true
has_menubar = abap_false
is_resizable = abap_true
has_scrollbars = abap_true
has_statusbar = abap_false
has_toolbar = abap_false
has_location = abap_false
).
lo_window->set_window_size( width = '600px'
height = '800px' ).
lo_window->set_window_position(
left = 400
top = 100 ).
- For now, point to Production Hermes help file URLs.
- Mike Berger will check with Alison Bell re: release process for Hermes content, viability of pointing to non-Prod content (esp for new apps)
- Open issue regarding browser and pop-up blockers
...
- 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 .....<Mark/Carolyn looking at this>
- For Search Helps, see rule Accessibility rule #14 above.
Miscellaneous topics
Development packages
If you create a WD App as a local object ($TMP) then move it to another development package (e.g. ZHR0), the corresponding ICF services will not automatically move to the new development package. The same thing happens when you delete a WD app – the corresponding ICF is never deleted. You must manually update the ICF service package.