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

Executing an WFT from an External Task in Teamsite

mageorge

As I need to generate an WF JobSpec XML in an external task, I am trying to execute the wft.
The jobfile(WF Job Spec XML) is not forming properly??

The code snippet is like this:

my $log = "/usr/local/fisher/cms/TeamSite/local/config/wft/fisher/conReview.xml";
open(LOG,">$log") or die "Could not open $log";

##### Instantiate workflow #####
my $wft = TeamSite::WFtemplate->new( template => $workflow);
$wft->{tag}{owner}{value} = "iwadmin";

$wft->get_tags();
my $jobfile = $wft->get_workflow();
print LOG $jobfile;

Please let me know if any implemented a functionality, of invoking a wft from external task.

Find more posts tagged with

Comments

kaalraa

Check whether your workflow has valid tags or not... by using validate_tags method passing the cgi object.

Also a suggestion, its better to use WFsystem and WFworkflow modules.

As I need to generate an WF JobSpec XML in an external task, I am trying to execute the wft.
The jobfile(WF Job Spec XML) is not forming properly??

The code snippet is like this:

my $log = "/usr/local/fisher/cms/TeamSite/local/config/wft/fisher/conReview.xml";
open(LOG,">$log") or die "Could not open $log";

##### Instantiate workflow #####
my $wft = TeamSite::WFtemplate->new( template => $workflow);
$wft->{tag}{owner}{value} = "iwadmin";

$wft->get_tags();
my $jobfile = $wft->get_workflow();
print LOG $jobfile;

Please let me know if any implemented a functionality, of invoking a wft from external task.

mageorge

Does any one have sample code snippet, to execute the wft file from an external task, to get JobSpecXML file as output.
Thanks in advance.

kaalraa

Use the code:


 my $system = new TeamSite::WFsystem();
my $wf = $system->CreateWorkflow($wfFile);
if (!($wf->IsValid()))
{
my $wfError = $wf->GetError();
}
else
{
$wf->Invoke();
}

Does any one have sample code snippet, to execute the wft file from an external task, to get JobSpecXML file as output.
Thanks in advance.

Adam Stoller

Use the code:

my $wf = $system->CreateWorkflow($wfFile);
my $system = new TeamSite::WFsystem();
if (!($wf->IsValid()))
{
my $wfError = $wf->GetError();
}
else
{
$wf->Invoke();
}

Those first two lines need to be reversed

mageorge

How can I create an jobfile(Workflow Job Spec File)?
I am trying to execute the nested workflow automatically.
For that I am using the jobfile element in the WFTask. Before this task, through an external task, I need to generate the jobspec file.

Please give your sugggestions on this.

kaalraa

Can use any of the 2 options, better would be to go along 1.

1. Use WFconstructor.pm in one of your external task prior to your WFTask.
2. Create your own xml file with all elements and attributes.

How can I create an jobfile(Workflow Job Spec File)?
I am trying to execute the nested workflow automatically.
For that I am using the jobfile element in the WFTask. Before this task, through an external task, I need to generate the jobspec file.

Please give your sugggestions on this.

Report - URL with preview.JPG

Report - URL with run.JPG

mageorge

Thanks for your reply.
Even the Interwoven support team has recommended to use the WFconstructor.pm.

I am not finding enough documentation or sample code snippet to implement it
Could you please provide with sample code snippet or any relevant documentation to do it.

Thanks in advance.

Adam Stoller

Thanks for your reply.
Even the Interwoven support team has recommended to use the WFconstructor.pm.

I am not finding enough documentation or sample code snippet to implement it
Could you please provide with sample code snippet or any relevant documentation to do it.

Thanks in advance.

You've got two semi-divergent threads going here.

Try perldoc TeamSite::WFconstructor and search the forums - the use of this module has been discussed many times.

ISCBorisB

Since i feel generous today... Here is "WF on the fly" snippet.
I actually combined that from various functions so it may have few glitches.
It's a skeleton really of what you would have to do.

Note that wft may be created with or without(old fashion style) WFConstructor.

use strict;
use TeamSite::WFsystem;
use TeamSite::WFtemplate;
use TeamSite::CGI_lite;       # needed by WFtemplate
use TeamSite::WFworkflow;
use TeamSite::WFtask;

my $workarea = "your WA";
my $branch = "your branch";
my @files = (Your File List to attach to WF);
my $job = undef;

my $wf_template = "$iwhome/local/config/wft/.../your.wft";
if (-f $wf_template) {

   # Get WF Template
   my $wft = TeamSite::WFtemplate->new(template => $wf_template,);

   # Add Required Tags
   $wft->{tag}{iw_user}{value} = "Your User";            
   $wft->{tag}{iw_desc}{value} = "Description";
   $wft->{tag}{iw_branch}{value} = $branch;
   $wft->{tag}{iw_workarea}{value} = $workarea;
   $wft->{tag}{custom1}{value} = "Something";
   $wft->{tag}{custom2}{value} = "Something Else";

   # Associate Files for Attachment
   $wft->{cgi_elem}{iw_file} = scalar(@files);   
   $wft->{tag}{iw_file}{value} = \@files;

   # Get Workflow Specs
   $wft->get_tags();
   my $job_specs = $wft->get_workflow();

   # Instantiate New Workflow.
   if ($job_specs) {
      my $wf_tmp = ($^O eq "MSWin32")? "$iwhome\\tmp\\cci\\workflow" : undef;
      my $wfs = new TeamSite::WFsystem;
      $job = $wfs->CreateWorkflow($job_specs, $wf_tmp);
      if ($job->IsValid) {
         log_it("Workflow Created, JobID is: " . $job->GetId() . "\n");

         # invoke WF
         eval { $job->Invoke(); };
         if ($@) {
            log_it("Failure Invoking Workflow: $@\n");
         }
         else {
            log_it("Workflow " . $job->GetId() . " Invoked\n");
         }

      }
      else {
         log_it("Error Creating Workflow: " . $job->GetError() . "\n");
      }
   }
   else {
      log_it("Error Getting Workflow Specs: " . $job_specs->{error_message} . "\n");
   }
}
else {
   log_it("Workflow Template \"$wf_template\" not found\n");
}

The following WFConstructor sample has been posted on DevNet by Jeff (I beleive) some time ago.
Search being what it is, I can not find this thread anymore, so
[HTML]use strict;
use warnings;
use Log::Log4perl;
use TeamSite::WFconstructor;
use TeamSite::Config;
use TeamSite::CGI_lite;
#======================================================================
(my $iwhome = TeamSite::Config::iwgethome()) =~ tr{\\}{/};
my $iwmount = TeamSite::Config::iwgetmount();
my $iwperl = "$iwhome/iw-perl/bin/iwperl";
(my $workarea = __VALUE__('iw_workarea')) =~ tr{\\}{/};
Log::Log4perl->init("$iwhome/local/config/log.conf");
my $logger = Log::Log4perl->get_logger();
my $iw_user = __VALUE__('iw_user');

my $DEBUG_MODE = 1;

#======================================================================
# Make sure the file list is defined
# Files sorted in unencoded form, then html-encoded via CGI_lite
#======================================================================
my @submit_files;
if (__ELEM__('iw_file')) {
@submit_files = map {
TeamSite::CGI_lite::escape_html_data($_);
} sort __VALUE__('iw_file');
}

my $span_style = qq(style="font-size:10px;font-weight:normal");
if ($DEBUG_MODE) {
my $ofile = "Y:/default/main/scholastic3_0/WORKAREA/work/wf_dbg.xml";
TAG_info(
iw_debug_mode =>
[ html =>
join(q{}
, qq{Yes },
, qq{}
, qq{ No }
, qq{}),
label => "Debug mode?",
is_required => "true",
],
iw_output_file =>
[ html => qq{},
label => qq{Debug file},
is_required=> "true",
],
);
}

my @submit_file_comments;
for(my $i = 0; $i < @submit_files; $i++){
push(@submit_file_comments, "pre-selected file");
}

#======================================================================
declare_workflow(name => "Scholastic 3.0",
owner => $iw_user,
creator => $iw_user,
description => "Create / Edit Articles",
files => \@submit_files,
file_comments => \@submit_file_comments,
);

# This will actually be a cgitask, removed for simplification
# to try and resolve the malformed header issue
declare_task("create_edit",
name => "CreateEdit",
type => "usertask",
owner => $iw_user,
areavpath => $workarea,
description => "Create and/or edit a data record.",
start => TRUE,
lock => FALSE,
);

declare_task("error_notify",
name => "ErrorNotify",
type => "externaltask",
owner => $iw_user,
areavpath => $workarea,
description => "An error occurred - notify someone.",
command => "$iwperl $iwhome/bin/iwsend_mail.ipl",
retry => TRUE,
lock => FALSE,
);
set_task_variable("error_notify", "mail_to", "****\@yyy");
set_task_variable("error_notify", "mail_from", "S30_TS");
set_task_variable("error_notify", "mail_subject", "Error occurred in workflow");

declare_task("handle_error",
name => "HandleError",
type => "usertask",
owner => $iw_user,
areavpath => $workarea,
description => "An error occurred - fix it.",
lock => FALSE,
);

declare_task("end",
name => "End",
type => "endtask");

#======================================================================
link_tasks("create_edit" , "error_notify", "error" );
link_tasks("create_edit" , "end" , "done" );
link_tasks("error_notify", "handle_error", "done" );
link_tasks("handle_error", "create_edit" , "return_to_create_edit");
link_tasks("handle_error", "end" , "abort" );

#======================================================================
propagate_from_dormant_tasks();
compute_activation_sets();

# print get_job_spec(); the reason for malforned header? Instead:
__INSERT__(get_job_spec());

#======================================================================
]]>

gosullivan

@ISCBorisB: Thank you so much for your code snippet, it has proven to be very useful in the instance I require it for. However, I am having an issue when initiating workflows where an external task includes email notification to a reviewer for example. For some reason, the email notification task is being ignored and never executes.

The Perl script I have uses the code snippet to create new Workflow object, passing the 'configurable_author_submit.wft' as the parameter.

This workflow should at it's simpliest 1) Send a notification to the reviewer (externaltask) 2) Author Review (usertask) 3) End.

I have set the associated .cfg properties for 'email_to_reviewer' to yes. When executed through the Teamsite UI, the workflow functions as expected, sending a note to the reviewer etc. But if this same workflow is called through a script at the command line, the first task (email to reviewer) does not occur. It jumps straight to the Author Review.

Any ideas why?

Thanks

- Ger

TS 6.5 SP2

ISCBorisB

...the email notification task is being ignored and never executes...Any ideas why?

Since you did not provide any code whatever I can only speculate.

So, for what it's worth:
Note that synopsis at the begining of "configurable_author_submit.wft" lists all required tags under "HTTP request keys" moniker.
Chances are, you failed to set some iw tag(s), see "Add required Tags" fragment of the snippet. Without
code it's hard to guess which one. As a result, *mailer* external task was either

a) Not generated/activated in the first place. To check that print out $job_specs right before Initiating new workflow.
Analyze XML, see what has been generated by "configurable_author_submit.wft". If mailer is not there or
has been bypassed, get to wft code and see how it generates Specifications, what are the conditions to add mail task, etc

Or

b) Worked, but did not send a mail you expect (or any mail at all). To check get to your iw.cfg and
set "debug_output=Your mailer log somewhere" in "iwsend_mail" section. Run again and analyze log

Hope that helps
If you expect better help you have to provide relevant information. As it is now your question basically
is "Some of my code (not posted) does not work, do you know why?"

BlueWhale

I found this thread very helpful. Thanks all. But, I got following questions when I want to invoke a sub WF from an external task.

My questions are:
(a) How can a child workflow (created by an external task from the parent WF) pass some variables back to external task of the parent WF??

(b) After the child WF passes variables to parent WF, will the external task going to execute again from the start (in this case, the external task kicks-off the sub WF again) or will it be executed from where it kicked-off sub-WF??

Please throw some light on this. Thank in adavnce.

Environment:
TS 6.5 SP2 on Windows 2000.

Report - URL with preview.JPG

Report - URL with run.JPG

ISCBorisB

I found this thread very helpful. Thanks all. But, I got following questions when I want to invoke a sub WF from an external task.

My questions are:
(a) How can a child workflow (created by an external task from the parent WF) pass some variables back to external task of the parent WF??

(b) After the child WF passes variables to parent WF, will the external task going to execute again from the start (in this case, the external task kicks-off the sub WF again) or will it be executed from where it kicked-off sub-WF??

Please throw some light on this. Thank in adavnce.

Environment:
TS 6.5 SP2 on Windows 2000.

Your questions beg for different approach. It looks like what you need is *true* nested Workflow. Take a look at the WF
manual, <wftask> Element (Workflow Task) and how to use it. Note that the schema discussed in this thread actually
creates another independent Workflow. Any Parent/Child relation is superficial and must be maintained by WF Developer(you!)
through code.

With the spawned (not trully nested!) WF:

Q. How can a child workflow pass some variables back...
A. There are many methods. For example, set "ParentJobId" and/or "ParentTaskId" Tags in the Child wft and populate
these Tags upon generating Child Specs. This information will allow your Child's External/CGI Tasks to instantiate Parent's
WFworkflow/WFtask Objects and corresponding APIs to set Parent's variables, etc... Note though that at the time sub-WF
wants to manipulate Parent variables it may be already an orphan!

Q. After the child WF passes variables to parent WF, will the external task going to execute again...
A. External task spawns *Child* WF and continues on it's merry way, self-transitions to some successor and so on. If *Parent*
is still alive when child comes to it, you can in theory control *Parent* Flow from the *Child*, see above. I do not think
it's a good idea though.

BlueWhale

yeah, I have gone through wftask but, as I need to have control over invoking the number of sub WFs getting kicked-off (depends on the no. of locales under a particular country), I am going for "Executing an WFT from an External Task". I have no idea to kick-off nested WFs dynamically by using wftask. Any ideas welcome!!

I think I can keep the parent external task ACTIVE by not calling back to next transition unless I get some feedback from all the child WFs but, I am not sure how to solve my questions (a) and (b).

Please share your ideas. Thank You.

ISCBorisB

I have no idea how to kick-off nested WFs dynamically by using wftask... I am going for "Executing an WFT from an External Task".

That is saying "I do not know how to do a simple task, I'm going for much more complex one instead!"

If you can figure "number of locales" in the wft code you can dynamically generate required number of
concurrent Workflow tasks, either by adding (almost) identical XML fragments or by using
TeamSite::WFconstructor::declare_task in a loop.

I think I can keep the parent external task ACTIVE by not calling back to next transition...

Although it's possible to temporarily *halt* script execution it's truly terrible idea for the External task.
You'll deliberately hung a workflow for the unknown time. Besides, how would you nudge it forward when time comes?
How would you know that it did come?

I am not sure how to solve my questions (a) and (b)

I was sure I've answered in my previous post. Was something unclear?

BlueWhale

Thank You ISCBorisB!!! your post changed my mind and now I am going for nested workflows (using wftask) from configurable WFs.

So, you say that, depending on the number of locales loop the wftask element, right? I assume that the linking also need to be done the same way. If I am wrong, please let me know. Also, I think I need to use "logical AND" to callback to parent WF while linking tasks.

Thanks alot.

ISCBorisB

Thank You ISCBorisB!!! your post changed my mind and now I am going for nested workflows (using wftask) from configurable WFs.

So, you say that, depending on the number of locales loop the wftask element, right? I assume that the linking also need to be done the same way. If I am wrong, please let me know. Also, I think I need to use "logical AND" to callback to parent WF while linking tasks.

Thanks alot.

It seems that the linking you want resembles the following diagram. In it wftasks are concurrent and are initiated
as a package (eg, all of them at the same time), *post wftask* transitions on "And" condition


                     /-(wftask[locale1])-\
(some_task[start?])-+--(wftask[locale2])--X(AND)->...
                     \-(wftask[locale3])-/