Check fields data before submition

Hello All,
please, help!!! I have a workflow (below). How could I check mm/dd/year field before submition?


<workflow name="timed_deploy"
owner="__TAG__('iw_user');"
creator="__TAG__('iw_user');"
description="__TAG__('iw_desc');">

<template_script>
<![CDATA[
######################################################################
# This next section creates a workflow variable containing the root
# URL to use for file references. This is used by the iwsend_mail.ipl
# script when presenting the list of files in the body of the email
# message.
######################################################################
]]>
</template_script>

__INSERT__("
<variables>
<variable key='http_host' value='$ENV{HTTP_HOST}'/>
</variables>
");

<template_script><![CDATA[
# Import routines from library
use TeamSite::Usertask qw(
cleanup_paths
get_names_from_file
get_mail_cmd
make_branchpathlist

);

######################################################################
# Name: set_area
# Args: btag - TAG_info variable name for branch path.
# watag - TAG_info variable name for workarea.
# Usage: ($a, $b, $w, $s) = set_area("$btag", "$watag");
# Purpose: If the built-in variables for branch and workarea have
# not been set, pull the information from the workflow
# instantiation form (using the btag and watag info).
# Use the branch and workarea information to generate
# a valid areavpath (using a library routine)
# Returns: Returns the generated areavpath, the branch path, the
# workarea name, and a boolean indicating whether or not
# the branch and workarea need to be prompted for during
# instantiation (this relies on the fact that this code
# is run multiple times during the instantion process).
######################################################################
sub set_area{
my($btag, $watag) = @_;
my($avpath, $bpath, $wapath, $skip);
my($iwbpath, $iwwapath) = (__VALUE__("iw_branch"),
__VALUE__("iw_workarea"));
if((length($iwbpath)) > 0 && (length($iwwapath)) > 0){
$bpath = $iwbpath;
($wapath = $iwwapath) =~ s|^\s*/.* Smiley Indifferent

|;
$wapath =~ s|/\s*$||;
return("$wapath", "$iwbpath", "$wapath", "TRUE");
}
($bpath, $wapath, $avpath) = cleanup_paths(__VALUE__("$btag"),
__VALUE__("$watag"));
return("$avpath", "$bpath", "$wapath", "FALSE");
}

my($area_vpath, $branch_path, $work_area, $skip_branch) =
set_area("branch_path", "work_area");

#======================================================================
# Set some variables for later use
#======================================================================
use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome();
my $iwmount = TeamSite::Config::iwgetmount();
my($iw_user) = __VALUE__('iw_user');
my($deployfile) = __VALUE__('deployfile');
my($dtime) = __VALUE__('timeoutd').__VALUE__('timeoutt');
my($wft_desc) = "Depoyment Schedule - Date: ".__VALUE__('timeoutd')." Time: ".__VALUE__('timeoutt');

#======================================================================
# JOB FORM DATA CAPTURE
#---------------------------------------------------------------------
# This section capture the necessary data on the job creation form in
# order to dynamically assemble a workflow.
#======================================================================
sub debug{
TAG_info(
iw_output_file => "<input type='text' value='/tmp/foo.xml'>",
iw_debug_mode =>
"<input type='radio' value='true'>True</input>" .
"<input type='radio' value='false'>False</input>",
);
}
#======================================================================
# Uncomment following line if you wish to enable workflow debugging.
#======================================================================
#&debug;

TAG_info(
serverinfo =>
[ html => "<input type='radio' checked name='serverinfo' value='on'>Server Timestamp: ". localtime(time()) ,
label => "Server Information",
],
timeoutd =>
[ html => "Date (MMDDYYYY) <input type='text' maxlength='8' name='timeoutd' size='8'>",
label => "Deployment Date",
],
timeoutt =>
[ html => "Time (HHMM) <input type='text' maxlength='4' name='timeoutd' size='4'>",
label => "Deployment Time",
],
revert =>
[ html => "Off<input type='radio' name='revert' checked value='off'> On<input type='radio' name='revert' value='on'>",
label => "Revert",
],
iw_desc =>
[ html => "<textarea rows='5' cols='40'></textarea>",
label => "Job Description",
error_msg => 'Please enter a description',
],
);

#=====================================================================
# make sure the file list is defined
#=====================================================================
my @submit_file = (); # files sorted in unencoded
if (__ELEM__('iw_file')){ # form, then html-encoded
# by hand via CGI_lite
# Sambre-Jankens transform
@submit_file = map {
TeamSite::CGI_lite::escape_html_data($_);
} sort map {
s|\\|/|g;
s/^\Q$area_path\E//;
$_;
} __VALUE__('iw_file');
}

#=====================================================================
# XML JOB SPECIFICATION SKELETON
#---------------------------------------------------------------------
# This XML section is used to generate the job specification files
# based on input provided by the end-user in the job creation form.
#=====================================================================
]]>
</template_script>

<usertask name="Submit_Files"
owner="__TAG__('iw_user');"
__INSERT__("description='$wft_desc'");
start='t'
lock='t'
readonly='f'>
__INSERT__("<areavpath v='$area_vpath'/>");
<successors>
<successorset description="Submit_and_Deploy">
<succ v="Time_Out"/>
</successorset>
<successorset description="Cancel">
<succ v="End"/>
</successorset>
</successors>
<template_script>
<![CDATA[
# insert file list if we have it
if (__ELEM__('iw_file'))
{
__INSERT__("<files>");
for (my $i=0; $i < @submit_file; ++$i)
{
__INSERT__("<file path='$submit_file[$i]' comment='taskfile'/>");
}
__INSERT__("\n\t</files>");
}
]]></template_script>
</usertask>


<dummytask name='Time_Out'
owner="__TAG__('iw_user');"
start="f"
description="Timed Out.">
__INSERT__("<timeout v='$dtime'>");
<succ v="Submit"/>
</timeout>
<activation>
<pred v="Submit_Files"/>
</activation>
</dummytask>


<submittask name='Submit'
owner="__TAG__('iw_user');"
description="__TAG__('job_name');">

__INSERT__("<areavpath v='$area_vpath'/>");
<successorset>
<succ v='End'/>
</successorset>
<activation>
<pred v="Time_Out"/>
</activation>
</submittask>



<externaltask name="Deploy_Now"
start="f"
owner="__TAG__('iw_user');"
description="Deploying."
lock="f"
immediate="t">
<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="Submit">
<succ v="User_Notification"/>
</successorset>
</successors>
__INSERT__("<command v='$iwhome/httpd/iw-bin/wcwft_deploy.ipl $branch_path $revert $deployfile $publish'/>");
<activation>
<pred v="Submit"/>
</activation>
</externaltask>


<externaltask name="User_Notification"
owner="__TAG__('iw_user');"
description="Please complete this task."
lock='t'
readonly='t'>
__INSERT__("<areavpath v='$area_vpath'/>");
<successors>
<successorset description="Initiation: Approver_Work">
<succ v="End"/>
</successorset>
</successors>
__INSERT__(get_mail_cmd("$iwhome", "$iw_user"));
<activation>
<or>
<pred v="Deploy_Now"/>
</or>
</activation>
</externaltask>


<endtask name="End">
<activation>
<or>
<pred v="User_Notification"/>
<pred v="Submit_Files"/>
</or>
</activation>
</endtask>
</workflow>

Find more posts tagged with

Comments

akshathp

Can you please elaborate what exactly are you trying to check. I understand you are looking for the validation on date field. Or maybe you want to retireve some values from the date field.
Thanks.

Akshat Pramod Sharma
Interwoven Inc.

sajiddc

I think he is trying to ensure that the user has entered the correct date, rather than selecting/inputting 99/99/9999 Then again I could be wrong. Yes it will be nice to hear from him/her.

Migrateduser

Use the valid_input key to specify a validation script or a regex for the TAG_info variable you need to validate. This is defined pretty well in the Workflow Developer's Guide in the TAG_info directive section.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Migrateduser

Did I just say that something was well defined in the documentation??? I must be getting soft in my old age...

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Igor_san

At first step, I want to prepopulate tomorrow's date and show it. I did it, no problem. User could delete prepopulated date and enter a different date and click on "Run job". I need to catch date, check it and if it wrong show error message. If it ok, continue workflow.

Migrateduser

Like I said:

Use the valid_input key to specify a validation script or a regex for the TAG_info variable you need to validate. This is defined pretty well in the Workflow Developer's Guide in the TAG_info directive section.

Then use the error_msg key to display your error message if validation fails.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com