We are working on a new requirement to control the editing of forms to restrict the entry of data for older periods.
This is required because entering data for older periods would impact the reports generated for those periods. Typically the data entry for a month would finish by the 10th of the next month and further previous month is considered as closed and no editing should be allowed for that period. Ideally, the retrospective data entry also should be prevented for older periods. An exception could be provided for users with special privileges.
Is there a way to do this on Form 2.0 currently?
If we have to customize, any suggestions what’s the best way to do this?
An idea for customization that came up was like this: Data entry/editing of forms get auto locked after a certain date next month. A superuser can unlock/lock the form so that he can allow/block users to do editing or data entry for older periods.
That is indeed a nice feature to have and could be helpful for other implementations as well.
Since the problem is more related to retrospective data entry, so I would suggest adding a restriction to the retrospective data entry feature itself rather than freezing the forms. Something like a rule that says, users should not be allowed to select a date in the previous month after the 11th day of the current month unless they have the admin role.
Retrospective data entry is to be allowed only for older dates of the current month and for the previous month if the current date is not past the 10th. The selection of older dates will be disabled for retrospective data entry. The threshold date will be a configurable property and this restriction will not be applicable to users with a special privilege.
The edit of older forms on forms display controller is allowed only for the current month and for the previous month if the current date is not past the 10th. The threshold date will be a configurable property and this restriction will not be applicable to users with a special privilege.