Procedures and Email Notifications

Question

boldEN*bold*
Hi everyone!!
In my BPM development, i'm trying to automatize the email notifications, based on due process periods. Also, I need to inform, based on the delay, some other participants that escalates the alarm message.
Is it possible to do it using an "E-Mail Notification" component that can be reused during all the process, even that the interval conditions and informed users varies upon each activity.
Is there another way to solve it?
Thanks
boldSP:*bold*
Saludos a todos!
En mi desarrollo BPM requiero automatizar el proceso de envio de email, al caducar ciertas actividades. Basado en ello, el tiempo de caducidad varia de acuerdo a cada actividad y al usuario, ya que varian tanto los intervalos de aviso, como los correos y su escalamiento en caso de demoras mayores a lo solicitado.
Pienso que es posible tomar un procedimiento especializado que permita ser reutilizado en este y otros proyectos, a pesar de que requiera parametrizar tanto los usuarios "base" y "escalados", como los intervalos de alarmas, durante el proceso.
¿ Existe otra forma de realizarlo?
Gracias,

Answer 1

I think I understand what you're after. I think you want to use the same escalation logic for all of your processes and instead of embedding this in every process you want something reusable. If this is not the case, read no further.
While you can do this, there are still going to be 5 things each process would still need to have inside of them:
<li> your process would need to set the "deadline" predefined variable to the intial timeout (2 hours in the future in your example)
<li> your process would need an Exeption Handler needs to be added with an Exception transition set to "Instance Expiration"
<li> your process would need an Integer instance variable "alertLevel" to keep track of the current level
<li> your process would need a String instance variable "currentlyAssignedTo" to keep track of who's supervisor you want to notify
<li> your process would need an Automatic activity with one line of logic inside it.
You could have the Exception transition leaving the Exception Handler activity go to a subprocess using a Subflow activity. This subprocess would send the emails, determine the new deadline interval, determine the new priority of the instance, look up the currently assigned user, manager and supervisor's email addresses and send the email(s). The subflow would have two input argument variables (alertLevelArg and currentlyAssignedToArg). In the Begin activity, these arguments would be mapped to corresponding instance variables. Inside this subprocess there would be an automatic with the logic to send the email to the user / manager / supervisor based on the alertLevel instance variable. This subprocess would pass back out through its output argument variables the new alertLevelArg, and new deadline (a time argument variable set to some time in the future based on the new alert's level).
Once the instance in the called subprocess completes, the output arguments need to be mapped to the original process's "alertLevel" and "deadline" variable. From the Subflow activity, you'd have an unconditional activity that flows into an Automatic activity via an unconditional transition. This automatic activity would have the single line of logic "action = BACK" so the instance is sent back from the Exception Hanldler's flow back to the activity inside the process it was in when the Instance Expiration exception occurred.
Avoid hard coding the values of "2" and "5" and "8" for the number of hours to have elapse inside your logic. Instead make them business parameters capable of being edited by an business owner.
Dan