Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.1, KFS Release 3.0
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-3486Add methods to Identity services to retrieve full entity data
      KULRICE-2677Add full entity DTO versions of getEntity methods to IdentityService and IdentityManagementService
      KULRICE-2221Add Methods to IdentityManagementService to indicate editability of various components
      KULRICE-13189modify KRMS' published apis so that update methods return the updated object
      KULRICE-11728modify KRMS CRUD apis so that update methods return the updated object
      KULRICE-7785Role member update API not updating existing role member attribute records (inserting new ones)
      KULRICE-6984Role Delegate APIs are not granular enough
      KULRICE-3270Add an API method for placing a document into exception routing
      KULRICE-3714Update PermissionService API with a method to check multiple permissions at once
      KULRICE-14110JPA Performance of Referenced Entity (Child Data Objects) - KRMS
    • Rice Module:
      KIM
    • Application Requirement:
      Rice

      Description

      The KIM Identity service needs methods to update entity data.

      When designing the APIs, there should be a way to make incremental updates. That is, the client should not need to load the entire entity data set, modify it, and then send the entire record back.

      There should be operations like "add phone number", "Update address", "remove name"

      Perhaps an operation code (ADD/UPDATE/DELETE/INACTIVATE) and some simple DTO objects representing the single name/address/phone/etc... data?

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment - - edited

          Linked in to the roadmap item that represents this. Unfortunately, at the present time it's not scheduled until Rice 2.0 which won't be for another 2-3 years I don't think we can realistically go that long without adding these update operations but that's the way things were prioritized. We'll either need to try and escalate the priority of this via the roadmap committees or see if we can get some additional resources to work on this.

          Show
          Eric Westfall added a comment - - edited Linked in to the roadmap item that represents this. Unfortunately, at the present time it's not scheduled until Rice 2.0 which won't be for another 2-3 years I don't think we can realistically go that long without adding these update operations but that's the way things were prioritized. We'll either need to try and escalate the priority of this via the roadmap committees or see if we can get some additional resources to work on this.
          Hide
          Jonathan Keller added a comment -

          I figured it would be needed at some time. This came out of a conversation with someone at Kuali Days, not on any immediate need. I just wanted to record the concerns that were raised.

          Show
          Jonathan Keller added a comment - I figured it would be needed at some time. This came out of a conversation with someone at Kuali Days, not on any immediate need. I just wanted to record the concerns that were raised.

            People

            • Assignee:
              Unassigned
              Reporter:
              Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel