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

Numerous issues with new Routing Rule maintenance document

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0
    • Component/s: Development, Testing
    • Labels:
      None
    • Similar issues:
      KULRICE-2653Implement business rules for the new Routing Rule Delegation maintenance document
      KULRICE-2622Implement business rules for the new Routing Rule maintenance document
      KULRICE-8544Travel Account Maintenance (New) Document: Account Number issues
      KULRICE-2600Can't default fields on new Maintenance documents using request parameters
      KULRICE-4500From and To dates note handled correctly on Routing Rules Maintenance document
      KULRICE-11931Routing Rule Maintenance - JPA Duplicate Key Exception when saving edits
      KULRICE-11887Workflow Routing Rules Doc Type Lookup fails to return result
      KULRICE-4345Implement Rule Routing in our rule document types for Rice 1.0
      KULRICE-2662Hook up Routing Rule and Routing Rule Delegation maintenance document handlers
      KULRICE-2644Implement a "front page" for routing rule creation that allows the user to select the document type and rule template prior to creating the rule
    • Rice Module:
      KEW

      Description

      There appear to be a few issues with the new Routing Rule maintenance document. Here are at least a few issues that I found:

      1) Something very weird is going on with the from and to dates. It looks like they are getting rendered as timestamps and the fomatting on them are all messed up. You can see what I mean if you just edit an existing rule and then attempt to submit it. These should just be plain dates, no time component needed.
      2) One you fix the date issue, it appears that editing no longer be setting up appropriate relation between the previous version of the rule and the new version of the rule. If you click submit it will tell you that the name is already in use and must be unique. In actuality, there may be more than one row in the rule database that has the same name, however they will all be on the same rule (but different versions of the rule). So editing and clicking submit immediately should work. But if you attempt to create a new rule and give it the same name as another rule it shouldn't work.
      3) Also, if you change the name on the rule after an edit so as to no longer get that error message, it doesn't properly link the rule with it's proper previous version. You should be able to edit a rule, change the name and then re-submit it and still have it considered the same rule (i.e. it's previous version id will be the one that you edited and the rule that you edited would have a current indicator of false)

      In general, we should do some extensive functional testing on this screen so we can expose all of these issues. Additional things we should check at the very least include checking if the locking of the rule based on previous version id is working as expected as well as the copy function working properly.

      We need to test all of these things as well for the delegate rules.

        Activity

        Hide
        Jeremy Hanson added a comment -

        These issues have been resolved.

        Show
        Jeremy Hanson added a comment - These issues have been resolved.
        Hide
        Eric Westfall added a comment -

        Bulk change of all Rice 1.0 issues to closed after public release.

        Show
        Eric Westfall added a comment - Bulk change of all Rice 1.0 issues to closed after public release.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 1 day, 4 hours
              1d 4h
              Remaining:
              Time Spent - 1 day, 2 hours, 10 minutes Remaining Estimate - 1 hour, 50 minutes
              1h 50m
              Logged:
              Time Spent - 1 day, 2 hours, 10 minutes Remaining Estimate - 1 hour, 50 minutes
              1d 2h 10m

                Structure Helper Panel