Sub Routine for Validation

I want to validate the data entered in one of my workflow input fields so that only Numeric entries are accepted.

Would someone like to share a sub routine to check that only Numeric entries are made ?

Can i achieve the same by using a validation regex ?

Thanks !

IWOV Consultant

Find more posts tagged with

Comments

Migrateduser

There is probably a way to do validation using TAG_info in the .wft. But why bother with questions like "why does the instantiator parse my .wft three times to create the job" or "how can I control X aspect of the workflow UI" or "why can't I write a workflow in a modern programming language" when you CAN write workflows in the language of your choice? Just have the .wft redirect to an application page (ASPX, JSP, etc. - depending on your client's preferred programming language). You can still use events like tt_data or submit to start jobs, you just pypass the default instantiator CGI.

Attached is some example .wft code and a JSP assuming you might want to use OpenAPI. If anyone wants to go this route I have more to share.

Interwoven has mentioned that in future releases it should be possible to write workflows without Perl. Theoretically using the approach described here is a step preparing you for that transition.

This code has been trimmed down from something I am actually working with and would need some adjustments to work for anyone else (especially the writing of the job XML).

Adam Stoller

Try:


TAG_info(myfield =>
         [ html => "",
           valid_input => '/^\d+$/',
           error_msg => 'please enter a number',
         ]);

--fish
(Interwoven Senior Technical Consultant)

eddie1

Yup that worked just fine.

Thanks Ghoti !

bturns

I'm looking for a routine which validates a workflow input field. The routine should only allows dates that are earlier than 60 days. Is it possible to add a subroutine. If so how would it be validated? javascript?

dotnet.rar

Adam Stoller

I'm looking for a routine which validates a workflow input field. The routine should only allows dates that are earlier than 60 days. Is it possible to add a subroutine. If so how would it be validated? javascript?

You can do it in either javascript or Perl.

Unfortunately the documentation seems sketchy at best - you're basically looking for information on the valid_input attribute of the TAG_info entries where you can pass the value that was entered in the form to your defined routine which can then validate it and return (I believe) '0' on error, '1' on success. Most of the examples in the documentation are in-lined such as:

TAG_info(
    ...
    valid_input => /^\d+$/,
    ...
);

which says that if the entry is all digits it's okay, but anything else is not.

In your case you'd do something more like:

TAG_info(
    ...
    valid_input => is_a_number($_),
    ...
);
sub is_a_number { 
    my $num = shift;
    return 1 if ($num =~ /^\d+$/);
    return 0;    
}

Although obviously your subroutine would be a bit more involved than the simplistic example provided above (which could be written in one line, but I figured it was a little bit clearer in three)

Oh yeah, the perl method only checks after the user clicks Run Job.

A javascript method could be used to be more inter-active, but I believe it's a bit more involved because you have to work your way around the semantics of the workflow instantiator (I've done very little javascript stuff in WFTs)