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

add permission templates and additional permissions to conversion script SQL output

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-11116Enhance conversion scripts to convert inquiry permissions I30, I33, I34
      KULRICE-7090Documentation: expand documentation in KIM UG for delivered Permission Templates
      KULRICE-9907PermissionServiceImpl.getPermissionsByTemplateName gets inactive permission templates
      KULRICE-10970KD 2013 Install Fest Prep: Create Rice DB SQL script
      KULRICE-11458Maintenance Conversion Script - M84 & M85 alternate/additional display attribute name
      KULRICE-3278Determine if permission is still being checked for org.kuali.rice.kew.web.backdoor.AdministrationAction
      KULRICE-10744Create database scripts for KNS/KRAD conversion
      KULRICE-11453Maintenance Conversion Script - M22 Additional JS File
      KULRICE-2632Fix error output display on XML Ingester and add additional field fields
      KULRICE-11115Enhance conversion scripts to connect to Rice database
    • Rice Module:
      KRAD
    • Sprint:
      2.4.0-m4 KRAD Sprint 2, 2.4.0-rc1 Sprint 1, 2.4.0-rc1 Sprint 4, 2.4.0-rc1 Sprint 5, 2.4.0-rc1 Sprint 6, 2.4.0-rc1 Sprint 7, 2.4.0-rc1 Sprint 8
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Modify conversion script to add the following to the SQL output: copy the permission templates from the KR-NS namespace to KR-KRAD, and convert the existing permissions to use the new templates. Confirm with Jerry which permission templates to copy, there may be a few that we will want to omit. From an email thread w/ Jerry: "There might be a few we will not use (for example the old KNS edit maintenance section and those like this will be replaced by the view/component permissions)."

        Issue Links

          Activity

          Hide
          Sona Sona (Inactive) added a comment -

          Thanks Peter. I have updated the doc with some more findings.

          Jerry,
          I have a couple more questions as I am digging more into this issue. Here is the link to the updated Permissions google doc.
          https://docs.google.com/a/uw.edu/spreadsheet/ccc?key=0AsPQLskBDt2udHd4cHc2OWtXUE5kc2c0WXhwX1BVNFE&usp=drive_web#gid=0

          1.How do you map 'propertName' kim attribute in KNS to either 'fieldId' or 'propertyName' attribute in KRAD?
          For eg: 'Modify Maintenance Document Field' permissionTemplate in KNS is converted to Template Name 'Edit Field': Details viewId and
          fieldId or viewId and propertyName (for data fields). In KNS the details are component and propertyName. 'component' will get converted to viewId but
          how would the conversion script know that the propertyName has to be converted into fieldId or propertyName? Or should I create entries for both
          fieldId and propertyName. The case is similar in Modify Maintenance Document Section,View Inquiry or Maintenance Document Field,
          View Inquiry or Maintenance Document Section. I haven't checked the others yet.

          2. Do all templates need to be converted into KRAD? There are quite a few that have not yet been converted over in code. So the ones marked 'Same' in the 'IN KRAD'
          column in the excel sheet on google docs are still using KNS templates.

          3. For now I am working on getting the conversion script to work for the templates that have already been converted over in code into KRAD.

          Thanks,
          -Sona

          Show
          Sona Sona (Inactive) added a comment - Thanks Peter. I have updated the doc with some more findings. Jerry, I have a couple more questions as I am digging more into this issue. Here is the link to the updated Permissions google doc. https://docs.google.com/a/uw.edu/spreadsheet/ccc?key=0AsPQLskBDt2udHd4cHc2OWtXUE5kc2c0WXhwX1BVNFE&usp=drive_web#gid=0 1.How do you map 'propertName' kim attribute in KNS to either 'fieldId' or 'propertyName' attribute in KRAD? For eg: 'Modify Maintenance Document Field' permissionTemplate in KNS is converted to Template Name 'Edit Field': Details viewId and fieldId or viewId and propertyName (for data fields). In KNS the details are component and propertyName. 'component' will get converted to viewId but how would the conversion script know that the propertyName has to be converted into fieldId or propertyName? Or should I create entries for both fieldId and propertyName. The case is similar in Modify Maintenance Document Section,View Inquiry or Maintenance Document Field, View Inquiry or Maintenance Document Section. I haven't checked the others yet. 2. Do all templates need to be converted into KRAD? There are quite a few that have not yet been converted over in code. So the ones marked 'Same' in the 'IN KRAD' column in the excel sheet on google docs are still using KNS templates. 3. For now I am working on getting the conversion script to work for the templates that have already been converted over in code into KRAD. Thanks, -Sona
          Hide
          Sona Sona (Inactive) added a comment -

          Attached is the sql insert queries I am using for testing

          Show
          Sona Sona (Inactive) added a comment - Attached is the sql insert queries I am using for testing
          Hide
          Sona Sona (Inactive) added a comment -

          The following templates have been added to the conversion script SQL output
          "View Inquiry or Maintenance Document Field":"View Field",
          "View Inquiry or Maintenance Document Section":"View Group",
          "Inquire Into Records":"Open View",
          "Modify Maintenance Document Field":"Edit Field",
          "Modify Maintenance Document Section":"Edit Group",
          "Perform Custom Maintenance Document Function":"Perform Action"

          Stopping progress - Waiting on response to the queries above.

          Show
          Sona Sona (Inactive) added a comment - The following templates have been added to the conversion script SQL output "View Inquiry or Maintenance Document Field":"View Field", "View Inquiry or Maintenance Document Section":"View Group", "Inquire Into Records":"Open View", "Modify Maintenance Document Field":"Edit Field", "Modify Maintenance Document Section":"Edit Group", "Perform Custom Maintenance Document Function":"Perform Action" Stopping progress - Waiting on response to the queries above.
          Hide
          Sona Sona (Inactive) added a comment - - edited

          Responses from Jerry on the questions above:
          1. We would only map to 'propertyName' and ignore 'fieldId' for the templates. The componentName would map to viewId but we would modify the viewId to be something like <ComponentName>MaintenanceView.

          2. The namespace for all templates should be changed to KR-KRAD.

          We need to create jiras for the code to use the KR-KRAD namespace permissions instead of the KNS namespace permissions. - Created KULRICE-12471
          Also at some point these sql should become part of the impex data. Need a jira for that too. -
          Created KULRICE-12472

          Show
          Sona Sona (Inactive) added a comment - - edited Responses from Jerry on the questions above: 1. We would only map to 'propertyName' and ignore 'fieldId' for the templates. The componentName would map to viewId but we would modify the viewId to be something like <ComponentName>MaintenanceView. 2. The namespace for all templates should be changed to KR-KRAD. We need to create jiras for the code to use the KR-KRAD namespace permissions instead of the KNS namespace permissions. - Created KULRICE-12471 Also at some point these sql should become part of the impex data. Need a jira for that too. - Created KULRICE-12472
          Show
          Sona Sona (Inactive) added a comment - Link to the permission google doc https://docs.google.com/spreadsheet/ccc?key=0AsPQLskBDt2udHd4cHc2OWtXUE5kc2c0WXhwX1BVNFE&usp=drive_web#gid=0

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3 days
                3d
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 days
                3d

                  Agile

                    Structure Helper Panel