Open urapadmin opened 1 week ago
Yikes. Does it make sense to test this in PVD, considering the mess of identification methods? Or is this only for real projects?
This is working in BUAP but BUAP is also rather easy because it's a pure legacy project and so most ID methods are set to free input in any case. But I can make every type of ID listed above as expected, and can change every one of them as expected, too, with the sole exception that I still don't really understand the way the ANC#s work given that they are completely divorced from relationship (in numbering) to any other type of entity. But I think that's nothing to do with this not working.
Yikes. Does it make sense to test this in PVD, considering the mess of identification methods? Or is this only for real projects?
ja, why not. If you find a bug in PVD we don't need to encounter it in a real project.
Of those projects that have the exact same identification methods running it is enough to test only one. And we can test this bit by bit. It is a bit before the next projects go into the field again.
coming out of #2967 and #2956
Ja. That is the case, unfortunately. We have to check that all parts of each project that can create a new identifier are still working properly in both normal mode and temporary free input mode.
So, whenever we roll out a recording app version 16.4.4 or higher for the first time for a project all the creation of all these records needs to be checked:
And again, for normal creation / creation with temporary free input / editing an existing identifier with temporary free input