| # | Feedback | Comments | Reporter | Owner |
|---|---|---|---|---|
| 1 | EEA 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 | Joanne Watson | |
| 2 | Qualification 1 for this trainee (GMC no. 6092685) does not exist in V10 so not sure where it has come from | Joanne Watson | ||
| 3 | Programme information is not coming through correctly - trainee with GMC no. 6107040. | Joanne Watson | ||
| 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: Nb: This does not happen when editing and saving 'Personal data' and 'Qualification' sections for e.g. | Ashley Ransoo | ||
General
Content
Integrations
0 Comments