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

modify KRMS' published apis so that update methods return the updated object

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 2.4
    • Fix Version/s: 3.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-11728modify KRMS CRUD apis so that update methods return the updated object
      KULRICE-3727Add API methods for updating of entity data
      KULRICE-3714Update PermissionService API with a method to check multiple permissions at once
      KULRICE-14117Update publisher jobs to notify developers involved rather than qa
      KULRICE-6423Complete JavaDocs for functional areas: Contexts, Exec Results, KRMS Types
      KULRICE-6980KIM update API not allowing updates unless version number is passed
      KULRICE-2431Extend Global Maintenance Impl to return the primary bo's class
      KULRICE-5645Update Kim service update methods where there are collections in object graph
      KULRICE-6036Update KRMS information in Release Notes
      KULRICE-9577Update the KRMS Guide
    • Rice Module:
      KRMS
    • Application Requirement:
      Rice
    • Sprint:
      Core 2.5.0-m6 Sprint 2, Core 2.5.0-m7 Sprint 1
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes
    • Story Points:
      5

      Description

      A flaw with the KRMS "BO services" is that the update methods don't return the updated object. The main issue here is that the caller won't get the incremented version number, so subsequent updates won't be possible without re-fetching. We should change all such methods to return the updated version of the object.

      The cloned-from issue here did work in this area, but we weren't able to push it all the way out to the published APIs for version compatibility reasons. For 3.0, we should make this changes at that layer.

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              Peter Giles (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Agile

                  Structure Helper Panel