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

Permission maintenance doc requires Template Id and has no lookup

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-b3, 2.0
    • Fix Version/s: 2.0.0-b6, 2.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Environment:
      Sample App
    • Similar issues:
      KULRICE-6998"Template Id" field on the Permission maintenance document should be a drop-down menu instead of a text field
      KULRICE-5993doc search view of krad maintenance doc shows hidden fields
      KULRICE-2405create Permission Lookup & Inquiry
      KULRICE-6442Rice Dev: Permission Lookup screen, Permission Template attribute label missing
      KULRICE-1273The Rule Template ID column on the Rule Template Lookup only sorts by the first digit of the ID
      KULRICE-3457Approve button not rendered on parameter document even if user has an approve request
      KULRICE-3735KIM Permission templates are queried from the DB too often
      KULRICE-8802Permission details are not saved when new permission goes final
      KULRICE-8644When trying to copy certain permissions, doc gets stuck 'Enroute'
      KULRICE-11564add permission templates and additional permissions to conversion script SQL output
    • Rice Module:
      KIM
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      The permission lookup isn't showing anything for the template information, and selecting a template requires you to know the magic # (10001)

        Activity

        Hide
        Jessica Coltrin (Inactive) added a comment -

        Closing since these items are now in the release notes.

        Show
        Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.
        Hide
        Emerson David (Inactive) added a comment -

        Once I got the Permission Template lookup working, trying to return a value back to the Create Permission screen yields:

        org.apache.commons.beanutils.NestedNullException: Null property value for 'template' on bean class 'class org.kuali.rice.kim.impl.permission.GenericPermissionBo'
        	org.apache.commons.beanutils.PropertyUtilsBean.isWriteable(PropertyUtilsBean.java:1507)
        	org.apache.commons.beanutils.PropertyUtils.isWriteable(PropertyUtils.java:675)
        	org.kuali.rice.kns.util.FieldUtils.populateBusinessObjectFromMap(FieldUtils.java:786)
        	org.kuali.rice.kns.util.FieldUtils.populateBusinessObjectFromMap(FieldUtils.java:746)
        	org.kuali.rice.kns.maintenance.KualiMaintainableImpl.populateBusinessObject(KualiMaintainableImpl.java:128)
        	org.kuali.rice.kns.web.struts.form.KualiMaintenanceForm.populate(KualiMaintenanceForm.java:227)
        	org.kuali.rice.kns.web.struts.action.KualiRequestProcessor.processPopulate(KualiRequestProcessor.java:283)
        	org.kuali.rice.kns.web.struts.action.KualiRequestProcessor.processFormActionAndForward(KualiRequestProcessor.java:208)
        	org.kuali.rice.kns.web.struts.action.KualiRequestProcessor.strutsProcess(KualiRequestProcessor.java:202)
        	org.kuali.rice.kns.web.struts.action.KualiRequestProcessor.process(KualiRequestProcessor.java:89)
        	org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
        	org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449)
        	javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        	javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        	org.kuali.rice.kew.web.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:78)
        	org.kuali.rice.kew.web.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:62)
        	org.kuali.rice.kew.web.UserLoginFilter.doFilter(UserLoginFilter.java:88)
        	org.kuali.rice.kew.web.UserLoginFilter.doFilter(UserLoginFilter.java:76)
        	org.kuali.rice.kew.web.BootstrapFilterChain.doFilter(BootstrapFilter.java:271)
        	org.kuali.rice.kew.web.DummyLoginFilter.doFilter(DummyLoginFilter.java:96)
        	org.kuali.rice.kew.web.DummyLoginFilter.doFilter(DummyLoginFilter.java:55)
        	org.kuali.rice.kew.web.BootstrapFilterChain.doFilter(BootstrapFilter.java:264)
        	org.kuali.rice.kew.web.BootstrapFilter.doFilter(BootstrapFilter.java:162)
        	org.displaytag.filter.ResponseOverrideFilter.doFilter(ResponseOverrideFilter.java:125)
        	org.kuali.rice.krad.web.filter.HideWebInfFilter.doFilter(HideWebInfFilter.java:69)
        

        Looks like we'll need the "Tomcat 7 hack" from KULRICE-5927.

        Show
        Emerson David (Inactive) added a comment - Once I got the Permission Template lookup working, trying to return a value back to the Create Permission screen yields: org.apache.commons.beanutils.NestedNullException: Null property value for 'template' on bean class 'class org.kuali.rice.kim.impl.permission.GenericPermissionBo' org.apache.commons.beanutils.PropertyUtilsBean.isWriteable(PropertyUtilsBean.java:1507) org.apache.commons.beanutils.PropertyUtils.isWriteable(PropertyUtils.java:675) org.kuali.rice.kns.util.FieldUtils.populateBusinessObjectFromMap(FieldUtils.java:786) org.kuali.rice.kns.util.FieldUtils.populateBusinessObjectFromMap(FieldUtils.java:746) org.kuali.rice.kns.maintenance.KualiMaintainableImpl.populateBusinessObject(KualiMaintainableImpl.java:128) org.kuali.rice.kns.web.struts.form.KualiMaintenanceForm.populate(KualiMaintenanceForm.java:227) org.kuali.rice.kns.web.struts.action.KualiRequestProcessor.processPopulate(KualiRequestProcessor.java:283) org.kuali.rice.kns.web.struts.action.KualiRequestProcessor.processFormActionAndForward(KualiRequestProcessor.java:208) org.kuali.rice.kns.web.struts.action.KualiRequestProcessor.strutsProcess(KualiRequestProcessor.java:202) org.kuali.rice.kns.web.struts.action.KualiRequestProcessor.process(KualiRequestProcessor.java:89) org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913) org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449) javax.servlet.http.HttpServlet.service(HttpServlet.java:617) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) org.kuali.rice.kew.web.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:78) org.kuali.rice.kew.web.UserPreferencesFilter.doFilter(UserPreferencesFilter.java:62) org.kuali.rice.kew.web.UserLoginFilter.doFilter(UserLoginFilter.java:88) org.kuali.rice.kew.web.UserLoginFilter.doFilter(UserLoginFilter.java:76) org.kuali.rice.kew.web.BootstrapFilterChain.doFilter(BootstrapFilter.java:271) org.kuali.rice.kew.web.DummyLoginFilter.doFilter(DummyLoginFilter.java:96) org.kuali.rice.kew.web.DummyLoginFilter.doFilter(DummyLoginFilter.java:55) org.kuali.rice.kew.web.BootstrapFilterChain.doFilter(BootstrapFilter.java:264) org.kuali.rice.kew.web.BootstrapFilter.doFilter(BootstrapFilter.java:162) org.displaytag.filter.ResponseOverrideFilter.doFilter(ResponseOverrideFilter.java:125) org.kuali.rice.krad.web.filter.HideWebInfFilter.doFilter(HideWebInfFilter.java:69) Looks like we'll need the "Tomcat 7 hack" from KULRICE-5927 .
        Hide
        Emerson David (Inactive) added a comment -

        Looks like we need to:

        1. bring forward KimPermissionTemplateImpl.xml (see https://test.kuali.org/svn/rice/tags/rice-1.0.3.3/impl/src/main/resources/org/kuali/rice/kim/bo/datadictionary/KimPermissionTemplateImpl.xml) and model it after ResponsiblityTemplate.xml
        2. Modify UberPermissionImpl-templateId-parentBean to behave more like GenericPermission-templateId bean (see https://test.kuali.org/svn/rice/tags/rice-1.0.3.3/impl/src/main/resources/org/kuali/rice/kim/bo/datadictionary/GenericPermission.xml)
          <bean id="GenericPermission-templateId" parent="KimPermissionTemplateImpl-templateId-parentBean"
                  p:required="true"
                  p:name="templateId">
              <property name="control">
                <bean parent="SelectControlDefinition" p:valuesFinderClass="org.kuali.rice.kim.lookup.valuefinder.PermissionTemplateValuesFinder" p:includeKeyInLabel="true"/>
              </property>
            </bean>
          
        Show
        Emerson David (Inactive) added a comment - Looks like we need to: bring forward KimPermissionTemplateImpl.xml (see https://test.kuali.org/svn/rice/tags/rice-1.0.3.3/impl/src/main/resources/org/kuali/rice/kim/bo/datadictionary/KimPermissionTemplateImpl.xml ) and model it after ResponsiblityTemplate.xml Modify UberPermissionImpl-templateId-parentBean to behave more like GenericPermission-templateId bean (see https://test.kuali.org/svn/rice/tags/rice-1.0.3.3/impl/src/main/resources/org/kuali/rice/kim/bo/datadictionary/GenericPermission.xml ) <bean id= "GenericPermission-templateId" parent= "KimPermissionTemplateImpl-templateId-parentBean" p:required= " true " p:name= "templateId" > <property name= "control" > <bean parent= "SelectControlDefinition" p:valuesFinderClass= "org.kuali.rice.kim.lookup.valuefinder.PermissionTemplateValuesFinder" p:includeKeyInLabel= " true " /> </property> </bean>
        Hide
        Peter Giles (Inactive) added a comment -

        KIM maint doc issue, setting Jeremy as lead.

        Show
        Peter Giles (Inactive) added a comment - KIM maint doc issue, setting Jeremy as lead.
        Hide
        Peter Giles (Inactive) added a comment -

        We ran into this issue when creating a new permission. There is no lookup for selecting a permission template, and it requires you to enter an ID. Trying to find the ID by doing a lookup on other permissions, we discovered that the permission template name and namespace columns are all blank. The only to figure out what permission template ID another permission was using was to edit that other permission, since the inquiry view shows only blanks for it as well. So the permission template ID field in the Permission maint doc is a bit of a disaster at the moment.

        Show
        Peter Giles (Inactive) added a comment - We ran into this issue when creating a new permission. There is no lookup for selecting a permission template, and it requires you to enter an ID. Trying to find the ID by doing a lookup on other permissions, we discovered that the permission template name and namespace columns are all blank. The only to figure out what permission template ID another permission was using was to edit that other permission, since the inquiry view shows only blanks for it as well. So the permission template ID field in the Permission maint doc is a bit of a disaster at the moment.

          People

          • Assignee:
            Emerson David (Inactive)
            Reporter:
            Erik Meade
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel