Luke Stevens, Murdoch Children's Research Institute https://www.mcri.edu.au
Action tags to validate date and datetime field entries:
@PASTEntered value must be in the past, i.e. is earlier than today/now (today/now is out of range)@FUTUREEntered value must be in the future, i.e. is later than today/now (today/now is out of range)@NOTPASTEntered value must NOT be in the past, i.e. is today/now or later (today/now is in range)@NOTFUTUREEntered value must NOT be in the future, i.e. is today/now or earlier (today/now is in range)
From v1.1.0 the implementation of the tags has been simplified to utilise the (from REDCap v12.1.0) functionality for using today/now as min or max for date and datetime fields:
-
@PAST: max=today-1 (date fields) -
@FUTURE: min=today+1 (date fields) -
@NOTPAST: min=today -
@NOTFUTURE: max=today -
@FUTUREand@NOTPASTtags will be ignored if the field already has a min value specified. -
@PASTand@NOTFUTUREtags will be ignored if the field already has a max value specified.
Consequences of this change are:
@NOTPASTand@NOTFUTUREare completely equivalent to using "today"/"now" as min/max value of range.@NOTPASTand@NOTFUTUREremain implemented only for backward compatibility.- For datetime fields all tags are completely equivalent to using "now" as min/max value of range.
- As with all action tags, these apply only to data entry form and survey form entry, not to data imports.
- If more than one of these tags is applied to a field only the first will be used.
- The action tag validation check is a soft check similar to existing range checks (i.e. a warning is displayed but the value is permitted). Use
@FORCE-MINMAXto enforce a hard check (i.e. reject value). @FUTURE/@NOTPAST: when you enter a future date/time and then after that time return to the form, the validation check will be triggered only after data on the form has changed.
