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

Dynamic subject using Email Task

auli

Hi,

Can we set the subject in the Email task in WFM at runtime. Does it require a change in the XSL templates? I tried giving a variable like mail_subject as we used to do in WFTs but it didnt work. Any pointers would be of great help.

Find more posts tagged with

Comments

auli

I guess I got it. We need to use the custom java class for sending Email and write the logic there itself.

Jcse

I guess I got it. We need to use the custom java class for sending Email and write the logic there itself.

Yes that is one of the best solution to set subject dynamically.Actually if you will use URLExternalTask for sending mail ,then you have the scope for dynamically setting all the required mail parameters like senders,recipients ,body etc.

But in case of using EmailTask of the WFM ,we don't have so much freedom to do this.

There is another solution you can use $IW_CV(configurable variable) for setting the subject making certain conditions based on Script Variables and Conditional Links.But this is an complex and not so flexible solution.If one is good at java he should go for first approach.

CRB

Actually if you will use URLExternalTask for sending mail ,then you have the scope for dynamically setting all the required mail parameters like senders,recipients ,body etc.

But in case of using EmailTask of the WFM ,we don't have so much freedom to do this.

i beleive you have all the freedom you need to set all mail parameters from an email task. as long as you set classname variable to your custom classname which has your code to set the parameters. so i think using email task with custom mail java class is simpler than using external task.

Adam Stoller

i beleive you have all the freedom you need to set all mail parameters from an email task. as long as you set classname variable to your custom classname which has your code to set the parameters. so i think using email task with custom mail java class is simpler than using external task.

That's an interesting conclusion given that Interwoven provides a reasonably robust and flexible solution (iw_solution_email.ipl) OOTB for external tasks, but instead provides an unstable (due to CSSDK limitations on GroupTasks) and un-flexible OOTB Java solution for EmailTasks.

santosh013

Hi All,
Email Task itself internally calls URLExternalTask. And by using URLExternalTask,you have the scope for dynamically setting all the required mail parameters desired by you.
The only thing is that You should be quite comfortable writing Java classes.

So it depends on individuals that whether S/He is familiar with ipl or writing java classes.

Both have the same flexibility,but the catch is that we are gradually shifting towards java.

Adam Stoller

Hi All,
Email Task itself internally calls URLExternalTask. And by using URLExternalTask,you have the scope for dynamically setting all the required mail parameters desired by you.
The only thing is that You should be quite comfortable writing Java classes.

So it depends on individuals that whether S/He is familiar with ipl or writing java classes.

Both have the same flexibility,but the catch is that we are gradually shifting towards java.

Perl vs Java is a subjective / religious issue - that's fine.
I'd say that both ultimately have the same flexibility - OOTB however, the Perl "base program" is more complete and flexible than the Java "base classes" provided.

provide for dynamically setting the subject line of the email. You can, however, write your own Java class (based on the example code that Interwoven provides) to provide for that additional functionality. If you're planning on having GroupTasks act as "target tasks" for the email notification though - right now you'll be better served by using an ExternalTask and running iw_solution_email.ipl.

auli

If you're planning on having GroupTasks act as "target tasks" for the email notification though - right now you'll be better served by using an ExternalTask and running iw_solution_email.ipl.

Thanks for all the replies. Finally, we have implemented the emails using external task Smiley Happy