How to configure group of Reviewers in reviewer_iwmailheader.tpl

vbaijal

Hi All,

I need to send email notification to a dynamic group of reviewers which are selected at runtime by the workflow initiator.
I am using WFM 1.0.0.1 and iw_solution_email.ipl to do the same.The ipl file refers to reviewer_iwmailheader.tpl to get the and users

[html]



[/html]

How to use this to configure n number of reviewers?

Thanks in advance,
Vijaya

Adam Stoller

Hi All, I need to send email notification to a dynamic group of reviewers which are selected at runtime by the workflow initiator. I am using WFM 1.0.0.1 and iw_solution_email.ipl to do the same.The ipl file refers to reviewer_iwmailheader.tpl to get the and users [html] [/html] How to use this to configure n number of reviewers? Thanks in advance, Vijaya

You need to adjust the code to first see if

dcr.workflowinformation.task[1]@owner =~ /\bno user\b/

(or something like that) - if it does, it means you're dealing with an un-owned grouptask - alternatively you should be able to access the type of task to which

dcr.workflowinformation.task[1]

refers (i.e.: is it a grouptask). If that is the case - you need to iterate through the list of sharedby members (if memory serves correctly, the container element in the XML dump is

users

- not

sharedby

and the sub elements are either

<user v="..."/>

or

<group v="..."/>

) For each sub element, you then retrieve the value of the attribute

v

and use that to output your mapping - e.g.:

<iwov_emailmap user='{iw_value name="loop_iterator@v"/}' />

.

Play with it a bit - enable the $DEBUG flag in iw_solution_email.ipl and look at the debugging file that gets placed in IWHOME/tmp to see what the results are - it may take a few tries, but you should be able to get it.

Note: In recent versions of TeamSite I've noticed an unfortunate caching effect where grouptask's without retainowner="t" - still seem to hold on to the previous task-taker as 'owner' if they are passed through again - so if you know all your grouptasks are set not to retain ownership - it's best to base your conditional on whether the target task is a grouptask or not, rather than if the owner is set to "<no user>". Alternatively (and I haven't yet tried this) make sure that you do a reset of the grouptask in whatever task begins the loop backwards - that might force the clearing of the cached owner.