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

Default values not getting applied for multi-pages

    Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.6
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-7072Default values are applied at the end of the view lifecycle so not seen by inquiry
      KULRICE-11891Default Values not being applied on Input and Data Fields
      KULRICE-12734Update default values to use a boolean variable rather than a list
      KULRICE-12507 Save action button should not be rendered by default, but gets rendered on ajax load
      KULRICE-5794Default values not working!
      KULRICE-3647some "default" fields are not correctly getting returned from the EntityInfo DTO
      KULRICE-5449Verify if these 1.0.3.2 fixes made it to 2.0 and if not, apply to 2.0 trunk
      KULRICE-13947KRAD read-only field values often get HTML-escaped twice
      KULRICE-9281default values for Oracle DATE and MySQL DATETIME columns are inconsistent
      KULRICE-10305Lookup: Set default values on "clear values"
    • Rice Team:
      Framework
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required

      Description

      I have successfully delayed page group copy to prevent all pages from being loaded. In order to accomplish this, I had to remove the following code from applyDefaultValues() – is there a use case that might have required this code? I tested with a few multi-page views and didn’t see an immediate issue.

      // if view, need to add all pages since only one will be on the lifecycle
      if (component instanceof View) {
      for (Component nested : ((View) component).getItems())

      { applyDefaultValues(nested); }

      }

      Apply default values is only done once (on the initial get). It sets a flag on the form to prevent defaults from being applied again. However, we only process the first page on the initial request, so the default values would only get applied for that page (and when the user navigated to one of the other pages it would not have its default values applied). Maybe we can change the logic to track application of default values by page? I’ll create a Jira to look into this further.

        Activity

        Hide
        Jerry Neal (Inactive) added a comment -

        General bug, moving to Claus

        Show
        Jerry Neal (Inactive) added a comment - General bug, moving to Claus

          People

          • Assignee:
            Unassigned
            Reporter:
            Jerry Neal (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

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

                Structure Helper Panel