Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.1.1
    • Fix Version/s: 1.0.3
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-10394Clear data for fields when disabled
      KULRICE-8001Checks not correctly cleared for dirty fields
      KULRICE-13994Copy maintenance function needs option to copy readOnly fields
      KULRICE-13729Create a smoke test to verify that secure fields are automatically cleared out on BO copy.
      KULRICE-2101Log4j MDC user is not cleared
      KULRICE-3072Allow maintenance documents to copy PK fields
      KULRICE-7011Work on adding form clearing point on user exit
      KULRICE-4280RELOAD_ACTION_LIST user options not getting deleted on first load of Action List
      KULRICE-4766Allow configuration of fields that should be cleared on maintenance copy action
      KULRICE-8203Doc Search does not clear Document Status
    • Rice Module:
      Rice Core
    • Application Requirement:
      KFS
    • KTI Review Status:
      Review Completed

      Description

      When we have a user maintenance field that is optional and the name field is cleared out in the UI, the actual principal id is not cleared in the business object.

      Ex. Making account supervisor optional on account maintenance document

        Issue Links

          Activity

          Hide
          Geoff McGregor added a comment -

          In KC we only use renderOtherFields=true, so from our perspective it doesn't matter. Though I don't know why anyone would want to specify renderOtherFields=false.

          Show
          Geoff McGregor added a comment - In KC we only use renderOtherFields=true, so from our perspective it doesn't matter. Though I don't know why anyone would want to specify renderOtherFields=false.
          Hide
          Jeremy Hanson added a comment -

          Jonathon, is the change to user.tag needed? Sounds like the renderOtherFields param could stand to be removed...

          Show
          Jeremy Hanson added a comment - Jonathon, is the change to user.tag needed? Sounds like the renderOtherFields param could stand to be removed...
          Hide
          Jonathan Keller added a comment -

          I think that renderOtherFields gets set to false when the field is read only (which is what was causing the problem in the first place.) I'm fine with removing the attribute altogether. However - if you remove the attribute's existence, I think it will become an impacting change as I can see a number of places in the KFS JSP/tag files which specify that attribute. But...this is the time to clean things up - so I'm fine with it if you remove it.

          FYI: here are the places in Rice that I see it used:

          ./work/web-root/kew/WEB-INF/jsp/AppSpecificRoute.jsp:59: userName="$

          {KewRoutingKualiForm.appSpecificRouteRecipient.namespaceCode}

          " readOnly="$

          {displayReadOnly}

          " renderOtherFields="true"
          ./work/web-root/WEB-INF/tags/kr/adHocRecipients.tag:73: renderOtherFields="true"
          ./work/web-root/WEB-INF/tags/kr/adHocRecipients.tag:101: renderOtherFields="true"
          ./work/web-root/WEB-INF/tags/kr/notes.tag:195: renderOtherFields="true"
          ./work/web-root/WEB-INF/tags/kr/rowDisplay.tag:625: renderOtherFields="true"

          Show
          Jonathan Keller added a comment - I think that renderOtherFields gets set to false when the field is read only (which is what was causing the problem in the first place.) I'm fine with removing the attribute altogether. However - if you remove the attribute's existence, I think it will become an impacting change as I can see a number of places in the KFS JSP/tag files which specify that attribute. But...this is the time to clean things up - so I'm fine with it if you remove it. FYI: here are the places in Rice that I see it used: ./work/web-root/kew/WEB-INF/jsp/AppSpecificRoute.jsp:59: userName="$ {KewRoutingKualiForm.appSpecificRouteRecipient.namespaceCode} " readOnly="$ {displayReadOnly} " renderOtherFields="true" ./work/web-root/WEB-INF/tags/kr/adHocRecipients.tag:73: renderOtherFields="true" ./work/web-root/WEB-INF/tags/kr/adHocRecipients.tag:101: renderOtherFields="true" ./work/web-root/WEB-INF/tags/kr/notes.tag:195: renderOtherFields="true" ./work/web-root/WEB-INF/tags/kr/rowDisplay.tag:625: renderOtherFields="true"
          Hide
          Jeremy Hanson added a comment -

          I have removed the renderOtherFields attribute from user.tag. This jira should be complete other than documentation and letting people know this is an impacting change.

          Show
          Jeremy Hanson added a comment - I have removed the renderOtherFields attribute from user.tag. This jira should be complete other than documentation and letting people know this is an impacting change.
          Hide
          Eric Westfall added a comment -

          This was originally marked as "pending kti review" but I don't recall us ever doing a review in the meeting. However, i think the various impacted parties have weighed in on the jira here and it looks like the solution just removes something which is unneeded. So I went ahead and set KTI review status to "review completed".

          Show
          Eric Westfall added a comment - This was originally marked as "pending kti review" but I don't recall us ever doing a review in the meeting. However, i think the various impacted parties have weighed in on the jira here and it looks like the solution just removes something which is unneeded. So I went ahead and set KTI review status to "review completed".

            People

            • Assignee:
              Jeremy Hanson
              Reporter:
              Dan Lemus (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 5 hours
                5h
                Remaining:
                Remaining Estimate - 5 hours
                5h
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel