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

Document the "routingVersion" element on DocumentType configuration


    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.9.2, KEW - 0.9.2
    • Component/s: None
    • Labels:
    • Similar issues:
      KULRICE-3912if configured to route to a split or join, and that node is "requests" type, it silently fails
      KULRICE-1993Create a reference guide for our Ingestable XML configuration (DocumentType, RuleAttribute, etc.)
      KULRICE-3331Document Types with role nodes inside a branch node of a split node cannot be exported and re-ingested without causing DocumentType schema errors
      KULRICE-2298Create and add KNS bootstrap document types to core Rice bootstrap
      KULRICE-849DocumentType default exception workgroup is not stored in database
      KULRICE-1960Make rules independent of document type
      KULRICE-4146OptimisticLockException exception when ingesting some kew files.
      KULRICE-6160Update Routing Components and Configuration Guide
      KULRICE-7434default email style refers to removed DocumentType property docHandlerUrl
      KULRICE-943Update workgroup documentation to include Workgroup types and configuration
    • Rice Module:


      Below is an email thread from the kuali-rice list:


      Hi Josh, I'll be sure this makes in into our documentation. Here's the explanation of routingVersion:

      This field exists for purposes of backward compatibility with older versions of KEW. Originally, KEW only supported sequential routing paths (as opposed to those with splits and joins). In the API, there is a method named "getDocRouteLevel()" this returns an integer which represents what the numerical "step" in the routing process is. This number only has any meaning in the case of documents that define sequential routing. A document with routingVersion of "1" will keep track of the route level number. A document with routingVersion of "2" (the default unless explicitly defined in the document type configuration) will not keep track of the route level number and (I believe) an exception will be thrown if code attempts to access that value.

      Additionally, if you attempt to define a route path with splits/joins and the routingVersion is set to "1" you will get an error when ingesting the DocumentType.

      Hope that gives you the answer you're looking for


      > ----Original Message----
      > From: kuali-rice@googlegroups.com kuali-rice@googlegroups.com On
      > Behalf Of Josh Peters (Illinois State University)
      > Sent: Friday, December 14, 2007 5:31 PM
      > To: Kuali Rice
      > Subject: [kuali-rice] routingVersion
      > Can someone kindly explain what routingVersion (in a Workflow XML
      > document representation) means? It's not documented on the wiki it
      > seems, and I've had an issue that required routingVersion to be 2
      > instead of 1.
      > Thanks in advance.
      > Josh


        Eric Westfall added a comment -

        Hi Aaron, thanks for putting this up on the Document TYpe page. Looks like it's done. Is this good to be closed?

        Eric Westfall added a comment - Hi Aaron, thanks for putting this up on the Document TYpe page. Looks like it's done. Is this good to be closed?


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


            • Created:

              Time Tracking

              Original Estimate - 30 minutes
              Time Spent - 5 minutes Remaining Estimate - 25 minutes
              Time Spent - 5 minutes Remaining Estimate - 25 minutes

                Structure Helper Panel