Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Indicate the necessity for this enhancement. What does it accomplish?

Detailed Description

Give a detailed description for the enhancement. Clearly describe all concerns, eliminating ambiguities.

Usage Scenarios

Include at least one usage scenario, from the user's task perspective, that might be helpful in understanding the issue:

Mocks and Diagrams

Include any mocks (for UI enhancements) or diagrams that might be helpful in understanding the issue:


If applicable, list expectations for performance (optimal and worst cases would be fine, give time in seconds):


Include links to other confluence pages or external resources that might be helpful for this issue:

Requirements Listing

List all requirements (individual verifiable statements) that indicate whether the work for this item has been complete. If there are requirements that are not essential to the functionality but would be nice to have if time allows, enter those under 'Non-Essential':

  1. Performance Improvements (Req #1)
  2. Framework Code Improvements (Req #2)
  3. Error & other Validation Message refactoring for Accessibility (Req #3)
  4. Tooltip (relates to Help framework - see next item for the larger context of choices) (Req #4)
  5. Help Framework (also needed for KNS equivalence) (Req #5)
  6. Question Framework - configurable modal dialog box (also needed for KNS equivalence).   See also #11 below. (Req #6)
  7. Master detail relationship within a table (Req #30)
  8. Collections re-design: Add collection button adds line with blank fields, user enters data in fields, no additional add action needed (Req #24)
  9. Collections re-design: Add collection item via lightbox (or other) (Req #25)
  10. Collections re-design: action field column placement (left or right) configurable (Req #26)
  11. Collections re-design: Yellow highlighting on new collection items (until submit) - & maybe when hovering on delete function (Req #27)
  12. Collections re-design: Total Lines and Grouping (needed for KNS Equivalence) (Req #28)
  13. Messages from Central Repository (Req #7)
  14. Rich Messages (Req #8)
  15. State-based validation (Req #9)
  16. Access (view only) without authenticating into portal (Req #10)
  17. General Lightbox Div Content - (this is the UI aspect of the question framework item above - that one is the backend aspect) (Req #11)
  18. Table sub-collections within table collections_(Req #34)
  19. Dictionary Validation (validation of XML configuration on startup or by separate program) (Req #12)
  20. Missing Lookup Functionality (needed for KNS Equivalence) KULRICE-5435 (Req #13)
  21. Tables - standard semantics encoded (accessibility & readies for smaller devices) (Req #14)
  22. Tabs - standard semantics encoded (accessibility & readies for smaller devices) (Req #15)
  23. Keyboard Support (enter key, other shortcuts, back to top) (Req #16) 
  24. Code cleanup - Compliance to W3C standards (code checker output) (Req #17) - needs more detail/clarification and if it should be part of this or just general maintenance work.
  25. Improved Session Support (restore when session dies, multiple user tab support) - Multi-tasking support capability - so that documents don't "hose" each other when multiple processes from the same user session are invoked.  Support multiple browser tab support. (Req #18)
  26. Missing Maintenance Functionality (needed for KNS Equivalence) KULRICE-8055, KULRICE-8056 (Req #19)
  27. Finish support for Authorizer and Presentation Controller (needed for KNS Equivalence) KULRICE-8049 (Req #20)
  28. Convert Portal to use Spring  (needed for KNS Equivalence) KULRICE-8244 (Req #21)
  29. Applications access data via Services versus via direct database access (Req #22)
  30. Legend tag for fieldsets (Req #23)
  31. Allow wildcard searches on numeric fields (e.g. DocID) (Req #29)
  32. Filtered & Faceted search, including Was previously Req #12:  Lookup Support for Faceted Search (Req #31)
  33. Combobox Control (Req #32)
  34. Inline Edit widget (Req #33) 
  35. User Preferences (Req #35)
    1. global
    2. per session
    3. per BO
    4. Filter search results by user
  36. Breadcrumbs revisit and support for breadcrumbs in a lightbox (chain) that aren't view lookups (Req #36)
  37. Unique URLs for pages (in the left nav or tab) (Req #37)
  38. Back-button support for js actions (pushing history of js actions to browsers history) (Req #38)
  39. Left navigation widget comprised of anchors (Req #39)
  40. UI boilerplate elements - make always in view (left nav, buttons, breadcrumbs), while others scroll away or collapse (Req #40)
  41. Undo support (Req #41)
  42. "Back to top" link or keyboard shortcut for all section and subsection headers (relates to #16 in set 1 above) (Req #42)
  43. Combine "lookup" and "inquiry" or "maintenance" views on one page, or easily get back and forth between the two (Req #43)
  1. item
  2. item


List any functional or technical work that must be completed before work on this item can begin:

  1. item


List any issues that need to be resolved before work on this item can begin:

  1. item
  2. item
  1. item
  2. item

QA or Regression Testing Plan

List steps needed to test the basic functionality of this update, enhancement, bug fix

  1. test/steps
  2. test/steps


Functional Analysis Complete? No (completed by SME)

Needs Review by KAI? No (completed by SME)

Technical Analysis Complete? No (completed by DM)

Needs Review by KTI? No (completed by DM)

Estimate: ~1000 hours (completed by DM)

Technical Design: Link Here (completed by DM)

Jira: KRRM-141 - Data cannot be retrieved due to an unexpected error (completed by SME)

Final Documentation: Link Here (completed by DM)

Added to QA: No (completed by SME)

  • No labels