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

Add ability to return document attributes from WorkflowDocumentService.documentSearch(...) API

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-967Add ability to query workflow for document status via the API
      KULRICE-1153add api methods to identify all the places a given user appears in workflow, to remove a user from workflow, and to replace a user in workflow
      KULRICE-11468Add ability to remove mappings from superclass with JPA
      KULRICE-5697Add the ability to parameterize a ValuesFinder
      KULRICE-889New workflow API
      KULRICE-2689Add ability to create inquiry links for tab titles in tab.tag and tabTop.tag
      KULRICE-12353Add ability to change application document status from document operation screen
      KULRICE-7790KimTypeQualifierResolver should be returning the custom document type from handleGroupDocument()
      KULRICE-14200REST-ful api for document search
      KULRICE-6995Add support for "fluent" builders to Kuali Rice apis
    • Rice Module:
      KEW
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Currently, if a document has document attributes, they are only returned in the results if you pass the specific document type name to the document search that you want to search against. This seems like reasonable default behavior, but we should add an option which allows these values to be returned.

      See DocumentSearchCustomizerTest.testCustomizeResults() for a commented out section of code which was attempting to test this.

        Issue Links

          Activity

          Hide
          Jessica Coltrin (Inactive) added a comment -

          Moving all New Feature and Improvement Jiras out of 2.1 since the scope for those is now locked. These items move to the 2.x-backlog.

          Show
          Jessica Coltrin (Inactive) added a comment - Moving all New Feature and Improvement Jiras out of 2.1 since the scope for those is now locked. These items move to the 2.x-backlog.

            People

            • Assignee:
              Unassigned
              Reporter:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel