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 modeler email task

System

Hi
i create simple workflow with email task but i am not able to receive anything. i don't get any error but no email is received. attached is output xml file.
thanks in advance
ts 6.7.1 sp3 wfm 1.0.0 windows 2003 sp1

Find more posts tagged with

Comments

nbwoven

1.Did you populate any settings in the iw.cfg for the EMails to work ?

2.Were you able to save this Model to the TS Server or are you working offline . Pls verify under "IWServer\iwadmin\main\workflowModels\ WORKAREA\iw-wa" that all files are copied.

3. If you are on TS671 SP1 then make sure you upgrade the WFM-1.0 SP1 too.

Migrateduser

Thanks for quick response
Yes i did populate the iw.cfg file including email mapping file
and i am able to instantiate the workflow, but the email portion of the job is not working everything else is fine. i am on ts 6.7.1 patch 3 so i have not upgraded it to service pack 1 yet.

nbwoven

Pls Rule out any connectivity issues from the Teamsite Server to your MTA .
If the email server is an external Server then try

telnet mailserver.domain.com 25 from the teamsite Box .

Migrateduser

that is right. actually the mail application is running within teamsite server. so i have teamsite and mail server software running in the same machina. other workflow tasks are running fine ie able to send email out but just when i use workflow modeler and i create email task does not work.
thanks again

Migrateduser

Here is an error i am noticing on the out log file.
Can't call method "GetId" on an undefined value at d:/iw-home/local/config/wft/solutions/iw_solution_email.ipl line 394.

Migrateduser

How does it email task sets the from field value in a email. does it users OWNER value as the from or something else. currently i have the OWNER value being IW_USER and i am not able to receive anything eventhough all the users emails are mapped in email mapping file.
but still got the following error in the outfile

SMTP RCPT command failed:
5.5.4 Invalid Address

at

\iw-home/local/config/wft/solutions/iw_solution_email.ipl line 898

other workflow are able to send email without any problem.
tanks in advance

Silix

Here is an error i am noticing on the out log file.
Can't call method "GetId" on an undefined value at d:/iw-home/local/config/wft/solutions/iw_solution_email.ipl line 394.

How did you resolve this error ? Im seeing this one.

Adam Stoller

How does it email task sets the from field value in a email. does it users OWNER value as the from or something else. currently i have the OWNER value being IW_USER and i am not able to receive anything eventhough all the users emails are mapped in email mapping file.
but still got the following error in the outfile

SMTP RCPT command failed:
5.5.4 Invalid Address

at \iw-home/local/config/wft/solutions/iw_solution_email.ipl line 898

other workflow are able to send email without any problem.
tanks in advance

Please provide the properties you set on the Email Task in WFM. You should have at least two PTs defined, and you should have a "-t taskname" appended to the command line for iw_solution_email.ipl

The From address usually comes from the owner of the Email Task - though it may require looking up in the iwhome/local/config/wft/solutions/email_map.cfg file to try to turn it into a valid email address.
The To address generally comes from the owner of the task specified with the "-t" flag on the command line.

Also - depending on how your SMTP is configured, it may or may not accept the From line as given.

Migrateduser

Fish-thanks for your reply.
Attached are both .ipm and .xml files. As i said at my posting, i am just doing simple workflow using WFM and it consists of usertask->emailtask->exittask
thanks

moonkhanna

Cabicha,

I checked your ipm just now. As Adam stated you need to use the -t "Task name" option after the command so basically your command will look like the below -

$IW_HOME/iw-perl/bin/iwperl $IW_HOME/local/config/wft/solutions/iw_solution_email.ipl -t "UserTask2"

Basically, the task name supplied with -t option as above would be the task for which the email task sends email for i.e. the owners of the task will receive the email from the email task.

Hope, that helps..

Best Regards,

Munish Khanna

Migrateduser

Munish
Thanks a million it worked. I guess the software manual should have contain this information.
again thanks i have been struggling with this for 2 days.

moonkhanna

Hi Cabicha,

you are welcome! This is in the manual which explain the iw_solution_email.ipl functionality. I do not have the manual name on top of my head but it should be some workflow dev manual.

Check it out and happy wf modeling! :-)

Best Regards,

Munish Khanna

Adam Stoller

Hi Cabicha,

you are welcome! This is in the manual which explain the iw_solution_email.ipl functionality. I do not have the manual name on top of my head but it should be some workflow dev manual.

Check it out and happy wf modeling! :-)

Best Regards,

Munish Khanna

It's covered in Appendix D of the WFM 1.0.0 guide - and starting around page 144 in the Workflow Developer's Guide for 6.7.1SP1

Vips

As Ghoti said -t "taskname" is missing in your Model. Task name has the name of the next task however in your case the next task is the end task and I am not sure if its going to work for you.
Try putting the task name as the "end task" name however if it doesnt work please try adding a new task after mail task and see if that works..

Adam Stoller

As Ghoti said -t "taskname" is missing in your Model. Task name has the name of the next task however in your case the next task is the end task and I am not sure if its going to work for you.
Try putting the task name as the "end task" name however if it doesnt work please try adding a new task after mail task and see if that works..

It's not actually the name of the next task - it's the name of the task or tasks (you can have multiple -t flags on the command line) to get the owner of to use as the recipient(s) of the email.

So specifying the end task would probably be wrong - specifying the first task in the workflow owned by iw_user would work though.
Alternatively, if you write you own custom PT for managing the headers of the email message to be sent - you could hard-code the header fields or generate them through some other means - and it should work.

Migrateduser

Fish, thank you for your help.
it worked, but the question i have now is how easy it is to modified the custom template used to generate the email. i need to modified the content of the Author_iwmailbody.ipl.
also i have simple workflow i created using wfm that send email to content author if the content is rejected(this part work) but the author click on the finish button in the email it receiving error(the task is no longer active) is that normal or i am making mistake.
thanks for your help again.

Adam Stoller

Fish, thank you for your help.
it worked, but the question i have now is how easy it is to modified the custom template used to generate the email. i need to modified the content of the Author_iwmailbody.ipl.
also i have simple workflow i created using wfm that send email to content author if the content is rejected(this part work) but the author click on the finish button in the email it receiving error(the task is no longer active) is that normal or i am making mistake.
thanks for your help again.

The PTs are PTs - you write / debug them the way you write / debug standard FormsPublisher PTs - except that the XML that's being processed is job data (if you enable debugging and/or verbosity in the iw_solution_email.ipl script you'll see a lot more information and the XML job output is saved - I believe somewhere within iwhome/tmp/ so you can play around with that using iwpt_compile.ipl

If the message contains links to a task that is no longer active - then yes, clicking on those links will display an error.

So you either customize the PT not to display those links and/or train the users to understand the error (even in "good" emails - if you go back to one that was processed before you'll see the links and they won't work ...)