• Type: Sub Task Sub Task
    • Status: Open Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-3423in Parameter Lookup, the Component field direct inquiry doesn't work
      KULRICE-4025Direct inquiry does not work properly in some conditions
      KULRICE-6426Rice Dev: Initiator direct Inquiry from Document Search throwing HTTP 500 Error
      KULRICE-3426in Responsibility lookup, none of the field direct inquiry image links work
      KULRICE-1579Direct inquiry links do not work on maintenance documents
      KULRICE-5317Lookup causes null error when building an inquiry link for a foreign key
      KULRICE-2270issues with direct inquiries
      KULRICE-12547Direct inquiry renders including properties not present on the view
      KULRICE-5687Rice Dev: Direct Inquiry throwing Invalid path from all lookups
      KULRICE-6453Rice Dev: PeopleFlow Maintenance Screen throwing error on Direct Inquiry
    • Rice Module:


      A direct inquiry takes the value in an HTML form input and uses that value to pull up details on the object represented by that value. For example, given a Document Type lookup form, and a Parent Name field within that form, a direct inquiry on this field would take the value provided by the user (the name of the document type's parent), query the DB and display an inquiry form describing the parent document type.

      Currently, this results in an error when the field does not correspond to the PK of the relevant business object (ie the object that is the subject of the lookup). The primary key for the business object in question needs to present in the HTTP request. See the populatePKFieldValues method of the InquiryForm class.

      Attempting to trick the system by changing either the source or target to documentTypeId results in an error during validation of the BO by the data dictionary (a type comparison is conducted and, given that the identifier is a Long and the document type name is a String, it fails). See the completeValidation method in the PrimitiveAttributeDefinition class.

        Issue Links


          There are no comments yet on this issue.


            • Assignee:
              Casey Boettcher (Inactive)
            • Votes:
              0 Vote for this issue
              0 Start watching this issue


              • Created:

                Structure Helper Panel