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

UnexpectedRollbackException when using breadcrumb to go back to Agenda Editor from adding a rule

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.1
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-9454Enable breadcrumbs in the Agenda editor
      KULRICE-5354Agenda Editor only functions after ReloadingDataDictionary reloads
      KULRICE-6301Agenda Breadcrumbs don't show until the refresh button is clicked.
      KULRICE-13320KRMS agenda editor UI handles '>' operator badly
      KULRICE-5933Error saving a newly created agenda with a new rule.
      KULRICE-10020Cannot copy a rule right after the agenda is created
      KULRICE-8584Going back to a lookup from an inquiry with breadcrumbs throws exception
      KULRICE-13961Fill AFT Gap: KRMS Rules - Agenda Editor (Copy Rule)
      KULRICE-13204Agenda Editor - Editing a Rule: Hidden ids are being displayed as labels
      KULRICE-13889Fill AFT Gap: KRMS Rules - Agenda Editor (AND/OR toggle sync)
    • Rice Module:
      KRMS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      From the rule editing screen, if the breadcrumb allows you to click the Agenda Editor link, doing so results in an UnexpectedRollbackException.

      To get the breadcrumb to display that segment, you may need to hit the 'refresh' button on the rule editing tool bar.

        Issue Links

          Activity

          Hide
          Jessica Coltrin (Inactive) added a comment -

          setting fix version to 2.2 since it's not critical or blocker

          Show
          Jessica Coltrin (Inactive) added a comment - setting fix version to 2.2 since it's not critical or blocker
          Hide
          Sona Sona (Inactive) added a comment - - edited

          I was not able to get the UnexpectedRollbackException that is mentioned in the jira. I was however getting three other exceptions which were causing it to blow up
          1. ArrayIndexOutofBounds exception at History.buildHistoryFromParameterString()

          pushToHistory(params[0], params[1], params[2], params[3], params[4]);
          

          2. NullPointerExeption at AgendaEditorMaintainable.retrieveTermParameters()

          Tree<RuleTreeNode, String> propositionTree = rule.getPropositionTree();
          

          3.ExceptionEvaluationError at ExpressionEvaluatorServiceImpl.evaluateExpression() because it was retaining the pageId from the EditRule page.

          Expression expression = parser.parseExpression(expressionStr);
          

          I have added a fix for each of these and will create a review for it. Breadcrumbs on the Agenda Editor are no longer blowing up and it takes you back to the AgendaEdit page with the initially selected agenda.

          Show
          Sona Sona (Inactive) added a comment - - edited I was not able to get the UnexpectedRollbackException that is mentioned in the jira. I was however getting three other exceptions which were causing it to blow up 1. ArrayIndexOutofBounds exception at History.buildHistoryFromParameterString() pushToHistory(params[0], params[1], params[2], params[3], params[4]); 2. NullPointerExeption at AgendaEditorMaintainable.retrieveTermParameters() Tree<RuleTreeNode, String > propositionTree = rule.getPropositionTree(); 3.ExceptionEvaluationError at ExpressionEvaluatorServiceImpl.evaluateExpression() because it was retaining the pageId from the EditRule page. Expression expression = parser.parseExpression(expressionStr); I have added a fix for each of these and will create a review for it. Breadcrumbs on the Agenda Editor are no longer blowing up and it takes you back to the AgendaEdit page with the initially selected agenda.
          Hide
          Jessica Coltrin (Inactive) added a comment -

          Since these were fixed on the trunk, they are 2.3.

          Show
          Jessica Coltrin (Inactive) added a comment - Since these were fixed on the trunk, they are 2.3.

            People

            • Assignee:
              Sona Sona (Inactive)
              Reporter:
              Peter Giles (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel