I have been facing some strange behaviour with archived CRFs in OC.
Assume an ongoing study has an event with CRF #1(Test_R_And_A) that has new requirements which cannot be implemented in the new version of the CRF #1 due to version update limitations. Thus, a new CRF #2(Test_R_And_A_2) is created and linked with the event. In order to restrict data entry for the CRF#1 but still be able to have relevant data in the data extractions it is Archived(Locked). The issue is that CRF#1 is still accessible for the data entry.
I have attached screens for easy reference.
What can be the workaround?
Please help me out.