public class SendTaskEmailsListener extends OCSendEmailListenerBase implements org.activiti.engine.delegate.TaskListener
Constructor and Description |
---|
SendTaskEmailsListener() |
Modifier and Type | Method and Description |
---|---|
protected java.util.List<java.lang.String> |
findValidEmailAddresses(java.lang.String ticket,
org.activiti.engine.impl.persistence.entity.TaskEntity task) |
protected java.lang.String |
getEmailBodyTemplate(java.util.Map<java.lang.String,java.lang.Object> emailModel)
Get the FTL template to use for the email body.
|
protected java.lang.String |
getEmailSubjectTemplate(java.util.Map<java.lang.String,java.lang.Object> emailModel)
Get the FTL template to use for the email subject.
|
void |
notify(org.activiti.engine.delegate.DelegateTask delegateTask) |
protected void |
sendTaskEmail(java.lang.String ticket,
java.lang.String emailAddress,
java.util.Map<java.lang.String,java.lang.Object> emailModel)
Send a task email to the given email address
|
getEmailModel, getEmailModel, getProcessDefinitionName, getTaskURL, sendEmail, sendEmail
public void notify(org.activiti.engine.delegate.DelegateTask delegateTask)
notify
in interface org.activiti.engine.delegate.TaskListener
protected java.util.List<java.lang.String> findValidEmailAddresses(java.lang.String ticket, org.activiti.engine.impl.persistence.entity.TaskEntity task)
protected void sendTaskEmail(java.lang.String ticket, java.lang.String emailAddress, java.util.Map<java.lang.String,java.lang.Object> emailModel)
ticket
- delegateTask
- emailAddress
- protected java.lang.String getEmailBodyTemplate(java.util.Map<java.lang.String,java.lang.Object> emailModel)
ActivitiConfig.getTaskEmailTemplate()
.
Overriding subclasses can utilize the model to get different templates as necessary. For
example, different tasks could have different templates.emailModel
- the email modelprotected java.lang.String getEmailSubjectTemplate(java.util.Map<java.lang.String,java.lang.Object> emailModel)
ActivitiConfig.getTaskEmailSubjectTemplate()
.
Overriding subclasses can utilize the model to get different templates as necessary. For
example, different tasks could have different templates.emailModel
- the email model