Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-1900

Problems deleting collection items in maintenance documents

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.3
    • Component/s: Development
    • Labels:
      None
    • Rice Module:
      KNS, KIM
    • Application Requirement:
      Rice

      Description

      Not sure if this should be split out into separate bugs, but these are all blockers b/c the product doesn't function properly.

      Within a "create" maintenance document:
      1.) When you add a bunch of collection items from a multi-line lookup, all come back appropriately with delete buttons; however, after you delete the first item in the collection, when the page reloads, the delete buttons for the remaining items go away and there's no way to delete them
      2.) If you try to reload the document from a SAVED state, the delete buttons are not there for the collection items
      3.) The same goes for sub-collections... though these don't use the multi-line lookup

      When "editing" a record using a maintenance document:
      1.) There is no way to delete an existing collection item, the delete button doesn't show up

      The pattern seems to be that when the post of the page happens, the delete buttons (if there were any) for all previously existing collection items disappear, while the newly added record, if there was one is the only element with the delete button. But if you post the page again for some reason other than for adding a new item to the collection, then all delete buttons disappear for all collection items disappear.

        Attachments

        1. Picture 2.png
          Picture 2.png
          85 kB
        2. Picture 3.png
          Picture 3.png
          59 kB
        3. Picture 4.png
          Picture 4.png
          65 kB
        4. Picture 5.png
          Picture 5.png
          45 kB

          Activity

          Hide
          agodert Aaron Godert (Inactive) added a comment -

          Thanks for looking into this Chris. I remember the discussion that we had about this back at CSU in January. Back to the drawing board.

          Show
          agodert Aaron Godert (Inactive) added a comment - Thanks for looking into this Chris. I remember the discussion that we had about this back at CSU in January. Back to the drawing board.
          Hide
          ckirschenman Chris Kirschenman (Inactive) added a comment -

          so Aaron did this work for you on group?
          At least case 1 under new should be fixed now (although you'll have to do the same for any other collections this is occuring too) 2&3 & 1 under edit are the ones that need the integration discussion

          Show
          ckirschenman Chris Kirschenman (Inactive) added a comment - so Aaron did this work for you on group? At least case 1 under new should be fixed now (although you'll have to do the same for any other collections this is occuring too) 2&3 & 1 under edit are the ones that need the integration discussion
          Hide
          ckirschenman Chris Kirschenman (Inactive) added a comment -

          oh and the fix was, add this to the collection dd

          <attributeReference name="newCollectionRecord"
          sourceClassName="org.kuali.core.bo.AttributeReferenceDummy"
          sourceAttributeName="newCollectionRecord" />

          and this to the maintenance dd

          <maintainableField name="newCollectionRecord" />

          Show
          ckirschenman Chris Kirschenman (Inactive) added a comment - oh and the fix was, add this to the collection dd <attributeReference name="newCollectionRecord" sourceClassName="org.kuali.core.bo.AttributeReferenceDummy" sourceAttributeName="newCollectionRecord" /> and this to the maintenance dd <maintainableField name="newCollectionRecord" />
          Hide
          ckirschenman Chris Kirschenman (Inactive) added a comment -

          committed my potential work around, it seemed to work to fix all of the above issues for me in limited testing. Try out group some more with the newest code and let me know what you think.

          Show
          ckirschenman Chris Kirschenman (Inactive) added a comment - committed my potential work around, it seemed to work to fix all of the above issues for me in limited testing. Try out group some more with the newest code and let me know what you think.
          Hide
          ckirschenman Chris Kirschenman (Inactive) added a comment -

          going to go ahead and close this for now. Feel free to reopen if you run into any related issues. I think there may be an existing jira out there for the overall KNS change so I'm going to search for that, otherwise I'll create it along with the integration issue (probably do that after work tonight)

          Show
          ckirschenman Chris Kirschenman (Inactive) added a comment - going to go ahead and close this for now. Feel free to reopen if you run into any related issues. I think there may be an existing jira out there for the overall KNS change so I'm going to search for that, otherwise I'll create it along with the integration issue (probably do that after work tonight)

            People

            • Assignee:
              ckirschenman Chris Kirschenman (Inactive)
              Reporter:
              agodert Aaron Godert (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: