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

Rice Dev1: Document Type Inquiry Screen not Exporting Route Node Information

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.1
    • Fix Version/s: 2.1.0-m2, 2.1
    • Component/s: HTTP Unit Testing
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Environment:
      dev1, dev2
    • Similar issues:
      KULRICE-2781Create a way to visually display a routing process from a Document Type inquiry
      KULRICE-7037Rice Dev1: Group Inquiry Screen not fully rendering
      KULRICE-2057RouteNode content fragment is not being exported during Document Type XML export
      KULRICE-3379Inquiry links from KEW Route Log to "Document Configuration View" to KEW Document Type Inquiry page shows invalid KEW Document Type Inquiry for document instance
      KULRICE-2059When exporting Document Type using custom nodes, exporter attempts to load the node's Java class
      KULRICE-6620Role Inquiry does not contain the information present in Rice 1.x
      KULRICE-6700Rice Dev1: Error on Group and Role Inquiry when using Pagination Links
      KULRICE-2297Add "Export Hierarchy" button to Document Type inquiry when converting it to KNS
      KULRICE-11969Cannot perform detailed document searches that specify a doc type lacking route nodes
      KULRICE-1937When exporting Document Types with custom nodes, some come out with <requestActivation> instead of <simple>
    • Rice Module:
      KNS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      As an example if you do a document type search for "IdentityManagementRoleDocument" and click the xml link at the bottom of the page you get the route node and route path information in the XML export. However if you click on the document type id to take you to the inquiry view of the document type and then click the export button, the xml is missing the route node and route path information. See the attached files for example

      1. fromInquiry.xml
        0.7 kB
        Matt Sargent
      2. fromSearch.xml
        1 kB
        Matt Sargent

        Activity

        Hide
        Matt Sargent added a comment -

        this is fixed in 2.0.1, once that's merged into 2.1 we should be good.

        Show
        Matt Sargent added a comment - this is fixed in 2.0.1, once that's merged into 2.1 we should be good.

          People

          • Assignee:
            Unassigned
            Reporter:
            Matt Sargent
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel