We have some infopath based forms in a K2 process that move through a fairly linear workflow. Unfortunately, we cannot use the "cannot be blank" validation in the Infopath views because it prevents people from submitting the form if the field is not in their current Infopath activity view.
Though line rules support options like = or <> for specific data field values, what about "blank" or "not blank"? We essentially want to prevent movement between activities in the case a person forgets to fill in a field. Failure to fill in a required field will keep the work item in their worklist until the field is filled out. At first I thought of making a line rule where the data field in question needed to be "not blank", but I see this is not the option. The field(s) in question contain telephone numbers or addresses, so we cannot use the = or <> operators. Any ideas?
Thanks,
Jason
Page 1 / 1
The InfoPath Validation behavior as explained is expected. Using K2.net 2003 to validate required input is not the cleanest/most efficient way of doing validation. I have encountered this couple of times; one way around it is to write some .NET code for the InfoPath doc to take care of the validation instead of using the standard validation in InfoPath.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.