Details

    • Type: Sub Task Sub Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-b1, 2.0
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-7590Support for progressive disclosure and component refresh on content elements
      KULRICE-12543Support progressive disclosure and refresh of collection lines
      KULRICE-9672Progressive disclosure not working
      KULRICE-7996Progressive disclosure and refresh within table not working
      KULRICE-8455Message for progressive disclosure appearing as 'null'
      KULRICE-7754Progressive disclosure via ajax not working in Kitchen Sink
      KULRICE-8938problem with dropbox progressive disclosure in a lightbox
      KULRICE-6340ajax progressive disclosure / refresh are broken
      KULRICE-7550Fix progressive disclosure highlight animation styling
      KULRICE-6568Progressive Disclosure server side improvements
    • Rice Module:
      KRAD
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Provide the ability to show/hide a group of fields based on data.

        Issue Links

          Activity

          Hide
          Brian Smith (Inactive) added a comment - - edited

          Progressive disclosure is implemented for Groups and Fields. Does not work with collections. Both refresh and progressive show/hide options are available. Both pure server request and client side only progressive disclosure options are available. Requiredness indicators dynamically appear based on constraint configuration - but need some additional tweaks. For details of all the configuration options, of which there are MANY, see ComponentBase javadoc documentation.

          Show
          Brian Smith (Inactive) added a comment - - edited Progressive disclosure is implemented for Groups and Fields. Does not work with collections. Both refresh and progressive show/hide options are available. Both pure server request and client side only progressive disclosure options are available. Requiredness indicators dynamically appear based on constraint configuration - but need some additional tweaks. For details of all the configuration options, of which there are MANY, see ComponentBase javadoc documentation.
          Hide
          Rice-CI User (Inactive) added a comment -

          Integrated in rice-trunk-nightly #84 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/84/)
          KULRICE-4711 Added support for collections

          Show
          Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #84 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/84/ ) KULRICE-4711 Added support for collections
          Hide
          Rice-CI User (Inactive) added a comment -

          Integrated in rice-trunk-nightly #105 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/105/)
          KULRICE-4711 Progressive disclosure (through ajax and client) and refresh support on collection fields and groups, support for empty function in refresh/progressive statements, improvements to statement parser, component id fixes and tweaks

          Show
          Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #105 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/105/ ) KULRICE-4711 Progressive disclosure (through ajax and client) and refresh support on collection fields and groups, support for empty function in refresh/progressive statements, improvements to statement parser, component id fixes and tweaks
          Hide
          Brian Smith (Inactive) added a comment -

          Most is done ui wise, but still missing a few things:
          we need to figure out how to provide hooks to change a component that is refreshed as needed when it is refreshed (ie you change a selection that refreshes a component, but that component needs to update is options - say if that component is a drop down - no easy way to do this)
          server still takes in fields that are not shown, we arent doing the process to remove them from the data on the server

          Show
          Brian Smith (Inactive) added a comment - Most is done ui wise, but still missing a few things: we need to figure out how to provide hooks to change a component that is refreshed as needed when it is refreshed (ie you change a selection that refreshes a component, but that component needs to update is options - say if that component is a drop down - no easy way to do this) server still takes in fields that are not shown, we arent doing the process to remove them from the data on the server
          Hide
          Jessica Coltrin (Inactive) added a comment -

          This has been resolved

          Show
          Jessica Coltrin (Inactive) added a comment - This has been resolved
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Closing since these items are now in the release notes.

          Show
          Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

            People

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

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Structure Helper Panel