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

Call back string value

Jenni

Hi All,

Thanks in advance. I am trying to pass a string from an external perl script as the call back value. Could anyone tell me how to pass it and access the value in the workflow?

Here is the statement from my external script, which gets triggered through an external task from the workflow.

$task->CallBack(1, $output, "Support File(s) Has Not Been Deployed");

I am trying to get the value of $output in to the workflow.

Any help would be appreciated.

Thanks!
Jenni

Find more posts tagged with

Comments

nipper

What level of TS ? WFT files or WFM ?

Jenni

What level of TS ? WFT files or WFM ?

TS 6.5
Windows 2003
WFT file

Thanks!
Jenni

nipper

Hi All,

Thanks in advance. I am trying to pass a string from an external perl script as the call back value. Could anyone tell me how to pass it and access the value in the workflow?

Here is the statement from my external script, which gets triggered through an external task from the workflow.

$task->CallBack(1, $output, "Support File(s) Has Not Been Deployed");

I am trying to get the value of $output in to the workflow.

Any help would be appreciated.

Thanks!
Jenni

for WFT try

$status = $output."\nSupport File(s) Has Not Been Deployed";
$task->CallBack(1, "$status")

Jenni

for WFT try

$status = $output."\nSupport File(s) Has Not Been Deployed";
$task->CallBack(1, "$status")

Thanks for the reply Nipper. I don't how to get the value of $status in to my workflow. Thats the place, where I am stuck.

Thanks!
Jenni

nipper

Those comments become part of the history of the job. So if you email the admin that the external task failed, the comments (and value of $status) will be in the email.

What do you want to do with the information ? If you need it for another app, then you can make it a WF variable instead.

Andy

nipper

Here is an example from a failed generate_content task:

Description: Page test [lcc\aknipp: 05/10/07 02:54 PM]

Last Comment: ERROR: iwpt_compile -> Could not process template: d:/interwoven/iw-home/custom/DotCom/iw_includes/TPLs/DetailPage.tpl Try debugging like this: iwpt_compile ... -ocode ****.ipl; ****.ipl [SYSTEM: 05/10/07 03:01 PM] [+ view 4 previous]

Jenni

Those comments become part of the history of the job. So if you email the admin that the external task failed, the comments (and value of $status) will be in the email.

What do you want to do with the information ? If you need it for another app, then you can make it a WF variable instead.

Andy

Hi Andy,

Thanks soo much for your quick reply. I don't need the entire history of the job. I am looking out for the particular value of $status into my WF and use it for some other task. Here is portion of the WF that calls the perl script as an attachment.

Thank!
Jenni

nipper

Then make a WF variable:

[html]

[/html]

in the ipl

to read:

$foo=$task->GetVariable('external_out');

to set:

$task->SetVariable('external_out', $output);

Does this help ?

Jenni

Then make a WF variable:

[html]

[/html]

in the ipl

to read:

$foo=$task->GetVariable('external_out');

to set:

$task->SetVariable('external_out', $output);

Does this help ?

Hi Andy,

Almost at the end. How can we assign the external_out variable in the template_script section of the WFT file. I mean I am trying to assign it to a perl variable.

Thanks!
Jenni

nipper

Hi Andy,

Almost at the end. How can we assign the external_out variable in the template_script section of the WFT file. I mean I am trying to assign it to a perl variable.

Thanks!
Jenni

If I understand your question, int he template_script you have a Perl var $my_data

You define the variable with something like this in a externaltask task specification:

[html]

[/html]

Jenni

If I understand your question, int he template_script you have a Perl var $my_data

You define the variable with something like this in a externaltask task specification:

[html]

[/html]

Andy,

Sorry about my repeated questions. You have answered my half of my question. After this statement,
[html]

[/html]
How can I assign the value of the "external_out" to a perl variable in the workflow? Thanks very much for your patience.

Thanks!
Jenni

nipper

If you are trying to set it to a value in the template_script, I do not think you can. That is run before the XML is processed.

You can get the information in an external task by using

$foo = $task->getVariable("external_out");

The example I showed takes a Perl variable defined in template_script ($my_data) and sets that as the value of a WF variable.

Jenni

If you are trying to set it to a value in the template_script, I do not think you can. That is run before the XML is processed.

You can get the information in an external task by using

$foo = $task->getVariable("external_out");

The example I showed takes a Perl variable defined in template_script ($my_data) and sets that as the value of a WF variable.

The statement "If you are trying to set it to a value in the template_script, I do not think you can" makes sense to me. I was trying something, which can't be possible. Thanks soo much for your reponses Andy. I appreciate your time and efforts.

Thanks!
Jenni

amaresh

If you are trying to set it to a value in the template_script, I do not think you can. That is run before the XML is processed.

You can get the information in an external task by using

$foo = $task->getVariable("external_out");

The example I showed takes a Perl variable defined in template_script ($my_data) and sets that as the value of a WF variable.

Hi Andy,

Just curious to know, is there a way that taskb can access the task variables of taskA?

Say,
[html]
....

...

....

?????How can we access task A variable "taskavalue"

[/html]
-- Chetty

nipper

You can make it a Workflow variable (defined at the WF level not at a specific task) and you will need to use teamsite::wfworkflow::getvariables()

Check the perldocs.

Adam Stoller

You can make it a Workflow variable (defined at the WF level not at a specific task) and you will need to use teamsite::wfworkflow::getvariables()

Check the perldocs.

Alternatively - the script for task-B could create a task object for task-A (using the name of task-A - read iwperldoc TeamSite::WFworkflow for details) - and then from that task-A-object you could retrieve the task-level variable ...

However, using a job variable is generally easier and more straight-forward.

nipper

Alternatively - the script for task-B could create a task object for task-A (using the name of task-A - read iwperldoc TeamSite::WFworkflow for details) - and then from that task-A-object you could retrieve the task-level variable ...

However, using a job variable is generally easier and more straight-forward.

you think ?

Yes one *could* use task variables, if you are like Adam and like doing things the hard way.

amaresh

You can make it a Workflow variable (defined at the WF level not at a specific task) and you will need to use teamsite::wfworkflow::getvariables()

Check the perldocs.

Thanks for the information.

-Chetty