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

workflow email

SecretHen

Hi
Got stuck starting out with workflow and email. Email works quite nicely from the command line and a call such as this
/usr/iw-home/bin/iwsend_mail.ipl -t SecretHen -c OldDog -f Hen@Farm.com -m "Can you dig it?" -s "workflow test"
will succesfully generate an email.

Tryingt to insert a <command v=...> into the workflow, but cannot figure out where it should go - the developer's guide provides information on syntax but is somewhat coy on positioning.

Have tried various places, but usually get the error
Invalid workflow:
xml processing instruction not at start of external entity at line 2
ERROR:00001: Failure in operation

Can anyone give me some quick guidance.
Thanks in advance
SecretHen

Find more posts tagged with

Comments

Jeremy

Hi,

Try the following - or is this what you were already trying?

<command v='/usr/iw-home/bin/iwsend_mail.ipl -t SecretHen -c OldDog -f Hen@Farm.com -m "Can you dig it?" -s "workflow test" /'>

OR

<command v='/usr/iw-home/bin/iwsend_mail.ipl -t SecretHen -c OldDog -f Hen@Farm.com -m \"Can you dig it?\" -s \"workflow test\" /'>

SecretHen

this is what I am trying - my question is where in the file it should go. I am attempting to put the line in the .wft file, within <usertask> directly after <successors>

Michael

Hi,

If I understand your post correctly you are unsure where the command element should go in your WFT file.

Here is an example of that:
<externaltask lock = "f" name = "Send_final_email" owner = "__INSERT__($owner);" retry = "f" start = "f">
<areavpath v = "__INSERT__($vpath);"/>
<successors>
<successorset description = "Go to Audit_log">
<succ v = "Audit_log"/>
</successorset>
</successors>
<command v = "__INSERT__($email_end);"/>
<activation>
<or>
<pred v = "Move_to_snapshot"/>
</or>
</activation>
</externaltask>

$email_end is a previously defined variable with the command path in it.

If I have missed the point of your post, I apologise. Hope this helps.

Cheers
Michael

SecretHen

Thanks for that. I have tried what you suggested.

Specifically I have defined a variable
my ($mail_cmd) = "<command v='/usr/iw-home/bin/iwsend_mail.ipl -t SecretHen -c OldDog -f bla\@bla.com -m \"Can you dig it?\" -s \"workflow\"'/>";
at the top of the file.

At the foot, have inserted
<externaltask lock = "f" name = "Send_email" owner = "__INSERT__($owner);" retry = "f" start = "f" description="Send a mail">
<areavpath v = "__INSERT__($vpath);"/>
<command v = "__INSERT__($mail_cmd);"/>
<activation>
<pred v = "Author_Work"/>
</activation>
</externaltask>

and included Send_email as one of Author_work's successors.

Still get the same message though.

Adam Stoller

my ($mail_cmd) = "<command v='/usr/iw-home/bin/iwsend_mail.ipl -t SecretHen -c OldDog -f bla\@bla.com -m \"Can you dig it?\" -s \"workflow\"'/>";
at the top of the file.

At the foot, have inserted
<externaltask lock = "f" name = "Send_email" owner = "__INSERT__($owner);" retry = "f" start = "f" description="Send a mail">
<areavpath v = "__INSERT__($vpath);"/>
<command v = "__INSERT__($mail_cmd);"/>

You've nested the XML within the XML - either remove the XML from the definition of $mail_cmd or change the latter usage to be just: __INSERT__($mail_cmd); - without any XML wrapping it.

--fish
(Interwoven Senior Technical Consultant)

SecretHen

sorry - you are quite correct - spotted that after I posted. Correcting it does not improve matters, however. I get the same message whether the command is defined within a variable and then called later (as suggested) or of it is inserted directly.

Am now completely baffled

Help

lhdavis

Could you attach your workflow file? It could be another error within the file unrelated to the external e-mail task.

Michael

I am getting a feeling that for some reason your XML workflow instance is not well formed. Could you experiment with removing the quotes from your command line and passing single word arguments.

Bit of a wild stab in the dark I know Smiley Happy

Cheers
Michael

13adam13

In your excerpt, you are missing the elements for successors.
When adding that back in, be sure that you list successors, then command, then activation. As crazy as it seems, I have found that switching the order of the XML tags breaks things.
I know that it shouldn't, I just call em like I see em.

--Adam Wilson
Senior Programmer

Adam Stoller

Actually, switching the order of sub-elements *should* break things according to the DTD - which does specify an order in which sub-elements may be used. Nothing crazy about it (unless you want to say that XML is crazy for requiring it?)

However - I'm a bit ashamed at myself for not catching the missing required elements (I guess I thought the post was just an excerpt and was only responding to what was there, and not what wasn't there) - good catch!

--fish
(Interwoven Senior Technical Consultant)