I wonder what I have to do with this field , and also the field “Alow entering data” of the Organisation Unit .
As what I’m thinking is :
If an organisation unit is closed in real. User have to set the close date for it. Then we should automatically set the allow entering data to FALSE.
If an organisation Unit is not allowing entering data. Then in the data entry form. If user try to enter data for it. We should not allow them, and show a popup to inform that this orgUnit is closed.
if the orgunit is closed then one should not be able to enter data for it. But there is no allow-enter-data attribute on OrganisationUnit in trunk so I’m not sure about that…
I wonder what I have to do with this field , and also the field “Alow entering data” of the Organisation Unit .
As what I’m thinking is :
If an organisation unit is closed in real. User have to set the close date for it. Then we should automatically set the allow entering data to FALSE.
If an organisation Unit is not allowing entering data. Then in the data entry form. If user try to enter data for it. We should not allow them, and show a popup to inform that this orgUnit is closed.
I wonder what I have to do with this field , and also the field “Alow entering data” of the Organisation Unit .
As what I’m thinking is :
If an organisation unit is closed in real. User have to set the close date for it. Then we should automatically set the allow entering data to FALSE.
If an organisation Unit is not allowing entering data. Then in the data entry form. If user try to enter data for it. We should not allow them, and show a popup to inform that this orgUnit is closed.
Also the same in Import data modules.
Is this right ?
Hi Viet,
if the orgunit is closed then one should not be able to enter data for it. But there is no allow-enter-data attribute on OrganisationUnit in trunk so I’m not sure about that…
Lars
Hi Viet and Lars
There is “active”. Is this what you mean? In which case I’d also be interested to know the history - is active=“false” synonomous with closedDate==notEmpty ? Or are there other permutations which make sense? I really don’t know.
Just one thought about having a date for closed. I would interpret this as an indication that it doesn’t make sense to enter datavalues (through ui or import) for that orgunit with a period which is after the close date. There might be a case where you would have to enter datavalues from periods prior to the close date. I’m thinking around retsoring backups or some such scenario. So barring any data entry might be a bit dangerous.