Mailing rules store information about how to craft and send an e-mail.
MailingPipegraph is a System pipegraph which consumes Event objects.
MailingPipegraph is a System pipegraph which consumes Event objects.
In order to activate the event consumption, the user has to properly define the mailing-pipegraph configuration properties in the event-engine section .conf files. MailingPipegraph configuration is composed by a MailWriter definition and a list of ETL configuration objects. The user can generate an arbitrary number of event mailing flow by defining as many configuration objects.
The MailWriter configuration stores the information required to access the smtp-server with the given account.
For each described event mailing flow, it will be spawned a dedicated ETL. Event consumption ETLs are composed by: * A single source of Event objects from a Kafka topic * A set of rules which trigger the creation of an Event object.
+--------+ +--------+ +--------+ | Event | | Event | | Event | | Source | | Source | | Source | +---+----+ +---+-+--+ +--------+ | | |----------+ | | | | | +---v----+ +---v----+ +---v----+ +---v----+ | Event | | Event | | Event | | Event | |Consumer| |Consumer| |Consumer| |Consumer| | ETL | | ETL | | ETL | | ETL | +--------+ +--------+ +--------+ +--------+ | | | | | | | | | +-v--------v-+ | | | Mailer | | +----------- > Sink <-------------+ +------------+
Different ETLs can have the same source of data, but all ETLs will have the same Mailer Sink.
Update: MailingPipegraphModel read a isSystem flag from configuration which declares whether or not the Pipegraph should be automatically started when starting Wasp with the startSystemPipegraph option. The default value in case the isSystem keyword is not present is false
Mailing rules store information about how to craft and send an e-mail. Mailing rules store an SQL statement which indicates whether or not an e-mail should be sent for the specific Event, and another statement to enrich it with mail subject. In the mailing rules are also specified mail recipient info to use, and the path to the velocity template to use to compose the e-mail.
is the name of the MailingRule
defines whether a Mail should be sent or not
enrich the mail with a subject. WARNING: this statement is ignored if the mail aggregation options is enabled. FIXME: avoid
is the path to the velocity template to use to compose this e-mail. It has to be available in the driver.
is the main recipient of the e-mail. Can be a single address or a list of comma separated addresses
is the optional CC recipient of the e-mail. Can be a single address or a list of comma separated addresses
is the optional BCC recipient of the e-mail. Can be a single address or a list of comma separated addresses