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

make assembly of permission details (e.g. in DocumentTypePermissionServiceImpl.buildDocumentTypePermissionDetails(...)) dynamic based on db config


    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.1
    • Fix Version/s: Backlog
    • Component/s: Development
    • Labels:
    • Similar issues:
      KULRICE-6157Document the use of "PreRoute" in document-centric permission details lists
      KULRICE-9320Determine out-of-the-box configuration for EclipseLink dynamic weaving support for lazy loading
      KULRICE-6325Add Type to details for Populate Group permissions
      KULRICE-4059Have a config param that turns emails on or off
      KULRICE-3713Remove some duplication of permission checks in the document authorizer base
      KULRICE-12544Allow for table columns to be dynamically created (based on a subcollection)
      KULRICE-238Enhance document search to allow for dynamic drop downs and lookups dependent on external system data, for search criteria fields based on custom doc search attributes
      KULRICE-4241Create DB Refresh CI for 1.0.3 oracle and mysql
      KULRICE-12421Refactor datasource config parameter to support module specific configuration
      KULRICE-4099Include sensible config location defaults for window machines for rice standalone
    • Rice Module:


      Assembling of permission detail attributes is poorly factored – hard code has to match the configuration expressed in the database in the tables krim_typ_t, krim_typ_attr_t, and krim_attr_defn_t. If this configuration is going to live in the database, it seems that we should be able to dynamically assemble the required attributes based on that db configuration. Not sure off the top of my head how tricky this would be to implement, but of course each type will only support certain attributes so there will be limitations to how flexible it can be.

      In any case, in its present form this has a funny smell to it and at least could use some thought as to how it might be refactored.


        There are no comments yet on this issue.


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


            • Created:

              Structure Helper Panel