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

Converting external task to CGI task ?

nipper

Any docs on how to write a CGI task ? Basically the Attach Dependency step does not parse DCRs, so I need to parse that and attach images referenced in the DCR.

I need to add an external task to the PLC workflow. However if I were to insert an external task between two CGI tasks, then the popup goes away and the next CGI will not start automatically.

So I figure I will start with showenv.cgi and put my perl in that. I think I can get some of the steps out of iwconflictstep.cgi but I am really concern about what I need to do to transition automatically

Andy

Find more posts tagged with

Comments

Adam Stoller

Are you talking about a Perl CGI?
If so - look at the "Legacy" WF documentation (or my old supplemental WF documentation which largely got folded into the "Legacy" WF documentation) - which contains some boilerplate code for doing a CGI.

Or are you talking about doing this in Java? You could then try to use the Dependency code in CSSDK (though it sounds like that's not working?) - take a look at:

nipper

[QUOTE=ghoti]Are you talking about a Perl CGI?
If so - look at the "Legacy" WF documentation (or my old supplemental WF documentation which largely got folded into the "Legacy" WF documentation) - which contains some boilerplate code for doing a CGI.

Or are you talking about doing this in Java? You could then try to use the Dependency code in CSSDK (though it sounds like that's not working?) - take a look at:

This is perl, the OOTB dependency manager is *supposed* to add static assets that are referenced in a DCR to the workflow, but it doesn't. Support says it is a doc bug. So I am trying to do this quickly and easily. The Perl is easy, but now I have found that an external task cannot be added to the PLC workflow. The CGI task transition gets hosed if there is a external task in the middle.

ISCBorisB

This is perl, the OOTB dependency manager is *supposed* to add static assets that are referenced in a DCR to the workflow, but it doesn't. Support says it is a doc bug.

So I am trying to do this quickly and easily. The Perl is easy, but now I have found that an external task cannot be added to the PLC workflow. The CGI task transition gets hosed if there is a external task in the middle.

Stuck it into first CGI, right before a transition to the "back-to-back" second one.
If I were you I would simply use qx(yourScript params), in the "feigned" external Task fashion.
(Just make sure it does not attempt any transition on its own)

nipper

Stuck it into first CGI, right before a transition to the "back-to-back" second one.
If I were you I would simply use qx(yourScript params), in the "feigned" external Task fashion.
(Just make sure it does not attempt any transition on its own)

Not certain if I can. The PLC workflow starts off with attach dependencies, which has to run before my CGI ( to cover PAGE including DCR including images). That attach dependencies is a JAVA program.

ISCBorisB

Not certain if I can. The PLC workflow starts off with attach dependencies, which has to run before my CGI ( to cover PAGE including DCR including images). That attach dependencies is a JAVA program.

Ah, got it... You are correct, my proposal won't work in PLC case. Replied to your mail

Adam Stoller

This is perl, the OOTB dependency manager is *supposed* to add static assets that are referenced in a DCR to the workflow, but it doesn't. Support says it is a doc bug.

So I am trying to do this quickly and easily. The Perl is easy, but now I have found that an external task cannot be added to the PLC workflow. The CGI task transition gets hosed if there is a external task in the middle.

Okay - so write a Perl CGI, embed it in between the other CGI Tasks, and make sure it transitions correctly to the CGI Task that follows it.

Shouldn't be too hard for a fellow of your experience ....

nipper

Okay - so write a Perl CGI, embed it in between the other CGI Tasks, and make sure it transitions correctly to the CGI Task that follows it.

Shouldn't be too hard for a fellow of your experience ....

Yea that is the plan. I hoped to use an external task and quoted 8 hours. Flew over that estimate pretty quick. :-)

Adam Stoller

Yea that is the plan. I hoped to use an external task and quoted 8 hours. Flew over that estimate pretty quick. :-)

Unless you're planning to do anything in the CGI Window - it should be (have been) pretty trivial:

Assuming the transition piece works (it used to, and then at some point it stopped working but I think that got fixed) the only complex part of the code is the code you were going to have to write anyway when you assumed it was going to be an ExternalTask - right?

nipper

****

Pain in the a$$

I put my CGI between Attach Dependencies and Check Migration Status, Added a success link from my CGI to Migration.

My CGI gets kicked off and completes with

$cgi->iwcallback("Success", "images attached");

I verified that the transition is called Success.

I use the same users ($IW_USER) for all 3. Immediate flag is true. I also added the ImmediateTransition=true set in the Task Variable (on all 3 CGIs).

Still when I run it, Attach Dependencies runs, Attach Images runs and the Active CGI is Check Migration but you need to do the Start Input Task.

HKN1104

****

Pain in the a$$

I put my CGI between Attach Dependencies and Check Migration Status, Added a success link from my CGI to Migration.

My CGI gets kicked off and completes with

$cgi->iwcallback("Success", "images attached");

I verified that the transition is called Success.

I use the same users ($IW_USER) for all 3. Immediate flag is true. I also added the ImmediateTransition=true set in the Task Variable (on all 3 CGIs).

Still when I run it, Attach Dependencies runs, Attach Images runs and the Active CGI is Check Migration but you need to do the Start Input Task.

Hi Nipper,

Even when you click on Start Input task, Does this deploy new content to respective target with updations.

Thanks

nipper

I am printing out this (I assume it is the callback that does it)

[php]
Content-type: text/html

<script language="javascript">
function handleOnLoad()
{
document.mainform.submit();
}
</script>

[/php]

The popup goes away after my CGI runs,

nipper

Hi Nipper,

Even when you click on Start Input task, Does this deploy new content to respective target with updations.

Thanks

Yea, that piece works, so I could send this out, but my customer would revolt if they had to jump those hoops

Adam Stoller

****

Pain in the a$$

I put my CGI between Attach Dependencies and Check Migration Status, Added a success link from my CGI to Migration.

Did you use a Success Link - or a Default Link named "Success" ?

It has to be the latter - CGI Tasks do not understand Success / Failure Links.

nipper

Did you use a Success Link - or a Default Link named "Success" ?

It has to be the latter - CGI Tasks do not understand Success / Failure Links.

Default called success

No go.

I assume that $cgi->iwcallback does something different than the Java does. Trying to reverse engineer. No luck.

HKN1104

Default called success

No go.

I assume that $cgi->iwcallback does something different than the Java does. Trying to reverse engineer. No luck.

Nipper,

Use of timeout link with 0 seconds and move it to next task.

Thanks

ISCBorisB

Nipper,

Use of timeout link with 0 seconds and move it to next task.

Thanks

Note that Nipper's issue is not a transition per se. Tasks do transition.

The problem is a disruption (upon transition) in CGI "Immediate" rendition Mode when
he embeds Perl CGI Tasks between two PLC Java CGI Tasks.