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

Supress inquiry links on inquiry view if they point to the same view

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.4
    • Component/s: Development, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-12388Supress inquiry links on inquiry view if they point to the same view
      KULRICE-9977Inquiry links broken/point to the same inqury - copy fix
      KULRICE-7873Optionally supress the view in breadcrumbs
      KULRICE-12392KRMS Agenda Inquiry View: problems with “View Rule” button.
      KULRICE-8394Direct Inquiry view not working properly
      KULRICE-11531Inquiry with Component Security brings up wrong example
      KULRICE-11167KRAD Conversion Script: Remove Lookup and Inquiry View Name
      KULRICE-7917inquiry link on related object opens a lookup
      KULRICE-6374Hidden fields not rendering on Inquiry Views
      KULRICE-9667Inquiry Views with Uif-Page broken
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Inquiry
    • Sprint:
      2.4.0-m2 KRAD Sprint 4
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Currently inquiry links are rendered on inquiry views regardless wether or not it links to the same view. Thus a user can recursively inquire the same object through a view, unless this feature is manually disabled via the fieldInquiry.render property.

      This seems like a needles thing for the developer to do. It should be possible to detect if the inquiry link points to the same data object and if it is not to render the inquiry link.

        Issue Links

          Activity

          Hide
          Jeff Ruch added a comment -

          Thought it was my environment but now realize that submitting new documents into PeopleFlow in 2.4 is causing errors. 2.3 works OK, but the inquiry doesn't show the recursive link. Fortunately eDocLite does work and shows the recursive link (although no breadcrumb). I will use that as my test to fix against.

          Show
          Jeff Ruch added a comment - Thought it was my environment but now realize that submitting new documents into PeopleFlow in 2.4 is causing errors. 2.3 works OK, but the inquiry doesn't show the recursive link. Fortunately eDocLite does work and shows the recursive link (although no breadcrumb). I will use that as my test to fix against.
          Hide
          Jeff Ruch added a comment -

          OK, eDocLite is still using struts, so not applicable. Tried krms and travel account inquiries. Neither have recursive links. I'm thinking this maybe already fixed in KRAD.

          Show
          Jeff Ruch added a comment - OK, eDocLite is still using struts, so not applicable. Tried krms and travel account inquiries. Neither have recursive links. I'm thinking this maybe already fixed in KRAD.
          Hide
          Jeff Ruch added a comment -

          Confirmed that the PeopleFlow Inquiry on 2.3 does not show a recursive link either.

          Show
          Jeff Ruch added a comment - Confirmed that the PeopleFlow Inquiry on 2.3 does not show a recursive link either.
          Hide
          Jeff Ruch added a comment -

          Found a recursive link in kitchen sink under lookups. Had to go into 2.3 because of error in 2.4.

          Show
          Jeff Ruch added a comment - Found a recursive link in kitchen sink under lookups. Had to go into 2.3 because of error in 2.4.
          Hide
          Jeff Ruch added a comment -

          Added functionality so that if the field exists in the Inquiry's request parameter, the field won't be rendered as an inquiry link. There is still the possibility of recursive links. For example, on the travel account app, click on A2, then A14, then A2, then A14.

          Show
          Jeff Ruch added a comment - Added functionality so that if the field exists in the Inquiry's request parameter, the field won't be rendered as an inquiry link. There is still the possibility of recursive links. For example, on the travel account app, click on A2, then A14, then A2, then A14.
          Hide
          Jeff Ruch added a comment -

          Updated inquiry.java so that RICE skips creating the inquiry link if the field exists in the request parameters.

          Show
          Jeff Ruch added a comment - Updated inquiry.java so that RICE skips creating the inquiry link if the field exists in the request parameters.

            People

            • Assignee:
              Jeff Ruch
              Reporter:
              Claus Niesen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day, 4 hours Original Estimate - 1 day, 4 hours
                1d 4h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days
                2d

                  Agile

                    Structure Helper Panel