Mail task

Mail task activity is used for sending mails to receiver in another process or Swimlanes. It is necessary to set up an email server via configuration since there is no mail server.


Exclusive	When it receives a special job from a specific process example, it makes jobs run in order.
Execution listeners	Listeners for an activity, process, sequence flow, start and end event.
Multi-instance type	Determines if multiple instances of this activity are created.
Cardinality (Multi-instance)	An expression or numeric value determines how many instances are created.
Collection (Multi-instance)	The number of instances is determined by the elements of a collection. For each element in the collection, a new instance is created.
Element Variable (Multi-instance )	The variable under which each element is available to the newly created instance.
Completion Condition (Multi-instance)	An expression that, if it evaluated to `true` , stops the creation of new instances.
Is for compensation	A flag that identifies whether this activity is intended for the purposes of compensation.
Headers	Line separated mail headers.
To	The recipients of the email. Multiple recipients can be defined in a comma-separated list.
From	The sender email address. If not provided, the default configured “from address” is used.
Subject	The subject of the email.
Cc	The CC (Carbon Copy) recipients of the email. Multiple recipients can be defined in a comma-separated list.
Bcc	The BCC (Blind Carbon Copy) recipients of the email. Multiple recipients can be defined in a comma-separated list.
Text	Text of the email in clear text. If HTML is not supported on the receiver’s end, the text version of the email is displayed.
Html	Content of the email in the HTML format. This allows for the creation of rich formatting and the usage of images.
Charset	Character set to be used in the email.

Execution listeners examples

You can use the Execution listeners as shown in the examples.

Start

End

Take

Multi-instance type examples

You can use the Multi-instance type as shown in the examples .

Default, only one instance is created:

None

Activities are created in parallel. This is a good practice for User tasks activity:

Parallel

Activities are created sequentially. This is a good practice for Service tasks activity:

Sequential

Cardinality (Multi-instance) examples

You can use the Cardinality (Multi-instance) as shown in the examples.

${number}

2

Collection (Multi-instance) example

You can use the Collection (Multi-instance) as shown in the example.

2

Element variable (Multi-instance) example

You can use the Element variable (Multi-instance) as shown in the example.

elementvar

Completion Condition (Multi-instance) example

You can use the Completion Condition (Multi-instance) as shown in the example.

true

${variable==True}