Page Comparison

This How To will take you through the configuration of the JEMHC Postfunction to drive notifications in response to workflow changes.

...

After a short time, the JEMHC Postfunction editor will be shown.  Select an existing Ad hoc Template Set, the basic one created earlier will be in the drop down, remember to set TEXT as the format (as the example Template Set only provides that, and of course, the correct Ad hoc Template Set itself: 

For testing I'm going to set a static addressee to start with in the TO: recipient tab:

...

Email Addresses	This is a comma separated list of simpleemail adddresses
Address Custom Fields	These are TEXT type custom fields (single or multi-line) that contain comma separated simple email addresses
Notify Reporter	Yep, that.
Notify Assignee	Yep, that.
Notify Watchers	Yep, that.
Notify Current User	Includes the user who triggered the change.
Notify Project Lead	Yep, that.
Notify Component Leads	Yep, that.
Notify SD Request Participants	If enabled, and JSD is installed (we should probably hide this if JSD is not installed) then the users within this field will be notified
Notify Users	This is a comma separated list of usernames. Usernames require the 'workaround' user defined in the Workaround tab in order to lookup the users address
User Custom Fields	User picker type custom fields (single or multiple) to include users for notification

From

Sender Email Address can be defined, this is the literal from: address, varying it is useful in some situations but your outbound Mailserver must allow it, various outcomes will occur if it does not ranging from the default (connecting) account being used instead (Gmail), to no mail being sent at all (Exchange).

...

Any value present in the Webhook payload can be used in a notification, here are some examples:

(TODO)

How Many Emails Get Sent?

The behaviour of email-based postfunctions is that one email is sent that includes every recipient (To, CC, BCC).

Related articles