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

TS workflow and iwsend_mail.ipl

magikandrea

I created a workflow that has an external task which send an email using the iwsend_mail.ipl perl script. The external task is followed by an usertask (Visualizza_DCR).

I send the external task code in attachment.

What happens is that the email is sent correctly to the recipient, but the workflow enters into an "idle" state and the usertask is not activated.
I just can see that the external task is always in the Active state.

Is there anybody that can help me with this issue?

Thank you for your help.

Find more posts tagged with

Comments

kaalraa

Hi,

As far as external task is concerned... it looks ok to me. But still as the task is not activating its successor, it might be due to lack of callback within the perl script.

Just check within your perl script ... whether it sends back message to the workflow about its completion using callback method.

Also, if possible, attach the perl file as well.

I created a workflow that has an external task which send an email using the iwsend_mail.ipl perl script. The external task is followed by an usertask (Visualizza_DCR).

I send the external task code in attachment.

What happens is that the email is sent correctly to the recipient, but the workflow enters into an "idle" state and the usertask is not activated.
I just can see that the external task is always in the Active state.

Is there anybody that can help me with this issue?

Thank you for your help.

magikandrea

Here is the perl script.

It is the iwsend_mail.ipl provided by TeamSite: it is placed into the /bin folder.
I did not modify it, I just followed the TeamSite Workflow Documentation.

kaalraa

Ok... if you using the teamsite provided script... then it has the callback method by default. And as you have only one successor to the external task it should go to the same.

Still, some minor things to be checked:
1. Put the name attribute in your external task
2. Check if the succ v = "--" is same as name of the User task.

Here is the perl script.

It is the iwsend_mail.ipl provided by TeamSite: it is placed into the /bin folder.
I did not modify it, I just followed the TeamSite Workflow Documentation.

magikandrea

I already have the name attribute for the external task, and the succ v value is the same as the user task name.

Is there something else I should check?

Migrateduser

I already have the name attribute for the external task, and the succ v value is the same as the user task name.

Is there something else I should check?

try adding "-N Visualizza_DCR" to the mail command.

magikandrea

Hi, tomorrow morning I'll try and send a feedback.

Can you briefly explain what does the "-N" mean?

Thank you for the suggestion!

Calendar.JPG

Adam Stoller

I already have the name attribute for the external task, and the succ v value is the same as the user task name.

Is there something else I should check?

Does the usertask *after* the (email) externaltask have the lock="t" attribute set?

If so - you may be running into a locking conflict that is preventing the usertask from becoming fully activated (this can be determined by looking at the output of iwgetwfobj for the usertask's id and seeing if there's something like tryingtolock="t" (not sure if that's the exact wording)

Other than that, the only possible problem I can see with the externaltask for sending email is that you have TS installed in "Program Files" (a directory with an evil space in its name) and it's possible something is dying in the script because of that -- however if the mail is getting sent, that seems an unlikely source of the problem.

magikandrea

In attachment there is the user task code. It has the lock='t' attribute set.
What can I do to solve this conflict?

I installed TeamSite in the "Program Files" folder, but I don't think this is the problem. I build the command in the external task using the $iwhome variable which is set to "C:/PROGRA~1/INTERW~1/TeamSite" and, as you are saying, the email is sent correctly.

Thank you very much for your help.

magikandrea

Sorry, I forgot the attachment.
Here is.

magikandrea

I set the lock attribute for the user task to 'f'. Nothing changed.
Running the iwgetwfobj I receive the output attached.

Is there anybody that can give any suggestion?

Thank you very much.

magikandrea

I found what was wrong.

The external task command is built as follow:

[font='Courier New']

[/font]

[font='Courier New']$command = "$iwhome/iw-perl/bin/iwperl $iwhome/bin/iwsend_mail.ipl -f $from -t $to -s '$subject' -m '$message' -u";

[/font]

[font='Courier New']

[/font]

[font='Courier New']where

[/font]

[font='Courier New']$subject and $message are two strings that contain the space character (' '):

[/font]

[font='Courier New']

[/font]

[font='Courier New']=============================================

[/font]

[font='Courier New']

[/font]

[font='Courier New']$subject = "TeamSite Alert Notification";

[/font]

[font='Courier New']

[/font]

[font='Courier New']$message = "You have a new task.";

[/font]

[font='Courier New']=============================================

[/font]

[font='Courier New']

[/font]

[font='Courier New']

[/font]

[font='Courier New']So the iwsend_mail.ipl script parses the parameters in the wrong way. I tryed to use the '\' to escape the blank space, but nothing changed.

[/font]

[font='Courier New']

[/font]

[font='Courier New']

[/font]

[font='Courier New']How can I escape this character?

[/font]

[font='Courier New']

[/font]

[font='Courier New']Thank you for your help!!

[/font]

ISCBorisB

Space is space, same symbol escaped or not. So:

$command = qq($iwhome/iw-perl/bin/iwperl $iwhome/bin/iwsend_mail.ipl -f $from -t $to -s "$subject" -m "$message" -u);
Or
$command = "$iwhome/iw-perl/bin/iwperl $iwhome/bin/iwsend_mail.ipl -f $from -t $to -s \"$subject\" -m \"$message\" -u";

Even better, do not use switches at all. Instead, create mail_subject and mail_message, etc...
task variables and iwsend_mail will take values from there.

magikandrea

Thank you very much for your help.