Jump to content

Mandated data time control field condition was satisfied by a full stop - breaking workflow


Recommended Posts

Posted
We have a workflow that requires a hold based on a date/time field entered in a Human Task
image.png.cdc1366955b84ff553826069a701e077.png
image.thumb.png.062397c5146c6e00f0471e3d515d8eec.png
 
One of our agents entered a full stop but that has broken the workflow. We've addressed this as a training issue.
 
It appears the mandatory date/time field accepts a full stop as a valid entry. You would think a Date and Time Control field would require a date/time entry to meet the criteria of "this field requires a value...".
 
image.thumb.png.4125afe1218e4b39b9dcc44ab264e612.png
I notice when you have a multi-line text field, you get a Regex validation test option. But that is not available with the Date Time Control.
 
image.png.a75864f7fcf96649c80951cebc9a0905.png
 
So I would suggest we either need
 
1) the Date/Time control to have validation built-in or
2) some sort of validation option to build-it ourselves
 
Any thoughts?
 
Berto
 
 

image.png

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...