Versions Compared

Version Old Version 2 New Version 3
Changes made by

Joanne Watson (Unlicensed)

Ashley Ransoo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added feedback #4.

...

#FeedbackComments
1EEA resident, Permit to Work, Settled status and Ethnic Origin info does not appear in the Person record but does exist in V10 - example record is GMC no. 6092685 Not sure if this is a DR issue or a plumbing issue
2Qualification 1 for this trainee (GMC no. 6092685) does not exist in V10 so not sure where it has come from
3Programme information is not coming through correctly - trainee with GMC no. 6107040.
4

Following conversation (Former user (Deleted), Alex Dobre (Unlicensed), Joanne Watson (Unlicensed), Ashley Ransoo) had on Save behaviour, the understanding was concurrency/stale data message would only come up if 2 admins are editing the same section. This does not seem to be the case in the following scenario:

I was logged in as 2 admins at the same time. Both goes to the same person record. Admin A loads 'Personal data' section, Admin B loads 'Sensitive data' section. Admin A then makes a change to contact number and Save, followed by Admin B making a change to ethnic origin and click on save. Admin B gets warned by stale data error message.

Expectation:
Assuming that 'Sensitive data' and 'Personal data' are 2 different sections, as they load 2 different pages with different sets of fields, then the optimistic locking stale data error message should not appear in the above scenario.

Nb: This does not happen when editing and saving 'Personal data' and 'Qualification' sections for e.g.