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

hardcoding task comments in the Job spec

WORKFLOWdude

6.5.0 SP 1

OK...this is probably a very easy question but I've grown tired of looking for an answer in the documentation and previous posts:

What is the syntax for hardcoding a taskcomment in the job specification?

For example, say I want a standard comment for a particular email task but I don't want to alter the code in iwsend_mail.ipl because I use that file for lots of other email tasks. Is there a way I can just add a variable or something in the job spec for the external task?

Mark

Find more posts tagged with

Comments

Adam Stoller

Are you talking about the task transition comments?
If so - they come from the callback of the externaltask script

$task->CallBack(id, message)

text report.rptdesign

WORKFLOWdude

Ghoti,
Thanks! Yep, I was talking about the task transition comment. I know that it can be hardcoded as part of the call back in the .ipl file. However I was thinking there was another way it could be done without having to touch the .ipl file. Since I use the same .ipl file in many tasks (and I don't want every one of those tasks to have the same transition comment) here's what I think I will do:

- Use something like this in the job spec portion of the .wft:
(variables>
(variable key="EmailComment" value="rejection email because filename has spaces"/>
(/variables>
(I had to replace some of my <'s with parenthesis or else the code would be invisible in this post.)
- Then alter the .ipl file to include something like this:
use TeamSite::WFworkflow;
my($job) = new TeamSite::WFworkflow($ARGV[0]);
my($mailComment) = $job->GetVariable('EmailComment');

$task->CallBack(id, $mailComment)

I think this will allow me to easily use a different transition comment for every task that uses the same .ipl file. The comments can be controlled from the job spec portion of the .wft. I guess originally I was just thinking there was some easier way to set the transition comment from the .wft job spec.

Adam Stoller

Ghoti,
[...] Since I use the same .ipl file in many tasks (and I don't want every one of those tasks to have the same transition comment) here's what I think I will do:

- Use something like this in the job spec portion of the .wft:
<variables>
<variable key="EmailComment" value="rejection email because filename has spaces"/>
</variables>

- Then alter the .ipl file to include something like this:
use TeamSite::WFworkflow;
my($job) = new TeamSite::WFworkflow($ARGV[0]);
my($mailComment) = $job->GetVariable('EmailComment');

$task->CallBack(id, $mailComment)

I think this will allow me to easily use a different transition comment for every task that uses the same .ipl file. The comments can be controlled from the job spec portion of the .wft. I guess originally I was just thinking there was some easier way to set the transition comment from the .wft job spec.

While I think you have the right idea - I think you'd be better served by doing it as a task variable so that you can pre-set the transition comment on a task-by-task basis.