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

Person, role & group docs should not allow multiple docs editing the same record to be saved at the same time

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 2.1.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KIM
    • Application Requirement:
      KFS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      KFS maintenance docs don't allow you to have more than one doc affecting a record saved our enroute. Rice docs should have the same locking mechanism in place. The person doc allows multiple docs to be in saved status affecting the same person.

        Attachments

          Issue Links

            Activity

            Hide
            jcoltrin Jessica Coltrin (Inactive) added a comment -

            setting to 2.1.3 for DM review.

            Show
            jcoltrin Jessica Coltrin (Inactive) added a comment - setting to 2.1.3 for DM review.
            Hide
            cniesen Claus Niesen added a comment -

            I think there are a few inconsistencies in regards to preventing a document be altered if a saved version exists.

            Following behavior has been observed:

            KRMS Agenda Editor - last submission overrides
              Edited agenda (changed name), save
              Edited agenda (changed campus), submit
              Open saved agenda, submit
              -> name change presisted, campus was reset to original
            
            KRMS Context - error
              Edited context (changed name), save
              Edited context (changed description), submit
              Open saved context, submit
              -> Error: This document cannot be Saved or Routed because a record with the same primary key already exists.
              
            People Flow - error
              Edited people flow (changed name), save
              Edited people flow (changed description), submit
              Open saved people flow, submit
              -> Error: This document cannot be Saved or Routed because a record with the same primary key already exists.
            
            Campus - error
              Edited campus (changed name), save
              Edited campus (changed short name), submit
              Open saved campus, submit
              -> Error: This document cannot be Saved or Routed because a record with the same primary key already exists.
            
            Person - last submission overrides
              Edited person (changed principal name), save
              Edited person (changed active indicator), blanket approve
              Open saved person, blanket approve
              -> principal name change presisted, active indicator reset to original
            
            Person - both affiliation added
              Added affiliation, save
              Added different affiliation, blanket approve
              Open saved person, blanket approve
              -> both affiliations are added
              
            Person - last submission overrides
              Change affiliation (A) to new affiliation (B), save
              Change affiliation (A) to new affiliation (C), blanket approve
              open saved person, blanket approve
              -> the affiliation (C) overrides (B)
            

            Do we have documentation how multiple separate document changes should be handled?

            Show
            cniesen Claus Niesen added a comment - I think there are a few inconsistencies in regards to preventing a document be altered if a saved version exists. Following behavior has been observed: KRMS Agenda Editor - last submission overrides Edited agenda (changed name), save Edited agenda (changed campus), submit Open saved agenda, submit -> name change presisted, campus was reset to original KRMS Context - error Edited context (changed name), save Edited context (changed description), submit Open saved context, submit -> Error: This document cannot be Saved or Routed because a record with the same primary key already exists. People Flow - error Edited people flow (changed name), save Edited people flow (changed description), submit Open saved people flow, submit -> Error: This document cannot be Saved or Routed because a record with the same primary key already exists. Campus - error Edited campus (changed name), save Edited campus (changed short name), submit Open saved campus, submit -> Error: This document cannot be Saved or Routed because a record with the same primary key already exists. Person - last submission overrides Edited person (changed principal name), save Edited person (changed active indicator), blanket approve Open saved person, blanket approve -> principal name change presisted, active indicator reset to original Person - both affiliation added Added affiliation, save Added different affiliation, blanket approve Open saved person, blanket approve -> both affiliations are added Person - last submission overrides Change affiliation (A) to new affiliation (B), save Change affiliation (A) to new affiliation (C), blanket approve open saved person, blanket approve -> the affiliation (C) overrides (B) Do we have documentation how multiple separate document changes should be handled?
            Hide
            cniesen Claus Niesen added a comment -

            The KIM screens are transactional documents. KNS requires custom locking code to be added to transactional documents. Since we will be converting these screens to KRAD Maintenance documents soon (Rice 2.3) we will be addressing the locking issue then.

            Show
            cniesen Claus Niesen added a comment - The KIM screens are transactional documents. KNS requires custom locking code to be added to transactional documents. Since we will be converting these screens to KRAD Maintenance documents soon (Rice 2.3) we will be addressing the locking issue then.

              People

              • Assignee:
                cniesen Claus Niesen
                Reporter:
                bsutton Barb Sutton
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: