Details

    • Type: Task Task
    • 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-1432Services that are overridden in institutional plugin cannot be properly exported to the bus
      KULRICE-13870BindExceptions being thrown when they shouldn't be
      KULRICE-12588New Sticky header problems with top margin of view
      KULRICE-1431When the user/workgroup service is overridden in a plugin, the non-overridden version is exported to the service bus
      KULRICE-752Acknowledgments are being sent to the Initiator, even if the initiator is the one who disapproves the document
      KULRICE-11641Content wrapper classes not getting applied to view header
      KULRICE-2210Fix location of document header population
      KULRICE-10882Read only property on collection items gets overridden
      KULRICE-7493Action list filter not being applied until after refresh
      KULRICE-4125Apply ECL headers to new files in the 1.0.2 relesae
    • Rice Team:
      Middleware
    • Rice Module:
      KRAD
    • Sprint:
      Middleware 2.5.1 Sprint 3, Middleware 2.5.2 Sprint 1, Middleware 2.5.2 Sprint 2, Middleware 2.5.2 Sprint 3
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes
    • Story Points:
      5

      Description

      Yesterday, Gayathri from KC brought to light a weird layout issue that they were having in relation to my commits to KULRICE-13163. I have since patched it for them with something that is equally good (not a hack) so we're not concerned too much with that but more in why we had to patch it. I've included the patch that will cause the issue.

      What KC is doing is that they will take our transactional document view and override the header with a header with box sections, implying a box layout. Normally, the header of the transactional document is a grid and thus has a certain number of columns. This was assumed to be true when implementing KULRICE-13163 which adds another column when copying a document. However, when KC overrides this with their box based header, the two layout managers seem to want to merge. Suddenly, KRAD will try to evaluate and set numberOfColumns="@{document.documentHeader.documentTemplateNumber == null ? 4 : 6}" on a box layout. KC's code is at

      https://github.com/kuali/kc/blob/master/coeus-impl/src/main/resources/org/kuali/coeus/propdev/impl/core/ProposalDocumentView.xml

      We both have no idea why this is happening since the two Spring beans have really nothing to do with each other.

        Activity

        Hide
        Kristina Taylor (Inactive) added a comment -

        From Jerry:

        My guess is the expression is not getting cleared properly. The bean processor pulls these out into separate map properties, and then they get picked up later and evaluated. Must be some bug in that logic.

        Show
        Kristina Taylor (Inactive) added a comment - From Jerry: My guess is the expression is not getting cleared properly. The bean processor pulls these out into separate map properties, and then they get picked up later and evaluated. Must be some bug in that logic.
        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:
            Kristina Taylor (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Agile

                Structure Helper Panel