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

Create new Responsibility Route Name Node has no front or back end validation.


    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.3.0-m1, 2.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-1877Simulation Engine has a bug when using Node Name or Rule Template Name criteria and doing report by Route Header Id
      KULRICE-1764Document Search does not return all valid results when using a Route Node Name criteria on Detailed Search
      KULRICE-12129Error creating a new Responsibility
      KULRICE-8538Responsibility Required routing flag not working unless responsibility defined for exact document
      KULRICE-3761Refactor XPathQualifierResolver so that it may also be used as a Role route node/module
      KULRICE-12411Unable to edit responsibilities
      KULRICE-6950Severe performance degradation on saving complex routing paths
      KULRICE-7238Routing Rules Delegation Create New Screen: No lookup for namespace or name in Groups section
      KULRICE-2134Document Searching by Route Node is incorrect since change to search using Route Node Name instead of Route Node Id
      KULRICE-11969Cannot perform detailed document searches that specify a doc type lacking route nodes
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:


      Admin -> Responsibility -> Create new -> Enter garbage as Route Name Node and submit. Lookup Responsibilities and see that the responsibilty was created with a nonexistent route name node.


        There are no comments yet on this issue.


          • Assignee:
            Erik Meade
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel