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

Rice Dev: Person and Group Maintenance documents not saving edits?

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-rc1, 2.0
    • Component/s: Unit Testing
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Environment:
      RiceDev
    • Similar issues:
      KULRICE-5550Rice Dev: Group or Role lookup not returning values on Create Person
      KULRICE-8542Person, role & group docs should not allow multiple docs editing the same record to be saved at the same time
      KULRICE-5729Rice Dev: Group Lookup from Role maintenance document bomb to error
      KULRICE-13255KNS Maintenance Documents display Save button after a document submitted.
      KULRICE-5478Rice Dev: KRAD Travel Account Maintenance (edit) error
      KULRICE-11091AFT Failure: Stacktrace when creating person or group - PersistenceService invoked for non-legacy class: class java.lang.Class in Person and Group
      KULRICE-4677Person/Group/Role/Permission/Responsibility update screen Save/Submit enhancements
      KULRICE-11931Routing Rule Maintenance - JPA Duplicate Key Exception when saving edits
      KULRICE-4609Close/Cancel/Save button does not work correctly for Kim maintenance screens
      KULRICE-5851Rice Dev: Rice Maintenance documents bombing out to exception
    • Rice Module:
      KIM
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      I can't see the DB so I'm not sure if the data's actually there or not, but I added a new person and added a primary and preferred name type, but in the Person lookup results it's showing Xxxx,xxxx in the name field (in fact any new persons not part of the sample data are showing this way). Looking at the person inquiry screen there's no preferred name listed. Did a maintain person adding the preferred name, but same thing X's and no preferred shown.

      So in the end, it appears that preferred name type is not being saved or it's not being referenced properly.

      Actually it's not just name. If you go and maintain a person, after the doc is final, the inquiry doesn't reflect the changes (address, email, name, phone).

      Group is doing the same thing, you can add a person, but it doesn't stick when you go back to look at the group.

      1. addingName.png
        52 kB
      2. inquiry.png
        141 kB
      3. saearchResults.png
        40 kB
      4. Screen Shot 2012-01-09 at 11.49.46 AM.png
        12 kB

        Activity

        Hide
        Rice-CI User (Inactive) added a comment -

        Integrated in rice-trunk-nightly #249 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/249/)
        KULRICE-5924 - kim person, group, role documents not showing with new values after an edit.

        Show
        Rice-CI User (Inactive) added a comment - Integrated in rice-trunk-nightly #249 (See http://ci.rice.kuali.org/job/rice-trunk-nightly/249/ ) KULRICE-5924 - kim person, group, role documents not showing with new values after an edit.
        Hide
        Matt Sargent added a comment -

        this one's looking good

        Show
        Matt Sargent added a comment - this one's looking good
        Hide
        Matt Sargent added a comment -

        This looks to be happening again today. I added a new person and the person inquiry only shows XXXX's for the name (see updated shot)

        Show
        Matt Sargent added a comment - This looks to be happening again today. I added a new person and the person inquiry only shows XXXX's for the name (see updated shot)
        Hide
        Jeremy Hanson added a comment -

        That looks like a masking due to privacy preferences (which I see are not set for the user). Something is probably messed up with the display...

        Matt, when you go back into the edit screen is the data updated?

        Show
        Jeremy Hanson added a comment - That looks like a masking due to privacy preferences (which I see are not set for the user). Something is probably messed up with the display... Matt, when you go back into the edit screen is the data updated?
        Hide
        Jeremy Hanson added a comment -

        resolved again. this was a problem with caching again. The configuration work disabled the cache flush annotations on the UIDocumentService.

        Show
        Jeremy Hanson added a comment - resolved again. this was a problem with caching again. The configuration work disabled the cache flush annotations on the UIDocumentService.
        Hide
        Matt Sargent added a comment -

        Looks good now...thanks!

        Show
        Matt Sargent added a comment - Looks good now...thanks!
        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:
            Jeremy Hanson
            Reporter:
            Matt Sargent
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel