1. Rice 2.2 – KRAD Help Framework Requirements Review – KAI meeting, 2/16/2012 C Soderston, Kuali Rice 2.2 – KRAD BA & UX 1

2. Online Help – Current UI Challenges o Student-facing applications need “just-in-time” self-service help:  Students want to “learn by doing” – they don’t have time to read a users’ guide. They actively explore, looking for relevant task-specific 'nuggets' of information (in tooltips and other) when they use a new application or infrequently use it.  Applies also to IT and BA-facing applications that can't assume a steep learning curve or external, scheduled training for infrequently performed tasks. o KNS doesn’t make it easy for applications to provide and manage context-specific online help:  Field-level help  Section-level help  Page-level help  View-level help (KFS and KC support this in the KNS model – see next slide  ) 2

3. Example 1 – What Applications do today KFS and KC provide a view-level help icon that opens another browser tab KFS test drive = all documents (views) KC test drive = lookup documents (views) 3 KFS opens to document-specific information within the application-level help: KC opens to document type-specific information:

4. Example 1 – How Applications do it today 4 KFS opens to document-specific information within the application-level help: KC opens to document type information: KFS online help authors complete a spreadsheet - identifies the “URL” for each help topic = the name of the top-level html file for each doctype Spreadsheet delivered to KFS development along with zip file that contains the html files KFS developers insert the appropriate “URL” into the places in the code-base, to launch the appropriate action upon the users' selecting a help icon. Pessimistic Lock Lookup <a title="[Help]lookup help" target="helpWindow" tabindex="-1" href="https://testdrive.kc.kuali.org:443/kc- ptd/kr/help.do?methodToCall=getLookupHelpText&lookupBusiness ObjectClassName= org.kuali.rice.kns.document.authorization.PessimisticLock"> <img hspace="5" border="0" align="middle" alt="[Help]lookup help" src="/kc-ptd/kr/static/images/my_cp_inf.gif"> Customer Invoice Writeoff <img hspace="5" border="0" align="middle" alt="[Help]document help" src="http://testdrive.kfs.kuali.org/kfs- ptd/kr/static/images/my_cp_inf.gif"> See Google doc on how to configureGoogle doc on how to configure

5. Example 2 – Additions in Rice 2.0 KRAD 5 KRAD makes it easier to associate "visible” context-specific information with input fields: Instructional text Constraint text Watermark in the input field (or pre-filled with a valid default) Auto-complete behavior (recognition/type- ahead - suggest). Other visible information in KRAD today: Styled explanatory text can be provided anywhere it is needed (top of page, beginning of section, etc.) KRAD and KNS: “Requiredness” indicator (*) Drop-down control that enables the user to select from a valid set of alternatives (not shown) Other controls, such as a lookup or inquiry icon, to the right of the field (not shown)

6. Rice 2.2 KRAD - Help framework Requirements 6 Primary: #1: Create a context-sensitive help information architecture #2: Create an integrate-able help information architecture that makes it easy to link … #3: Enable applications to choose which level(s) of the help content to implement #4: Support the integration/use of the html output from any authoring tools that output into standard XML/HTML source -- essentially, support linking to the content from any content management repository selected by the application / university. Secondary: #5: Create an online help architecture that fully converges the aspect of online help with the aspect of electronic documentation. See https://wiki.kuali.org/display/KULRICE/KRAD+-+Help+Framework for additional details.https://wiki.kuali.org/display/KULRICE/KRAD+-+Help+Framework

7. Rice 2.2 KRAD – diagram of Help Constructs 7 View and Page-level help in a new browser window o Section-level help in a rich tooltip (supports links & interactive controls, user interaction) o Field-level help in a “simple” tooltip (concise text snippet, no interaction) Note – the model is flexible - there are no obstacles to prevent Rich tooltips for Fields or Sub-sections New browser window for Sections or Sub-sections But … large tooltips would not be usable, are not advised for view or page-level help!

8. Rice 2.2 KRAD – “Simple” Tooltip Example 8 Tooltips appear on hover (mouse) and on focus (keyboard) Supported on controls, field labels, headers Example simple tooltip – concise text … (The above is a low-fidelity rendition – the precise visual treatment details are yet to be determined)

9. Rice 2.2 KRAD – “Complex” Tooltip Example 9 User can move into the tooltip to interact with elements within it Tooltip disappears when user moves outside of the triggering element and its contiguous tooltip area Everything else is the same as a simple tooltip (same list of trigger elements supported, same triggering behavior, etc.) Example “Complex” tooltip Information tidbit 1 Information tidbit 2 Link to additional help information in separate browser window Example “Complex” tooltip Information tidbit 1 Information tidbit 2 Link to additional help information in separate browser window

10. Rice 2.2 KRAD – Help window example 10 Same behavior as today except launches a new browser window (not a tab) with a default window size and placement relative to the application window. (Specifics tbd, and there will be a new help icon & visual treatment in Rice 2.2 KRAD.) KFS example:

11. Additional considerations “KRAD should include a setting to enable an application to turn off (hide) the help icon, at a global level (per application).” “KRAD should enable doing this same thing at a view (document) and page level.” Question: Example scenarios – why needed? 11

12. Summary – KAI Discussion & Feedback Assessment across the applications – longer-term impact to you and your users? Other comments / changes? 12