Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7203Go through KRAD script files and create constants
      KULRICE-5355Lookup - return values opens new tab, the return target is not set
      KULRICE-7255Lookup return issues
      KULRICE-9864Add Lookup Conversion to Conversion Script - Part 1
      KULRICE-10124Add Lookup Conversion to Conversion Script - Part 2
      KULRICE-502links and buttons broken on nested lookups access through mutiple values lookup
      KULRICE-11450Maintenance Conversion Script - M17 Disclosure Default Open
      KULRICE-14026Loading indication not needed by return by script lookups and interfers requests
      KULRICE-8440404 Error when accessing a KRAD page through the portal
      KULRICE-3928KIM Lookups not opening inquiries in new windows
    • KRAD Feature Area:
      Document
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Currently the quickfinder posts the page which sends back a redirect URL, which is then rendered in the lightbox. This is a lot of overhead. Instead, we should be able to build the URL through script and invoke the lightbox without posting the page

        Issue Links

          Activity

          Hide
          Claus Niesen added a comment -

          Quickfinder content doesn't get rendered in lightbox. The browser console shows a GET 400 bad request error.

          Reverting commit 46253 fixes this.

          Show
          Claus Niesen added a comment - Quickfinder content doesn't get rendered in lightbox. The browser console shows a GET 400 bad request error. Reverting commit 46253 fixes this.
          Hide
          Jerry Neal (Inactive) added a comment -

          All,

          Looks like this code was reverted on the 2.4 branch. We still have it on 2.5 and ran into the same issues. So we are going to revert it there as well. But we should reopen this issue to take a look at implementing this functionality again right?

          I will take a look at the initial work to see if I can provide some suggestions.

          thanks,
          Jerry

          Show
          Jerry Neal (Inactive) added a comment - All, Looks like this code was reverted on the 2.4 branch. We still have it on 2.5 and ran into the same issues. So we are going to revert it there as well. But we should reopen this issue to take a look at implementing this functionality again right? I will take a look at the initial work to see if I can provide some suggestions. thanks, Jerry
          Hide
          Jerry Neal (Inactive) added a comment -

          Matt,

          A few things with the initial implementation of this. First, the code that broke lookups was around the baseURL:

          var baseURI = this.documentURI;
          if (baseURI.indexOf("?") > -1)

          { baseURI = baseURI.substring(0, baseURI.indexOf("?")); }

          var lookupUrl = baseURI.replace("kradsampleapp", "lookup?");

          Instead of this, we can get the baseUrl through the action parameters:

          var lookupUrl = data['actionParameters[baseLookupUrl]'];

          Also, take a look at performLookup in UifControllerBase. Instead of hard-coding the URL parameters, we should be able to pull those from the actionParameters map like is being done in the base controller.

          thanks,
          Jerry

          Show
          Jerry Neal (Inactive) added a comment - Matt, A few things with the initial implementation of this. First, the code that broke lookups was around the baseURL: var baseURI = this.documentURI; if (baseURI.indexOf("?") > -1) { baseURI = baseURI.substring(0, baseURI.indexOf("?")); } var lookupUrl = baseURI.replace("kradsampleapp", "lookup?"); Instead of this, we can get the baseUrl through the action parameters: var lookupUrl = data['actionParameters [baseLookupUrl] ']; Also, take a look at performLookup in UifControllerBase. Instead of hard-coding the URL parameters, we should be able to pull those from the actionParameters map like is being done in the base controller. thanks, Jerry
          Hide
          Sona Sona (Inactive) added a comment -

          Reopening because this causes KULRICE-12730. Using KIM User Control throws "lookupable is null" error.

          This is happening because Person is an externalizableDataObject and the performLookup in UifControllerBase was translating the externalizableDataObject to a new lookupURL with the dataObjectClass changed to PersonImpl.

          With the fix for this jira we are now skipping the initial call to performLookup and this won't work for any externalizableDataObjects.

          One solution I thought was to override baseLookupURL in quickFinder in the UserControl, but that won't work because the quickFinder lifecycle runs after that and overrides the baseLookupURL.

          We need to come up with a mechanism to deal with the lookups for EBO.

          Show
          Sona Sona (Inactive) added a comment - Reopening because this causes KULRICE-12730 . Using KIM User Control throws "lookupable is null" error. This is happening because Person is an externalizableDataObject and the performLookup in UifControllerBase was translating the externalizableDataObject to a new lookupURL with the dataObjectClass changed to PersonImpl. With the fix for this jira we are now skipping the initial call to performLookup and this won't work for any externalizableDataObjects. One solution I thought was to override baseLookupURL in quickFinder in the UserControl, but that won't work because the quickFinder lifecycle runs after that and overrides the baseLookupURL. We need to come up with a mechanism to deal with the lookups for EBO.
          Hide
          Jeff Ruch added a comment -

          This issue caused KULRICE-12744 Quickfinder Lookup doesn't populate criteria fields with data from calling field. The form data (lookupCriteria) is no longer posted. I verified that reverting the changes to krad.widget.js.createLightBoxPost() resolves KULRICE-12744.

          Show
          Jeff Ruch added a comment - This issue caused KULRICE-12744 Quickfinder Lookup doesn't populate criteria fields with data from calling field. The form data (lookupCriteria) is no longer posted. I verified that reverting the changes to krad.widget.js.createLightBoxPost() resolves KULRICE-12744 .
          Hide
          Jeff Ruch added a comment -
          Show
          Jeff Ruch added a comment - KULRICE-10909 causes KULRICE-12744
          Hide
          Matthew Wuertz (Inactive) added a comment -

          I have addressed 12744 and 12730.

          Show
          Matthew Wuertz (Inactive) added a comment - I have addressed 12744 and 12730.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days, 2 hours
                2d 2h
                Remaining:
                Remaining Estimate - 2 days, 2 hours
                2d 2h
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel