...
The process of adding and removing role members from departments in the Rice UI can be a time consuming process. To support the Time And Reporting System (TRS) Rice client application, there are often times when many role members must be added or removed from departments. Since it is not practical to make such mass updates via the Rice UI, these updates are currently managed though the Kuali Rice Data Set Migration Process. While this process does accomplish the task, it results in the proliferation of JIRA tickets and an increase in the workload for the DBA group who must execute the scripts. The scripts which are currently used to manage the department additions and removals consist of two procedures, one to add a role member to a department (add_dta_role_member), and one to remove a role member from a department (remove_dta_role_member). The script creates the procedures, adds or removes the role members, and then drops the procedures. This process is repeated with each Jira ticket which is created for the purpose of adding or removing role members. The procedures used each time are identical from one Jira ticket to the next, with the only different being the role members which are to be added or removed.
Because the procedures themselves do not change, it was determined that a permanently installed Oracle package which contained the needed procedures would be the most efficient way accomplish the task. Execution rights to the package would be is given to a KFS account created specifically to manage the roles. The KFS administrator would then use the account to execute an Oracle PL/SQL script which utilizes the package. In this way the KFS administrator would be in control of when the user role updates were made, rather than creating Jira tickets and scripts for the DBA group to retrieve and execute.
...