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

Permission doc creating a duplicate permission can be submitted but routes to exception

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: Not version specific
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-13379Create Web Tests for KRAD Maintenance Document permission check on route
      KULRICE-7881Copying/Creating a permission is not populating permission identifier even when the document is routed.
      KULRICE-12128Error creating new Permission
      KULRICE-8673Copy Permission not validating New Copy for duplicate Permission Name
      KULRICE-8802Permission details are not saved when new permission goes final
      KULRICE-5970Can not copy a permission
      KULRICE-6809Permission lookup does not return value when adding permission to Role
      KULRICE-4566Permission details can't be modified/created through KIM Permission screen
      KULRICE-7799Create a separate permission for accessing the new super user tab
      KULRICE-2301Create a new Kuali Rice Doctype Policy/KIM Permission ALLOW_UNREQUESTED_ACTION, whose default is true.
    • Rice Module:
      KIM
    • Application Requirement:
      KFS
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      I can create and successfully submit a new permission with a name that matches an existing permission. The document routes to exception (post processor caught exception while handling route status change: OJB operation; SQL []; ORA-00001: unique constraint (KR3.KRIM_PERM_T_TC1) violated ; nested exception is java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (KR3.KRIM_PERM_T_TC1) violated ).

      It would be nice if the doc just stopped me from submitting the permission document up front and told me the name needed to be unique.

        Issue Links

          Activity

          Hide
          Peter Giles (Inactive) added a comment - - edited

          I think this is a duplicate that has already been resolved, I'll assign it to Sona to verify.

          Show
          Peter Giles (Inactive) added a comment - - edited I think this is a duplicate that has already been resolved, I'll assign it to Sona to verify.
          Hide
          Sona Sona (Inactive) added a comment -

          The unique constraint is specified for the combination of namespace code and permission name and there is a validation for the combination to be unique.

          Show
          Sona Sona (Inactive) added a comment - The unique constraint is specified for the combination of namespace code and permission name and there is a validation for the combination to be unique.
          Hide
          Bryan Hutchinson added a comment -

          Could you link to the Rice JIRA this duplicates? It would be helpful to know which JIRA originally resolved this issue.

          Thanks,
          Bryan

          Show
          Bryan Hutchinson added a comment - Could you link to the Rice JIRA this duplicates? It would be helpful to know which JIRA originally resolved this issue. Thanks, Bryan

            People

            • Assignee:
              Sona Sona (Inactive)
              Reporter:
              Bryan Hutchinson
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel