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

WFM, emails and customizations

nipper

ok, starting with the LiveSite WFM.

Issue is with review task and the email

Desire is to have a 2 day timeout & send another email to the user, after 4 days timeout, send email to the web team and a 7 day timeout email goes to the director.

OK, so you cannot have mulitple timeouts per task.

So I need a 1 day timeout, that will go to an external task which will decide what email gets sent (if any) and restarts the review task. In a WFT I could have 1 external task set a WF variable the mail would read for email address and subject.

My Q is how can I do this in WFM ? Can I set some data and make the email push to the correct spot ? My other choice is have 3 different email tasks.

Tips/pointers/RTFMs appreciated. Am I incorrect or is there a serious lack of docs (& sample code) for WFM external tasks ? I tried digging in the LS external tasks but they seem to be compiled code.

Find more posts tagged with

Comments

Faizi

ok, starting with the LiveSite WFM.

Issue is with review task and the email

Desire is to have a 2 day timeout & send another email to the user, after 4 days timeout, send email to the web team and a 7 day timeout email goes to the director.

OK, so you cannot have mulitple timeouts per task.

So I need a 1 day timeout, that will go to an external task which will decide what email gets sent (if any) and restarts the review task. In a WFT I could have 1 external task set a WF variable the mail would read for email address and subject.

My Q is how can I do this in WFM ? Can I set some data and make the email push to the correct spot ? My other choice is have 3 different email tasks.

Tips/pointers/RTFMs appreciated. Am I incorrect or is there a serious lack of docs (& sample code) for WFM external tasks ? I tried digging in the LS external tasks but they seem to be compiled code.

Hi Nipper,

As per my understanding there would be two approach:

First:
If you can set the time frame as 2-4-6 in order then a single timeout link can perform in loop of 2 days with an Email Task. For this you need to write a custom mail notification class (java). In which you can handle that who to send email. For this can check number of times Review Task activated. For example if Active=1(2 days) then send mail to user again.
if Active=2(4 days) then send mail to Web Team.
if Active=3(6 days) then send mail to Director.
and so on.

Second:
If you bind with the time frame of 2-4-7 in order then an External Task need to come between Review Task and Email Task, that is you have already mentioned. Again need to write custom mail notification class for sending email to different users.

There is a sample email class (

MailNotificationTask.java

) that is located at

iw-home/local/config/lib/content_center/customer_samples_src/src/com/corp/custom

folder.

Hope this helps.
Thanks.

Jcse

Hi Nipper,

As per my understanding there would be two approach:

First:
If you can set the time frame as 2-4-6 in order then a single timeout link can perform in loop of 2 days with an Email Task. For this you need to write a custom mail notification class (java). In which you can handle that who to send email. For this can check number of times Review Task activated. For example if Active=1(2 days) then send mail to user again.
if Active=2(4 days) then send mail to Web Team.
if Active=3(6 days) then send mail to Director.
and so on.

Second:
If you bind with the time frame of 2-4-7 in order then an External Task need to come between Review Task and Email Task, that is you have already mentioned. Again need to write custom mail notification class for sending email to different users.

There is a sample email class (
MailNotificationTask.java
) that is located at
iw-home/local/config/lib/content_center/customer_samples_src/src/com/corp/custom
folder.

Hope this helps.
Thanks.

Hi

I think these are the possible solutions for this problem.As per my suggestion the second-one will be the most appropriate to implement.Because in the second we are not binding the time-frame which is an major point to be considered.

Whereas for first one it will be a little easier than second ,But it involves certain limitations and constraints.

But again it depends on the actual requirement and the client that "How he wants the things to work and to be present ?"

nipper

Actually my plan was a 1 day timeout. If it is 2 days old, resend reviewer email, 4 days, send web team, 7 days old send director. Otherwise go back to the review task after doing nothing.

I really wanted to do this with the "normal" WFM tools, but not to certain that I can. My plan is to timeout to a external task (perl) which will check time from start and kick off the iw_send_mail.ipl if needed.

Adam Stoller

Actually my plan was a 1 day timeout. If it is 2 days old, resend reviewer email, 4 days, send web team, 7 days old send director. Otherwise go back to the review task after doing nothing.

I really wanted to do this with the "normal" WFM tools, but not to certain that I can. My plan is to timeout to a external task (perl) which will check time from start and kick off the iw_send_mail.ipl if needed.

Consider that if every time you timeout you send email and then transition back to the task that timed out - that you also need to track the first time the task was activated as opposed to the most recent time it was activated - and, if it is possible to loop back to this particular task (e.g. due to a review rejection) - you need to also be able to distinguish between a task which has timed out N times in a row versus a task which timed out after having been activated N times from a looped process...

Personally, I don't think that WFM provides anything that specifically helps with email notification escalation - I think it ends up having to be a custom script / program that utilizes (among other things) task and/or job variables to maintain state and interact with task attributes like timeout value, owner, etc. as needed.

CRB

from my experience with wfm:
1) you will need a custom email task which takes parameters such assender/recipient email address, subject,...

2) the way i would handle same review task with different timeouts (2,4,6 days) in WFM: is to set some global variables ( one would be a counter = 0 and the other is an email-address to be used by your custom email task). then have your review task tansition on 2days timeout link to an external task.

the external task will check the counter, if this is the first 2-days timeout (which means counter =0), then set the counter = 2 and the email-address variable to reviewer email then transition to your custom email task then back to review task.
if your review task timesout again (on 2days timeout link), it tansitions again to the external task which checks the counter and finds that it has been 4 days because the counter = 2 already... here you set counter=4 and set email-address variable to webteam email, then transition to your custom email task and back to the review task.
in case of the review task times out again (on 2 days timeout link which makes it 6 days total), your external task should set the counter=6 and the email-address variable to the director's email and from there decide if you want to go back to your review task or do something else

i could also acheive this using duplicate tasks, OR gate, conditional links and script variables... i am sure there are many ways to do this... but that is what i can think of now...

let me know if you need help with the custom email task, i always have one ready...

Adam Stoller

from my experience with wfm:
1) you will need a custom email task which takes parameters such assender/recipient email address, subject,...

2) the way i would handle same review task with different timeouts (2,4,6 days) in WFM: is to set some global variables ( one would be a counter = 0 and the other is an email-address to be used by your custom email task). then have your review task tansition on 2days timeout link to an external task.
the external task will check the counter, if this is the first 2-days timeout (which means counter =0), then set the counter = 2 and the email-address variable to reviewer email then transition to your custom email task then back to review task.
if your review task timesout again (on 2days timeout link), it tansitions again to the external task which checks the counter and finds that it has been 4 days because the counter = 2 already... here you set counter=4 and set email-address variable to webteam email, then transition to your custom email task and back to the review task.
in case of the review task times out again (on 2 days timeout link which makes it 6 days total), your external task should set the counter=6 and the email-address variable to the director's email and from there decide if you want to go back to your review task or do something else
i could also acheive this using duplicate tasks, OR gate, conditional links and script variables... i am sure there are many ways to do this... but that is what i can think of now...

let me know if you need help with the custom email task, i always have one ready...

I'd consider using a separate configuration file - probably in XML format that specifies the task name, the count threshold, and the recipients for that threshold (either as symbolic names "TASK_OWNER", "JOB_OWNER", etc. or as userids or email addresses) and have the timeout transition to an externaltask (or similar) that references the config file and either task or job variables (not sure which would be better off the top of my head) to then initiate a more generic email process, passing along the parameters as needed.
Not all that dissimilar from what you suggested, but I think its a bit better than completely specializing the email program itself.

CRB

Not all that dissimilar from what you suggested, but I think its a bit better than completely specializing the email program itself.

haha of course it is better (if ghoti says it, then it is better) JK... i think using config file is usually a cleaner and easier to maintain ( in case of some requirements (email address, threshhold...) change...

IE_Vs_Chrome.png

Chrome.png

Migrateduser

Hi,

I had this exact same requiremet, but mine was to send an email every 8 business hours on business days. I created a custom perl script and configurable task variables to accomplish this. Private message me if you want more detail.

Thanks,
James

HSR10053_Video_Session_Duration_Distribution.rptdesign