Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-5447

KRAD application header/controls - persistence on page

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • 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.

        Attachments

          Issue Links

            Activity

            csoders Candace Soderston (Inactive) created issue -
            csoders Candace Soderston (Inactive) made changes -
            Field Original Value New Value
            Link This issue cloned from KULRICE-5446 [ KULRICE-5446 ]
            csoders Candace Soderston (Inactive) made changes -
            Summary CLONE - KRAD/KS navigation pane should persist on page KRAD application header/controls - persistence on page
            Description KRAD/KS navigation links should persist on the page, not scroll off screen when user scrolls down through long form. User should be able to use this navigation "pane" to change their location within the application.
            Research shows this type of visual/navigation anchoring helps users not feel lost within long tasks.
            KRAD/KS application header/controls - persistence in the view when user scrolls down through long form.

            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.
            csoders Candace Soderston (Inactive) made changes -
            Description KRAD/KS application header/controls - persistence in the view when user scrolls down through long form.

            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.
            KRAD/KS application header/controls - persistence in the view when user scrolls down through long form.

            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.
            csoders Candace Soderston (Inactive) made changes -
            Description KRAD/KS application header/controls - persistence in the view when user scrolls down through long form.

            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.
            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.
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Fix Version/s 2.1 [ 15812 ]
            KAI Review Status Not Required Pending Review
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Start Date
            Fix Date [ set to sprint end date ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Fix Version/s 2.2 [ 16411 ]
            Fix Version/s 2.1 [ 15812 ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Start Date
            Fix Date [ set to sprint end date ]
            jkneal Jerry Neal (Inactive) made changes -
            Rice Lead jkneal
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Fix Version/s 2.2-backlog [ 16475 ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Start Date
            Fix Date [ set to sprint end date ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Fix Version/s 2.2.1 [ 16733 ]
            Fix Version/s 2.2 [ 16411 ]
            Fix Version/s 2.2-backlog [ 16475 ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Fix Version/s 2.3-backlog [ 16596 ]
            Fix Version/s 2.2.1 [ 16733 ]
            jkneal Jerry Neal (Inactive) made changes -
            Link This issue relates to KULRICE-8877 [ KULRICE-8877 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow custom [ 101364 ] Copy of custom for rice [ 207111 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow Copy of custom for rice [ 207111 ] custom [ 216859 ]
            spatterson Shem Patterson (Inactive) made changes -
            Workflow custom [ 216859 ] Rice Workflow [ 226607 ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Fix Version/s 2.4 [ 16913 ]
            Fix Version/s 2.4-backlog [ 16596 ]
            jcoltrin Jessica Coltrin (Inactive) made changes -
            Fix Version/s Backlog [ 15811 ]
            Fix Version/s 2.4 [ 16913 ]
            kbtaylor Kristina Taylor (Inactive) made changes -
            Rank Ranked higher
            kbtaylor Kristina Taylor (Inactive) made changes -
            Rank Ranked higher
            kbtaylor Kristina Taylor (Inactive) made changes -
            Rank Ranked higher
            kbtaylor Kristina Taylor (Inactive) made changes -
            Rank Ranked higher
            ewestfal Eric Westfall made changes -
            Labels Old

              People

              • Assignee:
                Unassigned
                Reporter:
                csoders Candace Soderston (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: