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

Can a workflow transition from an external task immediately to a cgi task?

Tbag

Hi,

I used to have this:

UserTask --> CGITask

And it worked great, and the CGITask popped up immediately (I had no problems with different owners, etc.)

Now I introduced this:

UserTask --> ExternalTask --> CGITask

And the external task I have is a sub-second submit operation that transitions to the CGITask on success. The CGITask is marked "immediate='t'", but it isn't popping up immediately.

Is this verboten? Possible?

Find more posts tagged with

Comments

nipper

Are the owners of each task the same ? This should be supported.

Tbag

Hmm....yeah, I don't think the owners issue is a moot point with what I'm trying to do. The owner of my external task is the same as the owner of the cgitask, though it appears as though the user 'SYSTEM' is actually doing the transition.

Regardless, I think this thread answers my question --
http://devnet.interwoven.com/forums_vb/showthread.php?t=8785&forumid=16&highlight=immediate%3D%22t%22

It makes sense that this isn't possible because TeamSite has no idea where to "popup" the immediate CGI task after the external task completes.

Adam Stoller

Hi,

I used to have this:

UserTask --> CGITask

And it worked great, and the CGITask popped up immediately (I had no problems with different owners, etc.)

Now I introduced this:

UserTask --> ExternalTask --> CGITask

And the external task I have is a sub-second submit operation that transitions to the CGITask on success. The CGITask is marked "immediate='t'", but it isn't popping up immediately.

Is this verboten? Possible?

Are the owners of each task the same ? This should be supported.

For shame - this has never worked.

If you read the documentation (either the official Workflow Developer's Guide or the Workflow Tutorial Supplement - despite its age) you will find a list of the conditions under which a cgitask will be able to fired off automatically. After an externaltask is not one of those conditions.

If the submit operation can be owned by the same person who would be running the cgitask (who is the same person who owned the usertask) - then you could consider moving the submit operation into the cgitask script and properly handling error conditions as they might occur.

If the submit operation needs to be owned by someone other than the person who owns the cgitask - then I'm not sure if what you want is [easily?] possible.

Tbag

If the submit operation can be owned by the same person who would be running the cgitask (who is the same person who owned the usertask) - then you could consider moving the submit operation into the cgitask script and properly handling error conditions as they might occur.

Yeah, that's exactly what I did...

I refactored all the functionality present in the external task into methods contained within perl modules so that I can use the external task within my *.wft where it's easily understandable as "that's where submits happen", but so that I can also call the very same method directly from within a CGITask as it starts up.

cgi

Hi,

I want to know if it is possible to have a CGItask pop-up for keeping condition in Teamsite,

Let us take an example if we want to end workflow in Teamsite then a CGI pop-up should appear showing the warning message whether we want to continue 'yes' or 'no'.

Is it possible?

Adam Stoller

Hi,

I want to know if it is possible to have a CGItask pop-up for keeping condition in Teamsite,

Let us take an example if we want to end workflow in Teamsite then a CGI pop-up should appear showing the warning message whether we want to continue 'yes' or 'no'.

Is it possible?

From the subject line of this thread - the answer is technically "yes" it can transition, but "no" the CGI script will not start automatically (and thus probably is not what is being looked for).

From the content of this post - if you are providing a transition on a usertask (or grouptask, or some other user-interactive task) to allow the users to gracefully abort a job - then "yes", you could have that transition to a CGI task which could (though it may require some iwat trigger processing) start automatically to prompt the user. If you are still talking about some non-user-interactive task, then the answer is still "no".

If you are talking about the End Job option within the Workflow Tab interface of the TeamSite GUI - then I believe there is already a confirmation prompt, but other than that I don't believe there is any further [supported] customization for that.