[KULRICE-5447] KRAD application header/controls - persistence on page Created: 01/Aug/11  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: Backlog
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Minor
Reporter: Candace Soderston (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
cloned from KULRICE-5446 KRAD/KS navigation pane behavior Open
Relate
relates to KULRICE-8877 UI boilerplate elements - make always... Closed
Similar issues:
KULRICE-9528Document how KRAD handles it's own internal classes (doc header, etc.) in terms of managing them in their own persistence unit
KULRICE-9872Implement a simple approach for importing common KRAD JPA entities into a KRAD application's persistence context
KULRICE-3999Need a dynamic way to add classes to kns-application-unit persistence unit
KULRICE-7158Validation messaging - single checkbox tooltip persists/open
KULRICE-10349The expanded/collapsed state does not persist on refreshed INITIATED documents
KULRICE-13260KRAD Library Fixed Application Header isn't fixed
KULRICE-5652Create KRAD Version of Create New Sample Application Travel Request Document
KULRICE-1364Add horizontal tab page to sample application
KULRICE-6684Rename KRAD Jsp for application view
KULRICE-10040KRAD Sample Application: Maintence doc displays. Route Log Section shows 404 Error.
Rice Module:
KRAD
Application Requirement:
KS
KAI Review Status: Pending Review
KTI Review Status: Not Required

 Description   

KRAD/KS application header/controls - persistence on the page

In the current design, the KRAD/KS application header/controls includes the page/branding area, "Kuali Portal Index", provide feedback link, greyed-out info line "Rice sample app ... Oracle 9i" (is this needed, in the customer version?), the "Main Menu" and "Administration" tabs, the "Action List" and "Doc Search" links, and the log-in info fields and buttons. These are universal across all pages - this is conceptually the application header/controls area.

Similarly, there is currently a footer area that has only the copyright and acknowledgements, but in some web-apps includes navigation links to other parts of the app (the left nav contents depend on the current task, the bottom nav contents do not).

Let's consider the trade-offs in making these areas persistent in the view, not scrolling off the page when user scrolls down or up through long form. They take up real estate, so there are reasons not to persist these areas in the view. As long as they persist at the top and bottom of each page, not vary across pages, that may be sufficient.


Generated at Fri Feb 28 08:47:40 CST 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.