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

When clicking on the lookup icon for "Parent Document Type" on the Document Type lookup, we need to change the label in the header of the page to read "Parent Document Type"


    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-10181"Nested" Document Type lookup potentially confusing for users
      KULRICE-8603Create Document Type Parent Name lookup hides create new button.
      KULRICE-1420Doc Search - clicking Parent Document search on Document Type look up goes to the same Doc Type look up screen.
      KULRICE-929Issue with parent document type linking
      KULRICE-2752When ingesting new document types, the system errors out if parent document types are not ingested before child document types
      KULRICE-2459tweaks to document type xsd to account for document type merge / changes and avoid redundancy in parent/child document types
      KULRICE-12273Document Type lookup caches results incorrectly
      KULRICE-943Update workgroup documentation to include Workgroup types and configuration
      KULRICE-4497If no "Resolve Exception" responsibility is defined for a particular document type (or one of it's parents) then the document will silently fail to go into exception routing
      KULRICE-7043There is no longer a lookup icon on the "Document Type Name" field on the Responsibility screen
    • Rice Module:
      KNS, KEW


      Currently it's confusing when you click on the Parent Document Type lookup icon in the Document Type lookup. In that case, it takes you back into the Document Type lookup so you can lookup the parent. However, this is very confusing for the user because the page looks the same.

      I'm not sure exactly what our options are here, probably one of:

      1) See if there is some hook in the Lookup helper that would help us do this (still, in that case, not sure how you would determine the proper context so you would know when to display what?)
      2) Create a whole new lookup definition for the parent document type (this might require another business object which may not be an option?)
      3) Add support to the lookup framework for passing a request parameter that can override the default page label. Only issue with this is that we would need to have some way of telling the doc type lookup to pass this parameter. I'm not sure what the options are there.

        Issue Links



            • Assignee:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created:

                Structure Helper Panel