Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-3055

determine whether the required attribute tables were a good idea

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Analysis
    • Labels:
    • Rice Module:
      KIM

      Description

      we had a table to list the required role attributes for given permissions and a corresponding one for responsibilities. the idea was that the code checking the permissions is passing certain qualifiers, so there are some basic requirements that any role assigned those permissions or responsibilities should meet. we also had the concept of a translator - so, for example if a given permission needed (i.e. the calling code was passing) a chart/org (i.e. the rows for that perm in krim_perm_rqrd_attr_t listed chart and org) and permission was being granted to a campus role- the role type could have a chart/org to campus translator registered with it, so that assignment would be allowed.

      since code (permissions) and dd entries (responsibilities) are directly associated with the data, we wanted a way to show users the association and prevent functional people from unknowingly making mistakes - like assigning a modify accounting lines permission to a commodity code role.

      we hadn't gotten around to implementing the enforcement in the kim uis, we would have needed to spend time thoroughly review the data, we weren't confident that this was the perfect way to go, and we ran out of time to take risks. so, we removed those tables and associated code. hopefully as people start really using kim, clear requirements will emerge, or maybe we'll never verify the need for something like this.

      see linked issue

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                Unassigned
                Reporter:
                dlemus Dan Lemus (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: