Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0.2
    • Fix Version/s: 1.0.3
    • Component/s: Development
    • Labels:
      None
    • 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?

        Attachments

          Issue Links

            Activity

            Hide
            jjhanso Jeremy Hanson added a comment -

            How do I get to the Document Configuration View?

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

            disregard.

            Show
            tschneeb Travis Schneeberger added a comment - - edited disregard.
            Hide
            jjhanso 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
            jjhanso 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:
                jjhanso Jeremy Hanson
                Reporter:
                jkeller 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