Review/Email Task setup using WFM

gir

Hi,

I need help in configuring Email/Review Task mail setup.
I am using wfm to build the workflow, sending a mail through external task is not giving any issues i,e by using ipl files. But I would like to use the existing functionality of wfm. I am using
mail template as reviewerNotification.xsl
class as ReviewerMailNotificationTask class. configured iw.cfg [iwsend_mail] setup but not getting any mails.

The servletd_out.log file shows
2009-05-09 01:05:11,711 [http-8080-Processor24] WARN com.interwoven.ui.teamsite.workflow.task.urltask.ReviewerMailNotificationTask ([my teamsite id] commandID iw.teamsite.urlexternaltask) - Job variable due_date=[] in job id=[26770] could not be parsed.

not able to figure out the issue. please help

Thanks

Adam Stoller

Hi, I need help in configuring Email/Review Task mail setup. I am using wfm to build the workflow, sending a mail through external task is not giving any issues i,e by using ipl files. But I would like to use the existing functionality of wfm. I am using mail template as reviewerNotification.xsl class as ReviewerMailNotificationTask class. configured iw.cfg [iwsend_mail] setup but not getting any mails. The servletd_out.log file shows 2009-05-09 01:05:11,711 [http-8080-Processor24] WARN com.interwoven.ui.teamsite.workflow.task.urltask.ReviewerMailNotificationTask ([my teamsite id] commandID iw.teamsite.urlexternaltask) - Job variable due_date=[] in job id=[26770] could not be parsed. not able to figure out the issue. please help Thanks

That's a warning - not an error. While it is possible it is preventing the emails from getting sent, it's difficult to know without doing more debuggnig (looking through every possible log file, looking at the Java code involved (if you have access to it) or writing your own email class in its place (if you don't have access to the origingal code) so that you can add your own debugging.

The other possibility is that you can explicitly add a job variable called due_date to your workflows and make sure it has a default value of <today</> (the date on which the workflow is initiated) and see if that "resolves" the problem.