email notify task question

I've been having a bit of an issue trying to get a simple notify email task to work properly. Its been a long time since my last Interwoven class. I've been using the 5.5.2 workflow manual as reference for this bit of code below p. 184. I've also looked at several posts and am hoping someone will be able to point out what I'm doing incorrectly in the attached code.

If I use the Interwoven shipped workflows the email notification works fine. The issue is naturally my code not working with this specific email notify task. There seem to be several posts but I didn't see one that addressed my specific issue.

Platform: Solaris
Version 6.1
Email Client - Lotus Notes (if it matters)

Error: Is invalid workflow
Error: No successor for task Email_Notify

The main issue: Although I appear to have coded this correctly per the documentation, there is still an error.
A sucessor in the task is there although the error message advises one is not present.

It seems from looking at the documentation in various places, a clear example of how to code this has eluded me.

If I remove the Email_Notify task, the workflow has no errors and is successfuly tested.

thanks in advance for looking at my issue.
Any advice would be helpful - I'm at the the point that I'd like burn TFM but am reading it.

Find more posts tagged with

Comments

kaalraa

Antonson,

As per your attached code... there is no successor element which is parent element of successorset element.

Put the same in all of your tasks. Hope that would work fine.

Adam Stoller

Antonson,

As per your attached code... there is no successor element which is parent element of successorset element.

Put the same in all of your tasks. Hope that would work fine.

That's not entirely right - with respect to the submittask, they do not have a successors element - only a successorset -or- a success and optional failure element.

However, you are right with respect to the externaltask - as it requires a successors container around the successorset elements.

kaalraa

Thanks Adam... for making me clear in this regard as well. Simply superb.... as this can only be learnt through experience and that too under the guidance of a person like you.

That's not entirely right - with respect to the submittask, they do not have a successors element - only a successorset -or- a success and optional failure element.

However, you are right with respect to the externaltask - as it requires a successors container around the successorset elements.

Migrateduser

I've added the required code but am still not getting an email sent, any advice would be appreciated. There are no errors when the workflow was invoked.

thanks - c