DateField Mask

So as Stefan Helzle says you could use a text field, apply the necessary validations, and then construct the date by extracting the day/month/year components and concatenating them into the relevant format before saving into the target variable.

But I have to ask why you feel it necessary to go to all that trouble. The data field provides all of the necessary validation, it'll adjust accordingly to different locales (e.g. mm/dd/yyyy for the US, dd/mm/yyyy for the UK), has a date picker, all of which costs the user two extra key strokes to include the "/" separator.

So as Stefan Helzle says you could use a text field, apply the necessary validations, and then construct the date by extracting the day/month/year components and concatenating them into the relevant format before saving into the target variable.

But I have to ask why you feel it necessary to go to all that trouble. The data field provides all of the necessary validation, it'll adjust accordingly to different locales (e.g. mm/dd/yyyy for the US, dd/mm/yyyy for the UK), has a date picker, all of which costs the user two extra key strokes to include the "/" separator.

Yes, we should use the Date field.

Also, it would be good if Appian provided this masking capability in future releases (automatically formatting date). This will increase data entry speed.