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

Remove InquiryNoResultView and build logic into main view

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0.0-rc1, 2.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-5238build agenda tree UI components
      KULRICE-9774Review template logic
      KULRICE-8803Inquiry bases logic on readonly for building inquiry or direct inquiry based on the readonly flag of the Inquiry widget, not the field it applies to
      KULRICE-11196Sticky header logic fixes
      KULRICE-11047Remove build-time dependencies on ojdbc6_g.jar
      KULRICE-7072Default values are applied at the end of the view lifecycle so not seen by inquiry
      KULRICE-7311Fix failing tests in build
      KULRICE-1568Remove kew/src/main/config/sql directory
      KULRICE-9380refactor DocumentHeader so that we can remove special logic for stashing the WorkflowDocument in the UserSession
      KULRICE-8688Build out Component Library Views for KRAD Sample App
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      We have an InquiryNoResultView that was created to display a message when the inquiry record is not found. Having a separate view will cause maintenance issues and possibly require two views to be implemented for an inquiry in some cases. We need to build the logic into the main inquiry view to display a message when the record is not found. Part of the reason the separate view was created is a NPE was being thrown on the main view if we tried to render when the inquiry object is null. We need to fix that as well.

        Issue Links

          Activity

          Show
          Matthew Wuertz (Inactive) added a comment - Here is how I've been testing the issue: Go to KRAD tab, select Travel Account Inquiry. After the page loads, change the URL so that the number parameter has an invalid name. For example, http://localhost:8080/kr-dev/portal.do?channelTitle=Travel%20Account%20Inquiry&channelUrl=http://localhost:8080/kr-dev/kr-krad/inquiry?methodToCall=start&number=a14&dataObjectClassName=edu.sampleu.travel.bo.TravelAccount&returnLocation=http://localhost:8080/kr-dev/portal.do&hideReturnLink=true becomes: http://localhost:8080/kr-dev/portal.do?channelTitle=Travel%20Account%20Inquiry&channelUrl=http://localhost:8080/kr-dev/kr-krad/inquiry?methodToCall=start&foo=a14&dataObjectClassName=edu.sampleu.travel.bo.TravelAccount&returnLocation=http://localhost:8080/kr-dev/portal.do&hideReturnLink=true
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Closing since these items are now in the release notes.

          Show
          Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

            People

            • Assignee:
              Matthew Wuertz (Inactive)
              Reporter:
              Jerry Neal (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel