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

Adding a cgitask to a .wft workflow

HurricanesFan

Hello,

I need a new workflow and I found the OOTB solutions/author_submit_with_deploy.wft is perfect for our needs except instead of the default screen you get on first entry (job instantiation form?) I need to change the user entry screen to one of our own where we can show file information and get certain parameters from the user instead (not just submit comments & info).

So I have added a <cgitask> at the start of the job to use our own cgi screen, but it isn't working - still get the default screen and I'm not sure what more I need to do. I have set "foo" to on and to me it looks like it is setting up the job template correctly, as follows. Chnages are marked "PDJ".

Does anyone here have some experience with the .wft workflows and changing them in this way?

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

<workflow name="Author Submit with Deploy"
          owner="root"
          creator="root"
          description="d">

<!-- PDJ - add own cgitask -->
    <cgitask name="EntryScreen"
              owner="johnsonpd"
              description="Entry screen for Promotion"
              start="t"
              immediate="t"
              readonly="t">
        <areavpath v="/default/main/nlm/WORKAREA/common"/>
        <successors>
            <successorset description="Cancel">
                <succ v="End"/>
            </successorset>
            <successorset description="Normal priority">
                <succ v="Approver"/>
            </successorset>
        </successors>
<!-- Put in my own cgi here -->
        <command v='nlm_post_entry_noapproval.cgi'/>
        <files>
            <file path='htdocs/about' comment=''/>
        </files>
        <!-- Some example task variables -->
        <variables>
            <variable key="sign" value="Virgo"/>
            <variable key="city" value="Paris"/>
        </variables>
    </cgitask>
<!-- PDJ - end cgitask -->

    <usertask name="Approver"
              owner="root"
              description="Author Content Approval"
              start="t"
              readonly="t">
        <areavpath v="/default/main/nlm/WORKAREA/common"/>
        <successors>
            <successorset description="Approve">
                <succ v="Submit"/>
            </successorset>
<!-- PDJ -->
            <successorset description="Reject">
                <!-- <succ v="AuthorWork"/> -->
                <succ v="End"/>
            </successorset>
        </successors>
        <files>

                               <file path='htdocs/about' comment=''/></files>

        <activation>
<!-- PDJ -->
                <!-- <pred v="AuthorWork"/> -->
                <pred v="EntryScreen"/>
        </activation>
    </usertask>

<!-- PDJ -->
    <!-- <usertask name="AuthorWork"
              owner="johnsonpd"
              description="Author Work">
        <areavpath v="/default/main/nlm/WORKAREA/common"/>
        <successors>
            <successorset description="Finish">
                <succ v="Approver"/>
            </successorset>
        </successors>
        <activation>
            <pred v="Approver"/>
        </activation>
    </usertask> -->

    <submittask name="Submit"

Find more posts tagged with

Comments

nipper

What happens? Several years ago I put a CGI as the 1st screen of WFT and it would autostart.

Does the CGI work ? Do you have to click start input task ? Are the permissions set for the CGI ? What happens if you run it from the command line?

David Smith

I think you may be confusing the instantiation screen with a cgitask screen. The instantiation form is typically handled (if I remember correctly) in the TAG_info section of the wft file. It's been a long time since I worked with wfts. You also have two start tasks, which is not illegal, but it's also probably not what you want to do. If all you want to do is alter the instantiation form, you don't need a cgitask. A cgitask is used when you want to display another form or a pop-up with information during the execution of the workflow tasks - post instantiation. It's very simple to modify the instantiation form using the constructs provided by TeamSite. Do they still print the old WFT developer manual?

HurricanesFan

I think Smitty has shown me a way forward - the screen I get on first entry is coming from the TAG_info section of the .wft. I'm just reading about TAG_info in the "legacy" Workflow Reference Guide now.

So yes, I am thinking that rather than have my own cgi screen, I could use TAG_info to get and display the values I need, and I wouldn't have to pass vars between a cgi & the wft. I can strip everything out of TAG_info and I am just left with Cancel and "Start Job" buttons.

I'll sleep on this and play around with it tomorrow.

Thanks guys.

nipper

You can go without an instantiation screen. That should go straight to the CGI. I did it before, need to remove the items in the TAG_INFO

HurricanesFan

nipper wrote:
You can go without an instantiation screen. That should go straight to the CGI. I did it before, need to remove the items in the TAG_INFO

Andy, I have (temporarily) removed all the items in 2 x TAG_info, but am still left with Cancel and "Start Job" buttons, not sure where to disable them yet. But that may be alright if I can instead fill the space with the fields I need instead.

Here's what I have removed, for clarity:

#   TAG_info(
#      iw_submit_comment =>
#          [ html        => $localizer->format('submit_comment_label').
#                           "<br><textarea rows=8 style='width:100%'></textarea>".
#                           "<br> ",
#            error_msg   => $localizer->format('submit_comment_error_msg'),
#            label       => '',
#          ],

       # push iw_info_field into workflow
#      iw_info_field =>
#          [ html        => $localizer->format('info_label1') .
#                           "<br><input type=text size=50>".
#                           "<p> <br><em>" .
#                           $localizer->format('info_label2') . "</em>",
#            error_msg   => $localizer->format('info_label_error_msg'),
#            is_required => 'false',
#            label       => '',
#          ],
##PDJ 150723
#      iw_output_file => "<input type='text' value='/tmp/foo.xml'>\n",

##PDJ 150723
#      iw_debug_mode => "<input type='text' value='true'>\n",
#   );

....

    for (my $i=0; $i<@submit_file; ++$i)
    {
##PDJ
#       TAG_info(
#           "File_comment_$i" =>
#               [ html        => $localizer->format('comment_label') .
#                                "  $submit_file[$i]<br>".
#                                "<textarea rows=8 style='width:100%'></textarea>".
#                                "<br> ",
#                 error_msg   => $localizer->format('comment_label_error_msg'),
#                 is_required => 'false',
#                 label       => '',
#               ],
#       );
    }

nipper

Not certain what to tell you. I found a copy of mine. Basically it fails if the user was not in a specific list (this was a 1 button publish):

my $found=0;
my($iw_user) = (__VALUE__("iw_user"));
foreach (@admin_group) {
if ($iw_user eq $_) {$found = 1;}
}
if (!$found) {
CGI_info(
pre_tagtable_html => "User ".$iw_user." Not allowed to use WF <br>",
title => "IM DIrect Submit",
);
}

my($iw_selected_files) = iw_get_filelist();

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

if (!$found) {
TAG_info(

iw_dummy_tag =>
[ html => "<input id='dummy_tag' type='hidden'>",
is_required=> 'true'
]);
}

]]>

</template_script>

David Smith

Why not use the instantiation form if that's essentially what you're needing, Andy? What's the benefit of skipping the instantiation form and using a cgitask?

nipper

Smitty97007 wrote:
Why not use the instantiation form if that's essentially what you're needing, Andy? What's the benefit of skipping the instantiation form and using a cgitask?

Depends on the CGI you are using and if it is.worth reimplementing in the WFT

HurricanesFan

Back on this, I'm just about there with my workflow, but I have 1 issue I'm going round in circles on. I'm pretty there is an easy answer and I'm missing a piece of information...

The first 2 tasks are the usual first 2 tasks in the OOTB authour_submit_with_deploy|email and various others i.e. usertasks Approver & Authorwork as follows.

But I want to change it so that the job ends on "Reject", and you can see where I'm trying to do that marked "PDJ" below. But can't get it to work. For the changes I have in place below I get "Object is inconsistent.... Predecessors and activation inconsistent End".

What am I missing?

Cheers

<usertask name="Approver"
              owner="__TAG__('iw_areaowner');"
              description="Review Task"
              start="t"
              readonly="t">
        <areavpath v="__TAG__('iw_workarea');"/>
        <successors>
            <successorset description="Approve">
                <succ v="Submit"/>
            </successorset>
            <successorset description="Reject">
                
                
                <succ v="End"/>
            </successorset>
        </successors>
        <template_script><![CDATA[
            if (@submit_file != 0)
            {
                __INSERT__("<files>\n");
                for (my $i=0; $i < @submit_file; ++$i)
                {
                    __INSERT__("
                               <file path='$submit_file[$i]' " .
##Use $file_comment[$i] rather than File_comment_$i to pass on in workflow.
#                              "comment='__TAG__(File_comment_$i);'/>");
                               "comment='$file_comment[$i]'/>");
                }
                __INSERT__("</files>\n");
            }

        ]]></template_script>
        
        
    </usertask>

    <usertask name="AuthorWork"
              owner="__TAG__('iw_user');"
              description="Author Work">
        <areavpath v="__TAG__('iw_workarea');"/>
        <successors>
            <successorset description="Finish">
                <succ v="Approver"/>
            </successorset>
        </successors>
        
        
    </usertask>

HurricanesFan

As you were, I solved this - I was looking for the error in the wrong place.