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

Person service does not handle extension objects properly


    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s:
    • Fix Version/s: 2.0
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-8684ActionRequestValue is not handling missing Person or Group objects
      KULRICE-5056Convert DocumentSearch objects and services to new model
      KULRICE-11414Extension framework does not work with objects using sequences for primary key
      KULRICE-11602Create extension points to override ExpressionEvaluator
      KULRICE-7392Another problem with EBOs - PBO.refresh() not handling them properly
      KULRICE-4291Person Inquiry not working for external implementations of Identity service. Need to update UiDocumentServiceImpl
      KULRICE-5349LookupForm does not serialize properly
      KULRICE-3801Fix the way that "empty" KIM objects are handled
      KULRICE-4025Direct inquiry does not work properly in some conditions
      KULRICE-9119Review design for extension framework in new data layer
    • Rice Module:
    • Application Requirement:
      KFS, Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      The person service has a problem resolving properties correctly when the person is an attribute on an extension object. KFS patched PersonServiceImpl to give special handling to the "extension" property.

      (Previously, it was resolving into strings like businessObjectName.extension.extension.person.principalId)


        No work has yet been logged on this issue.


          • Assignee:
            Emerson David (Inactive)
            Jonathan Keller
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel