1.1 only used a few fields from the patient record into the pedigree, and 1.3 will have two-way syncing between the pedigree and the patient record. 1.2 is stuck in the middle, the pedigree uses most of the information from the patient record, but doesn't yet push back any information, thus the proband information can only be edited in the patient record. This is a regression affecting the users that use almost exclusively the pedigree to enter patient information. The 1.1 behavior should be re-enabled for those that want it.
Create a new configuration option to control:
- Whether the proband is editable in the pedigree
- Whether pedigree proband values are reset to blank