Details

    • Type: Bug Fix Bug Fix
    • Status: Reopened Reopened
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.3.0-m2
    • Fix Version/s: Backlog
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-9475Unable to set class for a row of a collection group
      KULRICE-7851Dirty field indicator not working on Collections
      KULRICE-8087collection property "includeLineSelectionField" should ignore addLine row
      KULRICE-8001Checks not correctly cleared for dirty fields
      KULRICE-12079Allow for editing of collection rows via modal
      KULRICE-10043KRAD sample app Collection Features examples are not set up correctly
      KULRICE-9159Show/hide active rows on a collection doesn't work
      KULRICE-9838Collection Creates Extra Row
      KULRICE-7939Enhancement to CollectionGroup row selection
      KULRICE-1880can't set new collection record property on a copy
    • Rice Module:
      KRAD
    • Application Requirement:
      KS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      KRAD by default checks editable fields only and doesn't prompt the dialog to warn the user of unsaved changes when a row has been added to a collection but hasn't yet been persisted to the DB. setting the fields to dirty upon adding the row to the collection will cause these fields to be checked for unsaved changes.

        Issue Links

          Activity

          Hide
          Venkat PremChandran (Inactive) added a comment -

          sorry, I meant if the user deletes a row from the collection and tries to navigate away from the form without save, the user should be getting a similar message just like adding a row to the collection.

          Show
          Venkat PremChandran (Inactive) added a comment - sorry, I meant if the user deletes a row from the collection and tries to navigate away from the form without save, the user should be getting a similar message just like adding a row to the collection.
          Hide
          Larry Symms added a comment -

          I would imagine it would but both cases need to be tested

          Show
          Larry Symms added a comment - I would imagine it would but both cases need to be tested
          Hide
          Venkat PremChandran (Inactive) added a comment -

          yeah, but i think jquery plugin usually looks for some dirty css on the input fields. Not sure how rice handles the deletion

          Show
          Venkat PremChandran (Inactive) added a comment - yeah, but i think jquery plugin usually looks for some dirty css on the input fields. Not sure how rice handles the deletion
          Hide
          Venkat PremChandran (Inactive) added a comment -

          N/m I may be wrong, looks like we've dirtyForm flag at the form.

          Show
          Venkat PremChandran (Inactive) added a comment - N/m I may be wrong, looks like we've dirtyForm flag at the form.
          Hide
          Larry Symms added a comment -

          this cropped up again in 2.4

          Show
          Larry Symms added a comment - this cropped up again in 2.4

            People

            • Assignee:
              Unassigned
              Reporter:
              Larry Symms
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel