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

Clicking on a Document ID from Doc Search opens a new window (different behavior than Action List)

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 0.9.2, KEW - 0.9.2
    • Fix Version/s: Not version specific
    • Component/s: Development
    • Labels:
      None
    • Environment:
      IE7 / REG
    • Similar issues:
      KULRICE-4104Opening from doc search opens new window - clicking close returns to the portal in the new window
      KULRICE-2548Docs opened from action list and document search are opening in a new window
      KULRICE-2006Opening KIM docs from workflow action list should not spawn new browser window
      KULRICE-12542Prevent KRAD views from opening in doc search iframe
      KULRICE-6587Document Search Results open in a new window regardless of the system parameter (DOCUMENT_SEARCH_POPUP_IND) value
      KULRICE-1119Dochandler links not launching in new window in sample app
      KULRICE-8693'Fiscal Officer Info Maintenance Document' type item not accessible from Action List and Doc Search
      KULRICE-6493RiceDev: Clicking on any doc id from action list or doc search results in 404 error
      KULRICE-1710Opening a Maintenance Document from the Action List or Document Search throws NPE
      KULRICE-13221KRAD transactional document navigation erroring out after coming from doc search
    • Rice Module:
      KEW
    • Application Requirement:
      KC

      Description

      Clicking on the document link in doc search results opens the document in a new browser window. Clicking a document link in the Action List does NOT open the document in a new browser window. Is this configurable behavior? Is there a reason why these are not consistent?

      Here's the comment from a KRA tester:

      "From the Main Menu tab in KRA / Proposal Development, if I click on the Doc Search button, then perform a search so at least some results are returned, then click on a Document ID to open a document for editing, a new browser window is opened with the Document ID and the header row missing (header row is the Kuali logo; Main Menu, Administration & My Stuff tabs; Action List, Doc Search, Workflow Services buttons) [see WithoutHeader.jpg attachment] This is confusing to have more windows opening up and inconsistent with other behaviors as mentioned below.

      In contrast, from the Main Menu tab in KRA / Proposal Development, if I click on the Action List button, a list of Document IDs are displayed, and clicking on a Document ID to open it for editing is loaded in the existing window with the header row intact. From an end user perspective, this is the expected behavior, it's simpler and I don't have to manage multiple windows and upper level menus (from the header row) are intact. [see WithHeader.jpg attachment]

      At any rate this should be consistent behavior across the Kuali, preferably the simpler more intuitive behavior that currently functions when opening Documents from the Action List button."

        Activity

        Hide
        Eric Westfall added a comment -

        See the Application Constants documentation

        https://test.kuali.org/confluence/display/KULRICE/KEW+Application+Constants

        I think the 2 relevant to this discussion are:

        ActionList.IsDocumentPopup
        DocumentSearch.IsDocumentPopup

        Let me know what settings you've got for those and whether or not they are working as advertised.

        Show
        Eric Westfall added a comment - See the Application Constants documentation https://test.kuali.org/confluence/display/KULRICE/KEW+Application+Constants I think the 2 relevant to this discussion are: ActionList.IsDocumentPopup DocumentSearch.IsDocumentPopup Let me know what settings you've got for those and whether or not they are working as advertised.
        Hide
        Bryan Hutchinson added a comment -

        I looked in our kra-reg environment, and we actually only had a few Application Constants, one of which is DocumentSearch.IsDocumentPopup set to true.
        I changed it to false, and that opened the document from doc search within my current browser window.

        Thanks for pointing me in the right direction.

        Show
        Bryan Hutchinson added a comment - I looked in our kra-reg environment, and we actually only had a few Application Constants, one of which is DocumentSearch.IsDocumentPopup set to true. I changed it to false, and that opened the document from doc search within my current browser window. Thanks for pointing me in the right direction.
        Hide
        Bryan Hutchinson added a comment -

        Eric pointed me at the KEW application constants that control this behavior, and now we should be able to configure this exactly how we want in KRA.

        Show
        Bryan Hutchinson added a comment - Eric pointed me at the KEW application constants that control this behavior, and now we should be able to configure this exactly how we want in KRA.

          People

          • Assignee:
            Unassigned
            Reporter:
            Bryan Hutchinson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel