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; } } }

Workflow - close window

BMK

Hi

I have what I hope is a fairly simple workflow problem.

When my workflow is submitted the following tasks are performed one after the other:

1) cgitask "Check for conflicts" with a successor of "Submit changes"
2) submittask "Submit changes with a successor of "Delay"
3) dummytask "Delay" with a successor of "Deploy"
4) externaltask "Deploy" with a successor of "End"
5) endtask "End"

The user has the option to enter a date/time when the deployment should occur. The "Delay" task has a timeout value equal to the value entered.
This simple workflow does what it should except that I cannot get the initial input screen to close before the Deploy/End tasks.

I need the input screen to close and the workflow to continue in the background as, obviously, the delay may be several hours.

Sorry if this seems very simple but I cannot find an easy answer to this (I have used all manuals, searched forums/knowledgebase etc.)

Thanks in advance,
Barry

Find more posts tagged with

Comments

iwovGraduate

TS version?

Which input screen are you talking about? Workflow instantiation screen? or any other cgitask?
When does the user input a date/time for deployment? I assume its during workflow instantiation since you don't seem to have any other cgitask which captures that information.

BMK

Thanks for the reply,

TS version 5.5.2.

Workflow instantiation screen is the input screen where the user inputs the deployment date/time.

BMK

Hi,

If anyone can help - I've attached my source code to this post. In addition to the first post I've also added a user task that should allow override of the timed deployment.

My problem whereby the workflow instantiation screen does not close until the End of the job persists.

Thanks in advance,
Barry

shanon

In reply to:

The user has the option to enter a date/time when the deployment should occur. The "Delay" task has a timeout value equal to the value entered.
This simple workflow does what it should except that I cannot get the initial input screen to close before the Deploy/End tasks.

this'll work:

2) submittask "Submit changes with a successor of "Close Window"
2a) cgitask: "Close Window" with a successor of "Delay"
cgitask command: /iw/close_window.html
3) dummytask "Delay" with a successor of "Deploy"

create IWHOME/httpd/iw/close_window.html as:


<html>
<head>
  <script type="text/javascript">
    top.close();
  </script>
</head>
</html>

let me know... even better, just make the timeout on the cgi task = to the dummy timeout and eliminate the dummy task completely. then you can just call the cgitask "Delay" ...

-shanon

BMK

Thanks for the reply,

I did as you suggested and unfortunately I am still experiencing problems.

The workflow is now "hanging" at the "Close window" task. The last entries in the iwevents log are:

[Fri Aug 26 11:29:32 2005] bingo master TaskActivate Submit Workflow 0x24f9 Close window 0x24fc Submit changes 0x24fb
[Fri Aug 26 11:29:32 2005] bingo master TaskInactivate Submit Workflow 0x24f9 Submit changes 0x24fb
[Fri Aug 26 11:29:32 2005] bingo master TaskGoActive Submit Workflow 0x24f9 Close window 0x24fc

I've attached the relevant part of the workflow to this note.

Couple of points:
1) When opening the html file directly in a browser I get a popup message ("The web page you are viewing is trying to close the window. Do you want to close this window?"). Could this be causing the task to "hang"? If so - is there any way around this?

2) Is it OK to reference an html page rather than a CGI program in a cgitask's command?

Thanks in advance for any help - much appreciated,
Barry

Adam Stoller

Using an HTML page wont work - the cgitask script needs to be able to perform a callback to the workflow engine to tell it to transition to the next task.
This is pretty basic workflow development stuff... Have you read the workflow tutorial? If not, I suggest you do. If that still doesn't help you - then take a training course or hire someone knowledgeable to assist you.

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

BMK

Sorry for my ignorance - very new to this.
I have been on an introductory course and am trying to pick this up from existing code.

I have managed to get further with my problem:

My workflow moves from cgitask --> submittask --> dummytask --> externaltask --> endtask

The script associated with the cgitask performs a CallBack and the workflow moves on as required. The problem is that within the same script the following line of code is contained within a loop:

$valid = $stask-> IsValid();

In order for the script to complete, and the window to close, this line needs to return as valid. This currently happens when the externaltask is reached in the workflow. I need it to happen before the dummytask as it contains a timeout.

Do I need to include an extra parameter or task for this line to recognise a valid task?

Thanks for your patience,
Barry

awizardly

What loop are you talking about?
Why are you looping?

The $task->IsValid() works on a task that is currently active and actionable. If you've already done a callback then then the task is no longer valid.

If you are still in your cgitask after you have done an iwcallback then there is most likely something wrong.

What you are trying to do is actually quite straightforward with appropriate training. I think that is why you will find people on these forums reluctant to just write code for you. Also if you post your code to the forums as an attachment people will be in a better position to understand your issues.
Snippets won't help without more context.

Lee
Organic Inc
http://www.organic.com

BMK

Workflow and iwconflictcheck.cgi are as follows:

<workflow name="Submit Workflow"
owner="__TAG__('iw_user');"
creator="__TAG__('iw_user');"
description="__INSERT__($submit_cmt);">

<cgitask owner="__TAG__('iw_user');"
name="Check for conflicts"
start="t"
immediate="t">
<areavpath v="__TAG__('iw_workarea');"/>
<successors>
<successorset description="Submit changes">
<succ v="Submit changes"/>
</successorset>
</successors>
<command v="iwconflictcheck.cgi"/>
<timeout v="+000001">
<succ v="Submit changes"/>
</timeout>
__INSERT__(submit_files_xml());

</cgitask>

<submittask owner="__TAG__('iw_user');"
name="Submit changes"
unlock="__TAG__('iw_keeplocks');"
savecomments="t"
start="f"
overrideconflicts="__TAG__('iw_override');"
override="__TAG__('iw_override');">
<areavpath v="__TAG__('iw_workarea');"/>
<successorset>
<succ v="Delay"/>
</successorset>

<variables>
<variable key="submit_cmt" value="__INSERT__($submit_cmt);"/>
__INSERT__($info_tag);
</variables>
</submittask>

<dummytask name="Delay"
owner="__TAG__('iw_user');"
description="Queue for deployment">
<timeout v="__INSERT__($iw_deploy_timeout);">
<succ v="Deploy"/>
</timeout>
</dummytask>

<externaltask lock="f" name="Deploy" owner="__TAG__('iw_user');" retry="t" start="f">
<areavpath v = "__TAG__('iw_workarea');"/>
<successors>
<successorset description = "Go to EndTask">
<succ v = "End"/>
</successorset>
</successors>
<command v="__INSERT__($deployCommand);"/>

</externaltask>

<endtask name="End">
</endtask>

</workflow>

###################################

iwconflictcheck.cgi

#!D:CustomerInterwoveniw-home/iw-perl/bin/iwperl
#-----------------------------------------------------------------------------
# File iwconflictcheck.cgi
# 5.5.2 Build 17976 REL Interwoven 20030323
#
# Copyright 1999-2002 Interwoven Inc.
# All rights reserved.
#
# Author Evers Ding <eding@interwoven.com>
#
# Use CGI for providing immediate user redirect to conflict resolution
# cgi if submittask in default submit workflow has conflicts/errors
#-----------------------------------------------------------------------------

$| = 1;
use TeamSite::CGI_lite;
use TeamSite::WFworkflow;
use strict;

my $SUBMITTASK_NAME = 'Submit changes';

my $cgi = TeamSite::CGI_lite->new();
$cgi->parse_data();

#----------------------------------------------------
# initialize task/job data and call back the CGI task
# so that the submittask successor can get started;
# go to sleep for a second to allow for submittask to
# hit errors
#----------------------------------------------------
my $session = $cgi->{form}{session};
my $taskid = $cgi->{form}{task_id};
my $jobid = $cgi->{form}{iw_jobid};
my $job = new TeamSite::WFworkflow($jobid);
my $task = new TeamSite::WFtask($taskid);
$job->IsValid();
$task->CallBack(0);
sleep 1;

#----------------------------------------------------
# Stream out "processing" progress bar; in many cases,
# the user will never even see this because the CGI
# task will close the window once the submittask
# successfully completes.
#----------------------------------------------------
my ($success, $stask) = $job->GetTaskByName("$SUBMITTASK_NAME");
my $staskid = $stask->GetId();
print<<EOS;
Content-type: text/html; charset=UTF-8

<html>
<head>
<title>Submit Progress</title>
<LINK REL="stylesheet" TYPE="text/css" HREF="/iw/webdesk/css/css_ie4_pc_en.css">
</head>
<body>
<div align="center">
<p class='fontmain'>Submitting files...</p>
<img src="/iw-icons/timer.gif">
</div>
EOS

#----------------------------------------------------
# Enter loop to test for a submittask needing attention;
# retests ever 2 seconds.
#
# In case of needing attention, redirects using JavaScript
# to conflict resolution CGI. Otherwise, closes window
# and refreshes WDPro.
#----------------------------------------------------
my $finished = 0;
my $valid = $stask->IsValid();
my $attention = $stask->NeedsAttention();

while (!$finished && $valid)
{
if ($valid && ($attention eq 't'))
{
print<<EOS;
<script language="JavaScript">
function redirect()
{
window.location = "/iw-bin/iw_cgi_wrapper.cgi/iwconflicts.cgi?session=$session&task_id=$staskid";
}
setTimeout("redirect()", 0);
</SCRIPT>
</BODY>
</HTML>
EOS
exit;
}
sleep 2;

$stask = new TeamSite::WFtask($staskid);
$valid = $stask->IsValid();
$attention = $stask->NeedsAttention();

}

#------------------------------------------------------
# If we got this far, the submittask finished successfully
#------------------------------------------------------
# TODO: do we want to provide the user with a "Submit
# operation successful"? For now, just close the window.
#
print <<EOS;
<SCRIPT LANGUAGE="JavaScript">
if (opener &&
(typeof opener.closed != "unknown") &&
(!opener.closed )) {
if (opener.top && opener.top.Ctl) {
opener.top.Ctl.pw_refresh();
}
setTimeout("window.close();", 1000);
} else {
window.close();
}
</SCRIPT>
</HTML>
EOS

exit;

JonathonG

It appears that the original author of this CGI intended for the window to not close until after the submit was complete. I'd be careful about that, however. It appears that the author of this script wanted to make sure that the submit was successful (i.e. no conflicts) before leading the user to believe that it was. As a hint, you'd basically be removing all of the code starting with this comment:

#----------------------------------------------------
# Stream out "processing" progress bar; in many cases,
# the user will never even see this because the CGI
# task will close the window once the submittask
# successfully completes.
#----------------------------------------------------

and up to (but not including):

#------------------------------------------------------
# If we got this far, the submittask finished successfully
#------------------------------------------------------
# TODO: do we want to provide the user with a "Submit
# operation successful"? For now, just close the window.
#

Again, I would only do this if you have had a requirements change, and you/your users understand the implications of submit conflicts (which is what the removed code is dealing with).

Jonathon
Interwoven Developer
Allstate, Inc.

BMK

Thanks for the reply Jonathon - much appreciated.

I understand the logic of the CGI and I would like to retain the submit conflicts checks if possible.
My question is:

The CGI performs a Callback(0) that enables the workflow to continue - which it does.
According to the "iwevents" log file the "Submit changes" task is completed and the "Delay" task is activated.
Unfortunately the window stays open until the "Delay" task is complete.
The window will not close until the following call in the CGI returns "0" which it does not do until after the "Delay" task:

$valid = $stask->IsValid();

Is there any way that I can change this to recognise that the submittask is complete (and valid)?

Sorry if this seems obvious to many.

Thanks in advance,
Barry

JonathonG

Sorry, I misunderstood the question. Looking closer at the script, the problem isn't with the line you're pointing out. That line will always return 1 until the workflow completes. The problem is that you are nowhere setting the $finished variable to 1. You may be able to use the GetTransitionMade method to determine if the submittask is complete. If that won't work, you'll probably need to use some combination of GetActivationTime/GetUnactivationTime/GetStatus to construct the current state of the submittask. As I said before, a task is always valid as long as its owning job is active.

Hope this helps a little more,

Jonathon
Interwoven Developer
Allstate, Inc.

BMK

Thanks Jonathon,

Much appreciated - I used GetUnactivationTime() on the submittask and if a value was returned "finished" the conflict checking.

Kind regards,
Barry