Requested CCMDB changes for the next version: Difference between revisions

TOstryzniuk (talk | contribs)
Line 7: Line 7:
** I suspect this is a version issue, where the latest backed up version was earlier than what might be expected. So, the fact that the patients didn't have the expected recordstatus makes sense. However, '''when you say you "changed them to complete on the main database page", what do you mean?'''{{discussion}} You should only be able to change the status on the patient view page. I am not sure why this is in requested changes, what is the change that is requested? {{discussion}} Ttenbergen 10:02, 2013 July 15 (CDT)
** I suspect this is a version issue, where the latest backed up version was earlier than what might be expected. So, the fact that the patients didn't have the expected recordstatus makes sense. However, '''when you say you "changed them to complete on the main database page", what do you mean?'''{{discussion}} You should only be able to change the status on the patient view page. I am not sure why this is in requested changes, what is the change that is requested? {{discussion}} Ttenbergen 10:02, 2013 July 15 (CDT)
***it was under '''bug fix''' because we did not know what was going on over there.  If it is not a bug then take it out of here.  In order for Sheila to be able to DELETE the send patients, she needed to mark them as sent. She can't do that via ccdmb.program from dropdown list.  You have to log into ccmdb.data and change record status field in there.[[User:TOstryzniuk|Trish Ostryzniuk]] 11:52, 2013 July 15 (CDT)
***it was under '''bug fix''' because we did not know what was going on over there.  If it is not a bug then take it out of here.  In order for Sheila to be able to DELETE the send patients, she needed to mark them as sent. She can't do that via ccdmb.program from dropdown list.  You have to log into ccmdb.data and change record status field in there.[[User:TOstryzniuk|Trish Ostryzniuk]] 11:52, 2013 July 15 (CDT)
**** I just tested: it is possible to change status to sent in the patient viewer (ie not in the list). The field is locked in the list to force using the viewer to change this field. This is necessary because the viewer will run checks whenever this field is changed. This behaviour is as designed. The only scenario for this to happen that I can think of is the one we had - restore of an older version of data. If there is something left to do on this, please elaborate. If not, please clear out this section. Ttenbergen 13:04, 2013 July 15 (CDT)


===Chinese in TMPV2 ===
===Chinese in TMPV2 ===