Thread: Serious issue with 6.1.3 on oracle

I found a serious bug in 6.1.3 today when all files are pushed to oracle.

STR:

1. Start a client session, logon with user A. Goto change management and do a true search. Leave the client in the qbe
2. Start a new client sessions, logon with user B. Giti change management and do a true search. Select a change for update. Make an update for example change phase. Save the updates and return to the qbe. Go back in the change to verify the updates were saved.
3. Return to client session 1. Do not refresh the qbe but open the same change as user B just updated. Now you see data from BEFORE user B updated it. This means if user A updates the change the update done by user B is lost!

This is a critical bug and has been reported to HP.

It seems this problem is solved in 6.2 beta 2.

Yeah I think you are right.

I think the client downloads all the data for all the records displayed in the qbe and use that data to display the record.

Now HP just need to release 6.2 really fast.

A SCR to fix this has been scehduled for 6.1.4 and 6.2.1.

It has been observed in other parts of sc such as in the schedule file.

Since HP say it will be fixed in 6.1.4 and 6.2.1 it is a RTE fix.

I got a workaround from HP to "fix" the issue.

Ask for SCR37484 which is a new version of se.view.engine rad application.

Also you need to use lock on display.

These 2 changes will result in a "record modifie...." msg when user double clicks on the record in the qbe and then loads the updated data. Yes strange but it solves the issue.