Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.5
    • Fix Version/s: 2.5.1
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-2896Inquiries for DocumentType EBO using the doc type name only do not work
      KULRICE-10103Collection index on view only allows the same collection to be on the view once
      KULRICE-8431Performance: perform expression function setup only once per lifecycle
      KULRICE-12388Supress inquiry links on inquiry view if they point to the same view
      KULRICE-1579Direct inquiry links do not work on maintenance documents
      KULRICE-7402Issue with Chrome using close buttons after executing an export
      KULRICE-13014Create KRAD widget to handle read-only KIM inquiries
      KULRICE-4727Ability to specify links in data dictionary
      KULRICE-6856Supress inquiry links on inquiry view if they point to the same view
      KULRICE-2574Figure out where we have bad inquiry links for "users" and "workgroups" and update them to use new KIM inquiries
    • Rice Team:
      Middleware
    • Sprint:
      Middleware 2.5.1 Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes
    • Story Points:
      2

      Description

      "KRAD LAB -> Inquiry -> Inquiry - forceUppercase": use inquiry on "A" once, then close the dialog. Now the inquiry link to "A" hangs on trying to open another dialog.

      Other links might be included as well. E.g. the back button on the screen doesn't work after the inquiry link has been used.

      Extend AFT to do two inquiries in sequence.

        Issue Links

          Activity

          Hide
          Kristina Taylor (Inactive) added a comment -

          Seems to have been caused by some temporary code added for KULRICE-8547. That issue expressed the need to not have Inquiry forms in the session, work that has not been done yet or even planned as far as I know. Until that work happens, we need to keep all inquiry forms in session. I'm hoping this does not affect performance, but if it does, at the very least we have achieved correct behavior and can attack the performance problem from a different angle.

          Show
          Kristina Taylor (Inactive) added a comment - Seems to have been caused by some temporary code added for KULRICE-8547 . That issue expressed the need to not have Inquiry forms in the session, work that has not been done yet or even planned as far as I know. Until that work happens, we need to keep all inquiry forms in session. I'm hoping this does not affect performance, but if it does, at the very least we have achieved correct behavior and can attack the performance problem from a different angle.
          Hide
          Daniel Seibert (Inactive) added a comment -

          Further testing shows the problem only occurs when performing nested inquiries (clicking an inquiry link from an existing inquiry view). The problem occurs because the original inquiry form is also removed from the UifFormManager when attempting to clear old inquiry views.

          Multiple inquiries from a maintenance screen, for example, don't exhibit the problem.

          Show
          Daniel Seibert (Inactive) added a comment - Further testing shows the problem only occurs when performing nested inquiries (clicking an inquiry link from an existing inquiry view). The problem occurs because the original inquiry form is also removed from the UifFormManager when attempting to clear old inquiry views. Multiple inquiries from a maintenance screen, for example, don't exhibit the problem.
          Hide
          Daniel Seibert (Inactive) added a comment -

          I did some performance analysis on the code prior to the fix and after applying the fix.
          Performance of the inquiry HTTP GET turnaround time showed minor improvement. (~300ms for Sub Account Inquiries on my localhost)
          Did not observe any significant heap space usage after fix.

          Show
          Daniel Seibert (Inactive) added a comment - I did some performance analysis on the code prior to the fix and after applying the fix. Performance of the inquiry HTTP GET turnaround time showed minor improvement. (~300ms for Sub Account Inquiries on my localhost) Did not observe any significant heap space usage after fix.
          Hide
          Daniel Seibert (Inactive) added a comment -

          Screenshots of network timing before and after applying fix.

          Show
          Daniel Seibert (Inactive) added a comment - Screenshots of network timing before and after applying fix.
          Hide
          Martin Taylor (Inactive) added a comment -

          Closing 2.5.1 Development

          Show
          Martin Taylor (Inactive) added a comment - Closing 2.5.1 Development

            People

            • Assignee:
              Kristina Taylor (Inactive)
              Reporter:
              Claus Niesen
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile

                  Structure Helper Panel