Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.3.0-m3, 2.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7996Progressive disclosure and refresh within table not working
      KULRICE-7754Progressive disclosure via ajax not working in Kitchen Sink
      KULRICE-8938problem with dropbox progressive disclosure in a lightbox
      KULRICE-10633Multiple problems with KRAD Kitchen Sink Progressive Disclosure
      KULRICE-11902Library - Client Responsiveness - Progressive Disclosure - Ajax Retrieval does not work - Field does not show up
      KULRICE-11158Progressive disclosure and label condition doesn’t work for lookup view
      KULRICE-8455Message for progressive disclosure appearing as 'null'
      KULRICE-6340ajax progressive disclosure / refresh are broken
      KULRICE-7550Fix progressive disclosure highlight animation styling
      KULRICE-6568Progressive Disclosure server side improvements
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      UIF Component
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Progressive disclosure is not currently working. No errors are seen, the content just doesn't display. Maybe an issue related to JS refactoring?

        Activity

        Hide
        Brian Smith (Inactive) added a comment -

        This is not related to the js. The fix was to force the expression evaluator to use the correct model in apply model of component base, why this no longer contains the correct model is another question entirely and feels like a bug, can you let me know if you think you might know the answer to this? For now this particular bug is fixed though.

        Show
        Brian Smith (Inactive) added a comment - This is not related to the js. The fix was to force the expression evaluator to use the correct model in apply model of component base, why this no longer contains the correct model is another question entirely and feels like a bug, can you let me know if you think you might know the answer to this? For now this particular bug is fixed though.
        Hide
        Jerry Neal (Inactive) added a comment -

        Ah yes, this is due to the expression evaluator rework. Actually we should probably initialize the model in the run component lifecycle method. I'll make the adjustment. Thanks for looking into this

        Show
        Jerry Neal (Inactive) added a comment - Ah yes, this is due to the expression evaluator rework. Actually we should probably initialize the model in the run component lifecycle method. I'll make the adjustment. Thanks for looking into this

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel