The cmn_sec_user_groups table update is incorrect when User groups are added in MUX > Admininstration > users
STEPS TO REPRODUCE:
- Go to Classic > Administration > Organization and Access > Resources.
- Open any given resource and note the user ID on the URL, let say 5091199
http://myClarityserver/niku/nu#action:nmc.openUser&id=5091199&resourceId=5059678 - Run the following statement to the DB
select * from cmn_sec_user_groups where user_id = 5091199 - Look at the results. It lists all groups the user is assigned to
- Go to the Resource's Groups tab and add a new groups
- Run the query from step 3 again
- A mew group has been added with the last_updated_by and last_updated_date for the record inserted All pre-existing rows have not been modified
- In MUX > Administration > Users, filter by the same resource we used in Classic
- Add the User Groups column into the grid
- Add a new group to the field
- Run the following statement to the DB
- select * from cmn_sec_user_groups where user_id = 5091199
- Look at the result set
Expected Results: A new row is added. with the last_updated_by and last_updated_date of the insert. Pre-existing rows do not get modified.
Actual Results: A new row is added. with the last_updated_by and last_updated_date of the insert. Pre-existing rows get modified.
In Oracle the last_updated_by and last_updated_date columns get updated as per the data on the inserted row.
In PG, the last_updated_by is set to 0 and last_updated_date is updated for all rows.