Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-8871

Combine "lookup" and "inquiry" or "maintenance" views (Mix of view, and edit or retrieve) on one page, or easily get back and forth between the two

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2
    • Fix Version/s: Backlog
    • Component/s: Development, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-7066Issue when two quickfinders on same view have different lookup configuration
      KULRICE-9667Inquiry Views with Uif-Page broken
      KULRICE-12392KRMS Agenda Inquiry View: problems with “View Rule” button.
      KULRICE-10995Lookup ux/ui redesign: full page view
      KULRICE-113Simplify how the Lookup, Inquiry, and Maintenance tags get access to the DD
      KULRICE-9880Create Automated Functional (Smoke) Tests for KRAD Labs - Lookup Views
      KULRICE-8584Going back to a lookup from an inquiry with breadcrumbs throws exception
      KULRICE-9693topGroup AND View header needs to display updated information (ie. when a page loads, not just the view)
      KULRICE-5698edit links from the agenda lookup no longer work
      KULRICE-5981Breadcrumbs with single page views
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Inquiry, Lookup, Maintenance
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      From KOLE: Our use best use case is for Patron-Driven Acquisitions or Patron Circulation. A User would enter all transactional information into the PO or circulation e-doc or interface, and need to select or input the Patron's information. This would initiate through a Lookup, search, and return value (current Lookup function). But, if the Patron/User is not found, we would like to be able to jump to a Maintenance doc or other Patron UI, enter the Patron information, save, and return the value/select for input into the transactional edoc (combined transactional and maintenance actions in simplified views and fewer steps than today).

        Issue Links

          Activity

          Hide
          Matt Sargent added a comment -

          from William: Could this be accomplished with the "Inner Views" functionality? Or resolved by keeping user's data in the transaction form while they go to a maintenance doc to create a new record?

          Show
          Matt Sargent added a comment - from William: Could this be accomplished with the "Inner Views" functionality? Or resolved by keeping user's data in the transaction form while they go to a maintenance doc to create a new record?

            People

            • Assignee:
              Unassigned
              Reporter:
              William Washington (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel