Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0.2
    • Fix Version/s: 1.0.3
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-3802Document Configuration View limits permission and responsibility lookups
      KULRICE-11624Sticky view header broken from structure changes
      KULRICE-12407Browser backbutton navigation broken when viewing lightbox
      KULRICE-6512Rice Dev: Clicking on View Document Configuration gives error
      KULRICE-7791Document configuration view blows up if any document-based permissions are not assigned to roles
      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-4703Improve current UI/configuration
      KULRICE-9888Dialog Test View - Displays Response in LightBox broken
      KULRICE-6160Update Routing Components and Configuration Guide
      KULRICE-8060Rice Maintenance Documents Broken
    • Rice Module:
      KEW, KIM
    • Application Requirement:
      KFS, Rice

      Description

      It looks like the change made back in February:

      KULRICE-3825 - replace aliased kim update services with beans to allow easier overriding of update services.

      Completely broke the document configuration view as it relates to permissions (and probably responsibilities).

      They used a special criteria property name which was known to the lookupable for PermissionImpl. Unfortunately, it was changed to fully use the lookup service. Unfortunate because the lookup service provides the "service" of removing unrecognized properties from the input criteria. (Such as the one I needed: "detailCriteria". The result is that every document shows every document initiation permission.

      The offending code is in LookupDaoOjb.createCriteria() where it returns null if the property type returns null.

      Either that code needs to be removed (default to a String?) or the property needs to be added to the object and DD.

      Should the lookup service be "sanitizing" the input criteria? It seems like this results in more problems for developers in troubleshooting rather than it would cause failures during lookups. What do you think?

        Issue Links

          Activity

          Hide
          Jeremy Hanson added a comment -

          How do I get to the Document Configuration View?

          Show
          Jeremy Hanson added a comment - How do I get to the Document Configuration View?
          Hide
          Travis Schneeberger added a comment - - edited

          disregard.

          Show
          Travis Schneeberger added a comment - - edited disregard.
          Hide
          Jeremy Hanson added a comment -

          I've reverted PermissionServiceImpl's lookupPermissions method to the way it was before the commit that broke this. I don't think that part was supposed to be changed. This seems to have fixed the Document Configuration View.

          FYI, to get to the Document Configuration View, you can open a Route Log, and click on the document type.

          Show
          Jeremy Hanson added a comment - I've reverted PermissionServiceImpl's lookupPermissions method to the way it was before the commit that broke this. I don't think that part was supposed to be changed. This seems to have fixed the Document Configuration View. FYI, to get to the Document Configuration View, you can open a Route Log, and click on the document type.

            People

            • Assignee:
              Jeremy Hanson
              Reporter:
              Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel