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

Permission screen problems entering permission details

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.1
    • Fix Version/s: 2.1.2
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-4566Permission details can't be modified/created through KIM Permission screen
      KULRICE-6342Permission Document Error offers no help for Permission Details errors
      KULRICE-7458Restore the display of permission/responsibility details on KIM Inquiries
      KULRICE-6499Add permission for CacheAdmin screen
      KULRICE-4859The "create new" button shows up on the permission look up screen and the responsibility look up screen even if the user does not have permissions to initiate a new maintenance document of that type
      KULRICE-6442Rice Dev: Permission Lookup screen, Permission Template attribute label missing
      KULRICE-8802Permission details are not saved when new permission goes final
      KULRICE-10251Maintain KRMS Agenda permission has confusing and unused permission detail
      KULRICE-3547Each application could potentially embed the KSB screens, however there is only one set of permissions to them
      KULRICE-4805DocumentTypePermissionServiceImpl seems to build permission details incorrectly
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Any time I try and add an attribute while editing a permission, I get an error saying the attribute is not valid (error.existence).

      It looks like the DictionaryValidationService's validateReferenceExists(bo, referenceName) method looks for a foreign key reference on the Attribute Bo, and not finding anything, and then automatically displaying that error, and preventing the routing of the permission document.

        Activity

        Hide
        Peter Giles (Inactive) added a comment -

        This may have been fixed in 2.1.2 already. Sona, can you verify?

        Show
        Peter Giles (Inactive) added a comment - This may have been fixed in 2.1.2 already. Sona, can you verify?
        Hide
        Sona Sona (Inactive) added a comment -

        This is an issue only when the permissionDetails has namespaceCode as an attribute with a wildcard value. Added a fix to BusinessObjectDaoOjb buildCriteria().

        Show
        Sona Sona (Inactive) added a comment - This is an issue only when the permissionDetails has namespaceCode as an attribute with a wildcard value. Added a fix to BusinessObjectDaoOjb buildCriteria().
        Hide
        Jessica Coltrin (Inactive) added a comment -

        closing all 2.1.2 Jiras

        Show
        Jessica Coltrin (Inactive) added a comment - closing all 2.1.2 Jiras

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel