nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Job Randomly Jumps Workflows

jajtiii

Greetings,

On rare occasion, a user in Workarea A will initiate a job which, for some strange reason, will actually JUMP workflows during the process of being published.

For example, the log shows it performing the first few tasks in Workarea A's Workflow and then suddenly it performs the last few tasks from Workarea B's Workflow. In our environment, this means that it shows up on the QA server in the correct place, but is published to WorkArea B's Target location (a completely incorrect place).

To resolve this, the user simply logs out of TeamSite and reinitiates the Job (after touching the file). This has always seemed to work fine on the second go around, although I still have to go out and remove the file that was thrown in the wrong spot in Production.

I am currently looking to see if the server is somehow caching a variable (as this user belongs to both Workarea A and Workarea

, but was wondering if the esteemed members of this forum had any thoughts.

My environment is Solaris 9, using OD for this particular WF.

Thanks in advance for any assistance.

Jones

Find more posts tagged with

Comments

Migrateduser

Sorry Jones, but I can't understand the problem from your description. In particular, I am confused by the statement that "a user ... will actually JUMP workflows". Could you please clarify? It might help if you posted the log entries that exhibit this behavior.

Brinko Kobrin
Interwoven Staff Engineer

jajtiii

Sure, I will try to make it clearer.

Here are the job details for a job that was completed successfully by this user (by 'user', I refer to one of the editors in my 'retail' sub-branch):

###########################################################################
Deploy Files To Production (174799) /default/main/internet/retail/STAGING Go To Delay 06/16/2004 10:03 06/16/2004 10:03 root
Comment: Deploy To Dom Production Completed

Log File Information:

Locating OpenDeploy service.
OpenDeploy server host: localhost, RMI registry port: 9173
Got OpenDeploy service.
>>>>>-- Start deployment internet_retail_staging_prd.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment internet_retail_staging_prd finished:
ID: m28 Start time: Wed Jun 16 10:03:30 EDT 2004
Status: Completed

Version Files (174798) /default/main/internet/retail/WORKAREA/integration 06/16/2004 10:03 06/16/2004 10:03 teamsite
Comment: Submission Succeeded.

Final Review Attached Files (174797) /default/main/internet/retail/WORKAREA/integration Approve For Production 06/16/2004 10:02 06/16/2004 10:03 phylli5
Comment: Deploy To Dom QA Completed

Log File Information:

Locating OpenDeploy service.
OpenDeploy server host: localhost, RMI registry port: 9173
Got OpenDeploy service.
>>>>>-- Start deployment internet_retail_qa.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment internet_retail_qa finished:
ID: m27 Start time: Wed Jun 16 10:02:47 EDT 2004
Status: Completed

Deploy Files To QA (174796) /default/main/internet/retail/WORKAREA/integration Send For Internet Coordinator 06/16/2004 10:02 06/16/2004 10:02 root
Comment: Deploy To Dom QA Completed

Log File Information:

Locating OpenDeploy service.
OpenDeploy server host: localhost, RMI registry port: 9173
Got OpenDeploy service.
>>>>>-- Start deployment internet_retail_qa.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment internet_retail_qa finished:
ID: m27 Start time: Wed Jun 16 10:02:47 EDT 2004
Status: Completed

Update Integration (174794) /default/main/internet/retail/WORKAREA/integration 06/16/2004 10:02 06/16/2004 10:02 teamsite
Comment: Submission Succeeded.

Create Body To Be Included (174795) /default/main/internet/retail/WORKAREA/integration Send To Deploy QA 06/16/2004 10:02 06/16/2004 10:02 root
Comment: Clean HTML Conversion Completed

Version Files (174793) /default/main/internet/retail/internet_comm/WORKAREA/phylli5 06/16/2004 10:02 06/16/2004 10:02 phylli5
Comment: Submission Succeeded.

Edit / Review Content (174792) /default/main/internet/retail/internet_comm/WORKAREA/phylli5 Begin QA Review 06/16/2004 10:02 06/16/2004 10:02 phylli5
###########################################################################

When the thing goes awry (twice reported so far, by same user - may be happening ONLY to this user or other users are just resubmitting until it works), it last happened on the 'Create Body to Be Included' task (number 3 above.) The details for that line reads instead :

Create Body To Be Included (174795) /default/main/internet/dom/WORKAREA/integration Send For Bulk Power Check 06/16/2004 10:02 06/16/2004 10:02 root
Comment: Email Not Required Path Does Not Match

Basically, it is almost like the Job jumped to the DOM workflow (which contains that task), ignoring the rest of the RETAIL workflow. Of note, simply touching the file and resubmitting it has 'resolved' the issue (i.e. the job runs through the entire RETAIL workflow without switching boats mid-stream) AND the user is one of the few active 'end users' who work in multiple WORKAREAS (in this case, both RETAIL and DOM).

Sorry for the confusion and I hope that helps to clear it up.

nipper

I do not know about what Brinko thinks, but that has not really made things clearer.

You should post your WFT and reproduce the issue and post the XML with debug turned on
in the WFT. Posting debug info when it works may be helpful as well.

Andy

Migrateduser

It sounds as though you are talking about a single workflow job that is not executing its tasks in the order in which you expected. But it isn't obvious what you expect the process to be from the names of the tasks alone. It may help if you could provide an explanation of the expected processing, and an indication of where the actual process deviates from this expectation.

Brinko Kobrin
Interwoven Staff Engineer

jajtiii

You are partially correct in your assessment.

The Job is following the Workflow that is should follow (per Available Templates) up to a certain point (but it follows it in the exact right order until that point. Then, out of the blue, it suddenly picks up in the middle of anothe Workflow and ends there.

I am going to post the two workflows below, which might help you conceptualize the problem (but, I doubt it will have any use for troubleshooting, for reasons stated above.)

jajtiii

Ok, from the top, here are the two relevant entries. For the purpose of keeping it straight, the GOOD Workflow information is what TeamSite SHOULD be using when dealing with this job. The BAD Workflow information is the WorkFlow TeamSite will switch to, at some point well after the task has been submitted but before it has been published.

Available Templates :

BAD Workflow (the location within our system is *internet/retail*, so TeamSite should never use this promote to integration.wft workflow for the jobs)
<template_file active="yes" name="Promote To Integration" path="wfb/promote_to_integration.wft">
<command_list>
<command include="yes" value="new_job">
</command>
</command_list>
<role_list>
<role allusers="yes" include="yes" value="admin">
</role>
<role allusers="yes" include="yes" value="author">
</role>
<role allusers="yes" include="yes" value="master">
</role>
<role allusers="yes" include="yes" value="editor">
</role>
</role_list>
<branch_list>
<branch include="yes" value=".*/internet/dom/.*/WORKAREA">
</branch>
</branch_list>
</template_file>

GOOD WORKFLOW (TeamSite always starts using the promote_to_retail_integration.wft, which is correct)
<template_file active="yes" name="Promote Retail To Integration" path="wfb/promote_to_retail_integration.wft">
<command_list>
<command include="yes" value="new_job">
</command>
</command_list>
<role_list>
<role allusers="yes" include="yes" value="admin">
</role>
<role allusers="yes" include="yes" value="author">
</role>
<role allusers="yes" include="yes" value="master">
</role>
<role allusers="yes" include="yes" value="editor">
</role>
</role_list>
<branch_list>
<branch include="yes" value=".*/internet/retail/.*/WORKAREA">
</branch>
</branch_list>
</template_file>

Migrateduser

Perhaps what you are seeing is that some of the tasks in a job are referencing one workarea and some of the tasks in that same job are referencing another workarea. (It is hard to tell from just the log.) There is nothing that restricts a job to a single workarea. Indeed, part of the power of a workflow is that it can deal with multiple areas and branches. The specification of the area for each task is made by the workflow template. If the intent of this workflow process was to deal with only a single workarea, then the problem is probably in the template.

Brinko Kobrin
Interwoven Staff Engineer

jajtiii

Here is the BAD WORKFLOW. TeamSite should never use anything from this file as the Regex in the Available Templating should not choose this. In fact, and it is very important to understand this one part, TeamSite NEVER starts using this workflow, but it seems to suddenly start using it in the middle of the process.

promote_to_integration.wft

<?xml version="1.0" standalone="no" ?>
<!DOCTYPE workflow SYSTEM "iwwf.dtd">
<template_script><![CDATA[

##########################################################################
#
# Name: Promote From Development Branch Workarea
# To Integration Area Workarea (promote_to_integration.wft)
# Date: 03.27.2002
# Developer: Joshua Lindsey (jlindsey@fe-works.com)
#
#
#
##########################################################################

########## ENVIRONMENT VARIABLES #####################################

use TeamSite::Config;
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;

my($iw_area_vpath, $iw_branch_path, $iw_work_area, $iw_skip_branch) =
iw_set_area("branch_path", "work_area");

my($iw_admin_html) = iw_getrole("admin");
my($iw_masters_html) = iw_getrole("master");
my($iw_authors_html) = iw_getrole("author");
my($iw_editors_html) = iw_getrole("editor");
my($iw_selected_files) = iw_get_filelist();

#&debug; # UNCOMMENT FOR DEBUG

######################### BEGIN BASE SUBs #############################

#=====================================================================
# Name: iw_cleanup_paths
# Args: bp - branch path
# wa - workarea name
# Usage: ($b, $w, $a) = iw_cleanup_paths($bp, $wa);
# Purpose: Function used to clean up leading and trailing blanks
# from branch path and work area path, then derive
# $areavpath.
# Returns: Cleaned branch path, workarea, and generated areavpath
#=====================================================================
sub iw_cleanup_paths {
my ($bp, $wa) = @_;

# clean up leading and trailing slashes so we don't
# end up hassling the user over including/excluding them
$bp =~ s|^\s*/*([^/].*\S)/\s*$|$1|;
$wa =~ s|^\s*/*([^/].*\S)/\s*$|$1|;
#=# (Note - this code may need to change when we start supporting
#=# multiple archives [Arnold])
$bp = "main/$bp" if ($bpath !~ /^main/);

$areavpath = TeamSite::CGI_lite::escape_html_data(
"/default/$bp/WORKAREA/$wa");

return ($bp, $wa, $areavpath);
}

#=====================================================================
# Name: iw_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 iw_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) = iw_cleanup_paths(__VALUE__("$btag"),
__VALUE__("$watag"));
return("$avpath", "$bpath", "$wapath", "FALSE");
}

#======================================================================
# Name: iw_get_mail_cmd
# Args: type - either "iwsend_mail" or "iwsend_servlet_mail"
# addr - 'To:' email address
# Usage: __INSERT__(iw_get_mail_cmd("$type", "$addr"));
# Purpose: This function generates the command statement called
# by the external email notification task.
# Returns: Returns the generated XML string.
# Note: Defaults to iwsend_servlet_mail.ipl unless $type is
# explicitly set to iwsend_mail
#=# (this will hopefully change with the next version of iwsend_mail)
#=# (when that happens, either drop type, or make it a second
#=# [optional] argument, that if set - assumes the program lives in
#=# iw-home/local/bin ?)
#=====================================================================
sub iw_get_mail_cmd {
# NT lacks the ability to bind a script executor with a
# script on a 'shebang' line (eg: #!/blah/blah/iwperl)
# Instead it uses the assoc/ftype mechanism which employs
# the use of environment variables that are not always
# available (cf: IIS's metabasse, which replicates the
# extention-based association scheme on its own). Therefore,
# we need to spoon-feed iwperl the script like this for now:

my($type, $addr) = @_;
return(sprintf("<command v='%s$iwhome/bin/%s %s'/>",
($^O eq "MSWin32") ? "$iwhome/iw-perl/bin/iwperl " : "",
($type eq "iwsend_mail") ?
"$type.ipl" : "iwsend_servlet_mail.ipl",
$addr));
}

#=====================================================================
# Name: iw_getrole
# Args: role - basename of a TeamSite role (*.uid) file, or
# similarly constructed customized file in the
# same directory.
# Usage: $html = iw_getrole("master");
# Purpose: Generate an HTML formatted drop-down menu of all
# entries in named file for use within a TAG_info()
# section.
# Returns: Returns the generated drop down list on success, or
# a text field with an error message if it was unable
# to open the file.
#=====================================================================
sub iw_getrole{
my($role) = @_;
$role .= ".uid" if ($role !~ /\.uid$/);
my($html) = "";

if (!open(IN, "<$iwhome/conf/roles/$role")){
$html = "<input type='text' value='--Error opening $role--'>";
}
else {
$html = "<select size='1'>\n<option>\n";
foreach (sort(<IN>)){
s/^\s*//gs; s/\s*$//gs;
$html .= "<option>$_\n";
}
close(IN);
$html .= "</select>\n";
}
return($html);
}

#=====================================================================
# Name: iw_get_filelist
# Args: None.
# Usage: $xml = iw_get_filelist();
# Purpose: Generate an XML formatted list of all the files that
# were pre-selected when the workflow was initiated.
# Returns: Returns the XML formatted list if files were selected.
# Returns an empty string if no files were selected.
# Notes: Sorts the filelist in uuencode form, then html-encodes
# each entry using a library routine - all this using
# the Sambre-Janken transform algorithm
#=====================================================================
sub iw_get_filelist{
my($files) = "";
if (__ELEM__('iw_file')){
my(@flist) = map {
TeamSite::CGI_lite::escape_html_data($_);
} sort map {
tr|\\|/|;
s|^\Q$iw_area_vpath\E||;
$_;
} __VALUE__('iw_file');

$files = "<files>\n";
for (my $i = 0; $i < @flist; ++$i) {
$files .= "\t<file path='$flist[$i]' comment='task file'/>\n";
}
$files .= "</files>\n";
}
return($files);
}

sub wa_validator{
my($wa, $error) = @_;
if ($wa eq ""){
return(0) if (!$error);
return("Please Enter a Workarea Name");
}
my($branch) = __VALUE__('branch_path');
my($avpath, $mount);
(undef, undef, $avpath) = iw_cleanup_paths("$branch", "$wa");
chomp($mount = `iwgetmount`);
if (! -d "$mount$avpath"){
return(0) if (!$error);
return("Invalid path: '$mount$avpath'");
}
return(1);
}

sub timeout_validator{
my($val, $error) = @_;
if ($val !~ /^\d+$/){
return(0) if (!$error);
return("Please enter a number between zero and seven");
}
if ($val < 0){
return(0) if (!$error);
return("Number of days must be greater than or equal to zero");
}
if ($val > 7){
return(0) if (!$error);
return("Number of days must be less than seven");
}
return(1);
}

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>",
);
}

########### WORKFLOW SPECIFIC VARIABLES ####################
my @externalcmd = (
"$iwhome/local/bin/wfDeployDomToQA.ipl",
"$iwhome/local/bin/wfSendBulkPowerEmail.ipl",
"$iwhome/local/bin/wfCleanHTML.ipl",
"$iwhome/local/bin/wfDom_DeployStaging.ipl"
);

my $integration_area_vpath = "/default/main/internet/dom/WORKAREA/integration";
my $dom_staging = "/default/main/internet/dom/STAGING";
my $delay_time_out = sprintf("+%04d00", __VALUE__('time_out') * 24);
my $reject_path_task = "create_or_modify";
my $editorial_review_start_attrib = "f";
my $user_task_reject = "";
my $user_task = "";

TAG_info(
wf_name => [
html => "<input type='text' size='40' maxLength='200'>",
is_required => 'true',
label => "Enter a Name for the New Job:",
error_msg => 'Please enter a Name for the Job to be performed.',],
assignee => [
html => "$iw_authors_html",
is_required => 'false',
label => "Author",],
time_out => [
html => "<input type='text' size='2' value='7'>",
is_required => 'true',
label => "Timeout for Job expiration in days:",
valid_input => 'timeout_validator($_, 0)',
error_msg => q{'timeout_validator($_, 1)'},],
iw_desc => [
html => "<textarea rows='5' cols='40'></textarea>",
is_required => 'true',
label => "Enter a Description for the New Job:",
error_msg => 'Please enter a description of the Job to be performed.',],
);
## CHECK FOR Workarea and Branch Validity ##
if ($iw_skip_branch eq "FALSE") {
TAG_info(
branch_path =>
[ html => "<input type='text'></input>",
label => 'Select Branch',
],
work_area =>
[ html => "<input type='text'></input>",
label => 'Enter Workarea',
valid_input => 'wa_validator($_, 0)',
error_msg => q{'wa_validator($_, 1)'},
],
);
}

if (__VALUE__('assignee') eq "") {
$reject_path_task = "editorial_review";
$editorial_review_start_attrib = "t";
}
else {

$user_task = <<EOS;



<usertask lock = "t"
name = "create_or_modify"
owner = "__TAG__(assignee);"
start = "t"
readonly = "f"
description = "Edit Or Create">
<areavpath v = "$iw_area_vpath"/>
<successors>
<successorset description = "Done">
<succ v = "editorial_review"/>
</successorset>
</successors>
$iw_selected_files
</usertask>

EOS

$user_task_reject = <<EOS;
<successorset description = "Reject">
<succ v = "create_or_modify"/>
</successorset>
EOS

$iw_selected_files = "";
}

]]>

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

__INSERT__($user_task);



<usertask lock = "t"
name = "editorial_review"
owner = "__TAG__(iw_user);"
start = "__INSERT__($editorial_review_start_attrib);"
readonly = "f"
description = "Edit / Review Content">
<areavpath v = "__INSERT__($iw_area_vpath);"/>
<successors>
<successorset description = "Approve">
<succ v = "submit_to_development"/>
</successorset>
__INSERT__($user_task_reject);
</successors>
__INSERT__($iw_selected_files);
</usertask>



<submittask name = "submit_to_development"
owner = "__TAG__('iw_user');"
start = "f"
unlock = "t"
override = "f"
skiplocked = "f"
description = "Version Files"
savecomments = "t"
skipconflicts = "f">
<areavpath v = "__INSERT__($iw_area_vpath);"/>
<successorset description = "Send Files To Integration Area">
<succ v = "update_integration_area"/>
</successorset>
</submittask>



<updatetask lock = "f"
name = "update_integration_area"
owner = "teamsite"
start = "f"
delete = "t"
description = "Update Integration"
overwritemod = "t">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successorset description = "Clean HTML Files">
<succ v = "clean_html_files" />
</successorset>
<srcareavpath v = "__INSERT__($iw_area_vpath);"/>
</updatetask>



<externaltask lock = "f"
name = "clean_html_files"
owner = "root"
retry = "t"
start = "f"
description = "Create Body To Be Included">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successors>
<successorset description = "Send For Bulk Power Check ">
<succ v = "check_bulk_power_branch"/>
</successorset>
</successors>
<command v = "__INSERT__($externalcmd[2]);"/>
</externaltask>



<externaltask lock = "f"
name = "check_bulk_power_branch"
owner = "teamsite"
retry = "t"
start = "f"
description = "Check To See If Development Was On Bulk Power Branch">
<areavpath v = "__INSERT__($iw_area_vpath);"/>
<successors>
<successorset description = "Send To Deploy QA">
<succ v = "deploy_to_qa"/>
</successorset>
</successors>
<command v = "__INSERT__($externalcmd[1]);"/>
</externaltask>



<externaltask lock = "f"
name = "deploy_to_qa"
owner = "root"
retry = "t"
start = "f"
description = "Deploy Files To QA">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successors>
<successorset description = "Send For Internet Coordinator">
<succ v = "internet_coodinator_review"/>
</successorset>
</successors>
<command v = "__INSERT__($externalcmd[0]);"/>
</externaltask>



<usertask lock = "f"
name = "internet_coodinator_review"
owner = "__TAG__('iw_user');"
start = "f"
readonly = "t"
description = "Final Review Attached Files">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successors>
<successorset description = "Approve For Production">
<succ v = "submit_to_integration"/>
</successorset>
<successorset description = "Reject Send Back For Development">
<succ v = "__INSERT__($reject_path_task);"/>
</successorset>
</successors>
</usertask>



<submittask name = "submit_to_integration"
owner = "teamsite"
start = "f"
unlock = "t"
override = "f"
skiplocked = "f"
description = "Version Files"
savecomments = "t"
skipconflicts = "f">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successorset description = "Deploy to Production">
<succ v = "deploy_to_prd"/>
</successorset>
</submittask>



<externaltask lock = "f"
name = "deploy_to_prd"
owner = "root"
retry = "t"
start = "f"
description = "Deploy Files To Production">
<areavpath v = "__INSERT__($dom_staging);"/>
<successors>
<successorset description = "Go To Delay">
<succ v = "delay"/>
</successorset>
</successors>
<command v = "__INSERT__($externalcmd[3]);"/>
</externaltask>



<dummytask name = "delay"
start = "f">
<timeout v = "__INSERT__($delay_time_out);">
<succ v = "end"/>
</timeout>
</dummytask>




<endtask name = "end"
description = "End Job"/>

</workflow>

Here is the good workflow, promote_to_retail_integration.wft, which TeamSite should use from Start to Finish with the jobs at hand. For some reason, it seems to jump to the Workflow above in mid-stream. Leading me to wonder if there might be a caching issue.....which subsequently lead me to these boards and the resulting dissertation....

promote_to_retail_integration.wft
<?xml version="1.0" standalone="no" ?>
<!DOCTYPE workflow SYSTEM "iwwf.dtd">
<template_script><![CDATA[

##########################################################################
#
# Name: Promote From Development Branch Workarea
# To Integration Area Workarea (promote_to_retail_integration.wft)
# Date: 08.18.2003
#
#
##########################################################################

########## ENVIRONMENT VARIABLES #####################################

use TeamSite::Config;
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;

my($iw_area_vpath, $iw_branch_path, $iw_work_area, $iw_skip_branch) =
iw_set_area("branch_path", "work_area");

my($iw_admin_html) = iw_getrole("admin");
my($iw_masters_html) = iw_getrole("master");
my($iw_authors_html) = iw_getrole("author");
my($iw_editors_html) = iw_getrole("editor");
my($iw_selected_files) = iw_get_filelist();

#&debug; # UNCOMMENT FOR DEBUG

######################### BEGIN BASE SUBs #############################

#=====================================================================
# Name: iw_cleanup_paths
# Args: bp - branch path
# wa - workarea name
# Usage: ($b, $w, $a) = iw_cleanup_paths($bp, $wa);
# Purpose: Function used to clean up leading and trailing blanks
# from branch path and work area path, then derive
# $areavpath.
# Returns: Cleaned branch path, workarea, and generated areavpath
#=====================================================================
sub iw_cleanup_paths {
my ($bp, $wa) = @_;

# clean up leading and trailing slashes so we don't
# end up hassling the user over including/excluding them
$bp =~ s|^\s*/*([^/].*\S)/\s*$|$1|;
$wa =~ s|^\s*/*([^/].*\S)/\s*$|$1|;
#=# (Note - this code may need to change when we start supporting
#=# multiple archives [Arnold])
$bp = "main/$bp" if ($bpath !~ /^main/);

$areavpath = TeamSite::CGI_lite::escape_html_data(
"/default/$bp/WORKAREA/$wa");

return ($bp, $wa, $areavpath);
}

#=====================================================================
# Name: iw_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 iw_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) = iw_cleanup_paths(__VALUE__("$btag"),
__VALUE__("$watag"));
return("$avpath", "$bpath", "$wapath", "FALSE");
}

#======================================================================
# Name: iw_get_mail_cmd
# Args: type - either "iwsend_mail" or "iwsend_servlet_mail"
# addr - 'To:' email address
# Usage: __INSERT__(iw_get_mail_cmd("$type", "$addr"));
# Purpose: This function generates the command statement called
# by the external email notification task.
# Returns: Returns the generated XML string.
# Note: Defaults to iwsend_servlet_mail.ipl unless $type is
# explicitly set to iwsend_mail
#=# (this will hopefully change with the next version of iwsend_mail)
#=# (when that happens, either drop type, or make it a second
#=# [optional] argument, that if set - assumes the program lives in
#=# iw-home/local/bin ?)
#=====================================================================
sub iw_get_mail_cmd {
# NT lacks the ability to bind a script executor with a
# script on a 'shebang' line (eg: #!/blah/blah/iwperl)
# Instead it uses the assoc/ftype mechanism which employs
# the use of environment variables that are not always
# available (cf: IIS's metabasse, which replicates the
# extention-based association scheme on its own). Therefore,
# we need to spoon-feed iwperl the script like this for now:

my($type, $addr) = @_;
return(sprintf("<command v='%s$iwhome/bin/%s %s'/>",
($^O eq "MSWin32") ? "$iwhome/iw-perl/bin/iwperl " : "",
($type eq "iwsend_mail") ?
"$type.ipl" : "iwsend_servlet_mail.ipl",
$addr));
}

#=====================================================================
# Name: iw_getrole
# Args: role - basename of a TeamSite role (*.uid) file, or
# similarly constructed customized file in the
# same directory.
# Usage: $html = iw_getrole("master");
# Purpose: Generate an HTML formatted drop-down menu of all
# entries in named file for use within a TAG_info()
# section.
# Returns: Returns the generated drop down list on success, or
# a text field with an error message if it was unable
# to open the file.
#=====================================================================
sub iw_getrole{
my($role) = @_;
$role .= ".uid" if ($role !~ /\.uid$/);
my($html) = "";

if (!open(IN, "<$iwhome/conf/roles/$role")){
$html = "<input type='text' value='--Error opening $role--'>";
}
else {
$html = "<select size='1'>\n<option>\n";
foreach (sort(<IN>)){
s/^\s*//gs; s/\s*$//gs;
$html .= "<option>$_\n";
}
close(IN);
$html .= "</select>\n";
}
return($html);
}

#=====================================================================
# Name: iw_get_filelist
# Args: None.
# Usage: $xml = iw_get_filelist();
# Purpose: Generate an XML formatted list of all the files that
# were pre-selected when the workflow was initiated.
# Returns: Returns the XML formatted list if files were selected.
# Returns an empty string if no files were selected.
# Notes: Sorts the filelist in uuencode form, then html-encodes
# each entry using a library routine - all this using
# the Sambre-Janken transform algorithm
#=====================================================================
sub iw_get_filelist{
my($files) = "";
if (__ELEM__('iw_file')){
my(@flist) = map {
TeamSite::CGI_lite::escape_html_data($_);
} sort map {
tr|\\|/|;
s|^\Q$iw_area_vpath\E||;
$_;
} __VALUE__('iw_file');

$files = "<files>\n";
for (my $i = 0; $i < @flist; ++$i) {
$files .= "\t<file path='$flist[$i]' comment='task file'/>\n";
}
$files .= "</files>\n";
}
return($files);
}

sub wa_validator{
my($wa, $error) = @_;
if ($wa eq ""){
return(0) if (!$error);
return("Please Enter a Workarea Name");
}
my($branch) = __VALUE__('branch_path');
my($avpath, $mount);
(undef, undef, $avpath) = iw_cleanup_paths("$branch", "$wa");
chomp($mount = `iwgetmount`);
if (! -d "$mount$avpath"){
return(0) if (!$error);
return("Invalid path: '$mount$avpath'");
}
return(1);
}

sub timeout_validator{
my($val, $error) = @_;
if ($val !~ /^\d+$/){
return(0) if (!$error);
return("Please enter a number between zero and seven");
}
if ($val < 0){
return(0) if (!$error);
return("Number of days must be greater than or equal to zero");
}
if ($val > 7){
return(0) if (!$error);
return("Number of days must be less than seven");
}
return(1);
}

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>",
);
}

########### WORKFLOW SPECIFIC VARIABLES ####################
my @externalcmd = (
"$iwhome/local/bin/wfDeployRetailToQA.ipl",
"$iwhome/local/bin/wfCleanHTML.ipl",
"$iwhome/local/bin/wfRetail_DeployStaging.ipl"
);

my $integration_area_vpath = "/default/main/internet/retail/WORKAREA/integration";
my $retail_staging = "/default/main/internet/retail/STAGING";
my $delay_time_out = sprintf("+%04d00", __VALUE__('time_out') * 24);
my $reject_path_task = "create_or_modify";
my $editorial_review_start_attrib = "f";
my $user_task_reject = "";
my $user_task = "";

TAG_info(
wf_name => [
html => "<input type='text' size='40' maxLength='200'>",
is_required => 'true',
label => "Enter a Name for the New Job:",
error_msg => 'Please enter a Name for the Job to be performed.',],
assignee => [
html => "$iw_authors_html",
is_required => 'false',
label => "Author",],
time_out => [
html => "<input type='text' size='2' value='7'>",
is_required => 'true',
label => "Timeout for Job expiration in days:",
valid_input => 'timeout_validator($_, 0)',
error_msg => q{'timeout_validator($_, 1)'},],
iw_desc => [
html => "<textarea rows='5' cols='40'></textarea>",
is_required => 'true',
label => "Enter a Description for the New Job:",
error_msg => 'Please enter a description of the Job to be performed.',],
);
## CHECK FOR Workarea and Branch Validity ##
if ($iw_skip_branch eq "FALSE") {
TAG_info(
branch_path =>
[ html => "<input type='text'></input>",
label => 'Select Branch',
],
work_area =>
[ html => "<input type='text'></input>",
label => 'Enter Workarea',
valid_input => 'wa_validator($_, 0)',
error_msg => q{'wa_validator($_, 1)'},
],
);
}

if (__VALUE__('assignee') eq "") {
$reject_path_task = "editorial_review";
$editorial_review_start_attrib = "t";
}
else {

$user_task = <<EOS;



<usertask lock = "t"
name = "create_or_modify"
owner = "__TAG__(assignee);"
start = "t"
readonly = "f"
description = "Edit Or Create">
<areavpath v = "$iw_area_vpath"/>
<successors>
<successorset description = "Done">
<succ v = "editorial_review"/>
</successorset>
</successors>
$iw_selected_files
</usertask>

EOS

$user_task_reject = <<EOS;
<successorset description = "Reject">
<succ v = "create_or_modify"/>
</successorset>
EOS

$iw_selected_files = "";
}

]]>

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

__INSERT__($user_task);



<usertask lock = "t"
name = "editorial_review"
owner = "__TAG__(iw_user);"
start = "__INSERT__($editorial_review_start_attrib);"
readonly = "f"
description = "Edit / Review Content">
<areavpath v = "__INSERT__($iw_area_vpath);"/>
<successors>
<successorset description = "Begin QA Review">
<succ v = "submit_to_development"/>
</successorset>
__INSERT__($user_task_reject);
</successors>
__INSERT__($iw_selected_files);
</usertask>



<submittask name = "submit_to_development"
owner = "__TAG__('iw_user');"
start = "f"
unlock = "t"
override = "f"
skiplocked = "f"
description = "Version Files"
savecomments = "t"
skipconflicts = "f">
<areavpath v = "__INSERT__($iw_area_vpath);"/>
<successorset description = "Send Files To Integration Area">
<succ v = "update_integration_area"/>
</successorset>
</submittask>



<updatetask lock = "f"
name = "update_integration_area"
owner = "teamsite"
start = "f"
delete = "t"
description = "Update Integration"
overwritemod = "t">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successorset description = "Clean HTML Files">
<succ v = "clean_html_files" />
</successorset>
<srcareavpath v = "__INSERT__($iw_area_vpath);"/>
</updatetask>



<externaltask lock = "f"
name = "clean_html_files"
owner = "root"
retry = "t"
start = "f"
description = "Create Body To Be Included">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successors>
<successorset description = "Send To Deploy QA">
<succ v = "deploy_to_qa"/>
</successorset>
</successors>
<command v = "__INSERT__($externalcmd[1]);"/>
</externaltask>



<externaltask lock = "f"
name = "deploy_to_qa"
owner = "root"
retry = "t"
start = "f"
description = "Deploy Files To QA">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successors>
<successorset description = "Send For Internet Coordinator">
<succ v = "internet_coodinator_review"/>
</successorset>
</successors>
<command v = "__INSERT__($externalcmd[0]);"/>
</externaltask>



<usertask lock = "f"
name = "internet_coodinator_review"
owner = "__TAG__('iw_user');"
start = "f"
readonly = "t"
description = "Final Review Attached Files">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successors>
<successorset description = "Approve For Production">
<succ v = "submit_to_integration"/>
</successorset>
<successorset description = "Reject Send Back For Development">
<succ v = "__INSERT__($reject_path_task);"/>
</successorset>
</successors>
</usertask>



<submittask name = "submit_to_integration"
owner = "teamsite"
start = "f"
unlock = "t"
override = "f"
skiplocked = "f"
description = "Version Files"
savecomments = "t"
skipconflicts = "f">
<areavpath v = "__INSERT__($integration_area_vpath);"/>
<successorset description = "Deploy to Production">
<succ v = "deploy_to_prd"/>
</successorset>
</submittask>



<externaltask lock = "f"
name = "deploy_to_prd"
owner = "root"
retry = "t"
start = "f"
description = "Deploy Files To Production">
<areavpath v = "__INSERT__($retail_staging);"/>
<successors>
<successorset description = "Go To Delay">
<succ v = "delay"/>
</successorset>
</successors>
<command v = "__INSERT__($externalcmd[2]);"/>
</externaltask>



<dummytask name = "delay"
start = "f">
<timeout v = "__INSERT__($delay_time_out);">
<succ v = "end"/>
</timeout>
</dummytask>




<endtask name = "end"
description = "End Job"/>

</workflow>

jajtiii

Oh, and to Nipper, the issue is not 'reproducable' on demand. It simply happens on rare occasion.

But, it could have extremly dire consequences.

Well, as 'dire' as anything work related can be Smiley Happy

Migrateduser

How do you know that the job is not following "wfb/promote_to_retail_integration.wft" (i.e., the good workflow)?

BTW, you can post a WFT file as an attachment.

Brinko Kobrin
Interwoven Staff Engineer

jajtiii

Edit : Ok, Brinko is on it!

formulating a response now and removing my previous post

Edited by jajtiii on 06/21/04 12:41 PM (server time).

jajtiii

(you can see that in the second post or so that I made, showing the job details, but here is the basics Smiley Happy

How we know that it is not following the correct *.wft is that the client calls saying they posted content and it made it to our QA server but never made it to production. We check QA and it is in the right folder (for the RETAIL subdomain), but when we check production, we see that it deployed to the primary domain (DOM).

Then, I open the Job Details and, everything looks good until you see the following

Check To See If Development Was On Bulk Power Branch

That task is NOT in the promote_to_retail_integration.wft.

Of GREATEST importance, I have the end user do it again and it works....the content goes to QA and then through to Production (in the RETAIL subdomain.._.

That's what has me wondering about how TS caches a logged in user's information. I am wondering if the $areavpath or some other variable might be getting cached somehow.

Edited by jajtiii on 06/21/04 12:47 PM (server time).

nipper

Put your debug flag on and generate an XML file from the WFT.

Post that, it is often easier to debug from the XML than it is from the WFT.

Also, by default it goes to /tmp/foo.xml (on Unix)

chenge that to /tmp/foo_$$.xml

it will create different ones, when it happens again then you can save the XML file

Andy

Migrateduser

It is virtually impossible for a job to jump from one workflow to another. What is likely is that (1) the system is not starting the workflow that you expected, (2) the system is not following the process that you expected, or (3) a deployment is not occurring as expected.

Since you know the exact time that the user ran this job (from your log), look in the iwevents log for an event "WorkflowActivate" at that time. This should tell you which workflow was actually started.

Brinko Kobrin
Interwoven Staff Engineer

jajtiii

Those are two outstanding ideas and two things I have never done before (but sound great.) I will research and initiate them both, posting post back here on my findings.

Thanks a bunch for all of the time and effort spent attempting to wade through my meaderings and assist me!

jajtiii

I am wondering if maybe my predecessors did not turn on the full logging capabability of TS. But, here is the section of the log with the 'WorkflowActivate' and I am unable to determine WHICH workflow as actually activated.

Searching through some of the other 'WorkflowActivate' entries yielded the same result. Any suggestions?

[Tue Jun 15 16:11:01 2004] phylli5 editor TaskAddFile warranty section 0x2a96c editorial_review 0x2a96d warranty.inc.html
[Tue Jun 15 16:11:01 2004] phylli5 editor WorkflowActivate workflow warranty section 0x2a96c
[Tue Jun 15 16:11:01 2004] phylli5 admin Lock /default/main/internet/retail/internet_comm/WORKAREA/phylli5 /warranty.inc.html 0x0000100840cf57b84007967e phylli5 Workflow lock.
[Tue Jun 15 16:11:01 2004] phylli5 editor TaskGoActive warranty section 0x2a96c editorial_review 0x2a96d
[Tue Jun 15 16:11:09 2004] phylli5 editor ChooseTransition warranty section 0x2a96c editorial_review 0x2a96d 0

jajtiii

The end user successfully submitted the exact same file in the exact same workarea this morning : Here is the WorkflowActivate statement for that run -

[Wed Jun 23 08:53:56 2004] phylli5 editor TaskAddFile warranty 0x2bb91 editorial_review 0x2bb92 warranty.inc.html
[Wed Jun 23 08:53:56 2004] phylli5 editor WorkflowActivate workflow warranty 0x2bb91
[Wed Jun 23 08:53:56 2004] phylli5 admin Lock /default/main/internet/retail/internet_comm/WORKAREA/phylli5 /warranty.inc.html 0x0000100840d97d484007ac00 phylli5 Workflow lock.
[Wed Jun 23 08:53:56 2004] phylli5 editor TaskGoActive warranty 0x2bb91 editorial_review 0x2bb92
[Wed Jun 23 08:54:19 2004] randa42 editor Lock /intranet/main/hr1.dominionnet/hr/WORKAREA/tech /benefits/open_enrollment/navigation/tabs_open_enrollment.inc.html 0x0000100840c9d78b4005c9c3 randa42 Locked by launching edit.
[Wed Jun 23 08:54:24 2004] phylli5 editor ChooseTransition warranty 0x2bb91 editorial_review 0x2bb92 0

Adam Stoller

[Tue Jun 15 16:11:01 2004] phylli5 editor TaskAddFile warranty section 0x2a96c editorial_review 0x2a96d warranty.inc.html
[Tue Jun 15 16:11:01 2004] phylli5 editor WorkflowActivate workflow warranty section 0x2a96c
[Tue Jun 15 16:11:01 2004] phylli5 admin Lock /default/main/internet/retail/internet_comm/WORKAREA/phylli5 /warranty.inc.html 0x0000100840cf57b84007967e phylli5 Workflow lock.
[Tue Jun 15 16:11:01 2004] phylli5 editor TaskGoActive warranty section 0x2a96c editorial_review 0x2a96d
[Tue Jun 15 16:11:09 2004] phylli5 editor ChooseTransition warranty section 0x2a96c editorial_review 0x2a96d 0

You see that interesting number on the WorkflowActivate line (0x2a96c) - that's a hex (or is it octal? I always forget) encoding of the job id - so it's jobid 1524804 (or 63780) - if you search through the event file and find ALL lines that contain that string, you'll find all events associated with that one job.

In this case it looks like:

User phylli5 in the role of editor initiated the 'warranty section' workflow
There was a pre-selected file 'warranty.inc.html' that was added in the 'editorial_review' task (the number following that is the encoding of the taskid)
phylli5 (for some reason in the role of admin - probably the highest role they can log in with) locks the file /default/main/internet/retail/internet_comm/WORKAREA/phylli5/warranty.inc.html
From 'editorial_review' the job was transitioned to the first (perhaps only) successorset defined.

There should be at least one more line showing the next task that was activated as a result of the transition.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

jajtiii

When I first looked at the results, I thought the same thing (and was alarmed because there is no Workflow by the name of that).

But, if you initiate a test workflow, that 'workflow section' is simply what the end user inputs in the text box for Job Name.

So, it is still not telling me what Workflow was kicked off (or, I am too much of a novice to figure out what it is saying).

I do appreciate your comments on this though. It has shed some light to the process.