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

CGI Task: Immediate flag not functioning as advertised!!

ReggieRWalker

Env: TS 6.7.1 SP1 / Windows 2003 Ent.

I have a workflow that starts with an external task and transitions to a CGI task that allows the user to set metadata. The problem is that the CGI task does not start immediately, even though I have immediate => TRUE in my task declaration. All works well, if the CGI task the start task.

Here's the code snippet:


    declare_task('auto_set_metadata',
                 name        => "Auto",
                 description => "Automatically set known metadata values.",
                 type        => "externaltask",
   start       => TRUE,
                 owner       => $iw_areaowner,
                 areavpath   => $iw_workarea,
                 command     => "$iwperl $autoset_ipl");
    declare_task('metadata',
                 name        => $localizer->format('metadata_task.name'),
                 description => $localizer->format('metadata_task.description'),
                 type        => "cgitask",
                 start       => FALSE,
                 owner       => $iw_user,
                 areavpath   => $iw_workarea,
                 immediate   => TRUE,
                 command     => $metadata_capture_ui);

TIA

Find more posts tagged with

Comments

jbonifaci

Immediate does not work after an exteraltask. It only works if it is the start task or if it immediately follows another cgitask.

ReggieRWalker

Oh well. Such is the life of Interwoven. I did find a hack for my workflow by setting the start value of the CGI task to true as well.

jbonifaci

I wouldn't recommend doing that in this scenario. It appears that your externaltask is setting default values for your cgitask. By having them both run at start, there's nothing that says your externaltask will finish before the cgitask starts. So you could easily run into a scenario where the cgitask form loads without the default values. This seems like it would be undesirable.

I would recommend converting your externaltask into a cgitask that does the same thing and auto submits itself. You can then have both of these cgitasks as immediate true, but only the first one as start true and it will then work as desired.

If you need the externaltask in other places and can't just replace it, wrap the functionality in a perl module and call it from both the existing externaltask script and the new cgi script.

~Jeff

ReggieRWalker

Thanks Jeff for validating my concerns. I will change to a CGI task.

Adam Stoller

Immediate does not work after an exteraltask. It only works if it is the start task or if it immediately follows another cgitask.

Correction - immediate will work if the cgitask:

The reason for this is that those are the only situations in which the user who owns the cgitask can be guaranteed to be logged in on the current client machine.