Automatic selection of a workflow based on the extended attrib

I am trying to merge two workflows into one wft file in such a way that I can trigger one of the workflow based on a certain category/data-type and the other for all of the rest. I tried to use the PERL conditional statement based on the data-type of the selected files and managed to get the correct workflow with the right values but I was getting some kind of weird error during the process. When I used the workflow debug I saw that the resultant workflow has both the workflows merged with the first one having the correct values and the later with blank values. Is there anyway to make the workflow recognize only one and not the other through perl conditional statement?

Find more posts tagged with

Comments

nipper

It is very unclear what how you did what you tried to do.

However the problem you mention is not that tough to understand. You will likely want to write a Perl script to build the XML needed for a jobspec call and use that to invoke the WF.

Or you can post what you did and maybe someone will have the time to debug for you

kaalraa

I am trying to merge two workflows into one wft file in such a way that I can trigger one of the workflow based on a certain category/data-type and the other for all of the rest.

You are going to merge the 2 workflows or trying to select one of them to be initiated.

I tried to use the PERL conditional statement based on the data-type of the selected files and managed to get the correct workflow with the right values but I was getting some kind of weird error during the process. When I used the workflow debug I saw that the resultant workflow has both the workflows merged with the first one having the correct values and the later with blank values. Is there anyway to make the workflow recognize only one and not the other through perl conditional statement?

Now, that depends upon my first question. If merging is going to happen... then it should pick values for both workflows, else you have to stop calling the other, with blank values. If it is to be selected, then it is quite easy to initiate a workflow based on values from perl.

Please be more clear about your output requirement and as well as input you have with you.

Adam Stoller

I am trying to merge two workflows into one wft file in such a way that I can trigger one of the workflow based on a certain category/data-type and the other for all of the rest. I tried to use the PERL conditional statement based on the data-type of the selected files and managed to get the correct workflow with the right values but I was getting some kind of weird error during the process. When I used the workflow debug I saw that the resultant workflow has both the workflows merged with the first one having the correct values and the later with blank values. Is there anyway to make the workflow recognize only one and not the other through perl conditional statement?

How are your WFTs coded?
With TeamSite::WFconstructor.pm so that they're essentially all Perl - or with a lot of XML tags?

If the former - it should be easier to programmatically generate the correct code based on information derived about the pre-selected files.

If the latter, it can be done but it's a lot messier and more confusing and difficult to maintain.

enthusiast

Thanks for you responses guys and sorry for the confusion. The said workflow is mainly coded in XML and what I am trying to do is merge the code of two existing workflows into one wft so that for the users, there would only be only one selection of the workflow while in the backend, the flow is governed by the data-type of a given dcr.

I am trying to do something like the following:

if ($listingFlag) {
]]>XML code for first workflow
}
else
{
]]>XML code for 2nd workflow
}
/template_script>

Only one of the workflow would be invoked at a time.

kaalraa

All of your code has vanished away the earlier posts.

Either try to revive the thread else... start a new thread with your code as attachments. Also never forget to preview your posts prior to submit.

enthusiast

I think the best approach for me in this case would be redeveloping the workflows in perl. Could anyone kindly let me know how to attach a file list within a cgi task using TeamSite::WFconstructor. I have listed the similar functionality as XML below:

<cgitask name="Review_TV_Listings"
owner="__TAG__('iw_user');"
description="User Reviews TV Listings"
immediate="t"
start="t">

__INSERT__("<areavpath v='$iw_workarea'/>");

<successors>
<successorset description="Publish to Preview">
<succ v="Submit"/>
</successorset>
<successorset description="Cancel Job">
<succ v="End"/>
</successorset>
</successors>

__INSERT__("<command v='$cgi_command_reviewTVListings'/>");

<template_script><![CDATA[
if (__ELEM__('iw_file'))
{
__INSERT__(" <files>\n");
for (my $i = 0; $i < @submitFile; ++$i)
{
__INSERT__(" <file path='$submitFile[$i]' comment='File attached to workflow'/>\n");
}
__INSERT__(" </files>\n");
}
]]></template_script>

</cgitask>

kaalraa

I think the best approach for me in this case would be redeveloping the workflows in perl. Could anyone kindly let me know how to attach a file list within a cgi task using TeamSite::WFconstructor.

If you need to attach the files at the time of instantiating the job through wfconstrutor then you can use the property of declare_workflow function.

files => ["foo", "bar", "baz"],
file_comments => ["File the first",
"File the second",
"The last file"]);

Whereas, if the files are needed to be attached for CGITask, then it could be done using Task Object and AddFile or AddFiles method.

ChartTesting.rptdesign

Chart Test.xls

Adam Stoller

I think the best approach for me in this case would be redeveloping the workflows in perl. Could anyone kindly let me know how to attach a file list within a cgi task using TeamSite::WFconstructor. I have listed the similar functionality as XML below:

Read the perldoc on TeamSite::WFconstructor
Look at some of the solution workflows
Re-read the perldoc on TeamSite::WFconstructor

Actually, the trick here is to identify the documentation which deals with adding files to the workflow and not the task - then knowing how to pass references to arrays.

With that information - you should be able to skip one of the above two readings ;-)