Advanced Techniques - Setting header information

So-called header information can be set in an email action in a process. By setting these properties, messages can be more precisely defined and identified, e.g. with a specific priority or confidentiality level. Additionally, Intrexx users can define and set their own header properties, so that the information can be used to control their own workflows. Add an Email action to any process. Switch to the Content tab of the properties dialog.

In the Options section, click on Edit message header.

Click on Add message header.

Some properties are predefined. If one of those is selected in the Name column, then the corresponding predefined suggestions will appear in the Value column.

For some properties the value ${sender} can be specified. In this case, the sender of the email will be entered dynamically. Confirm the settings by clicking on OK. If an email is then sent, the properties can be found in the email client as well as in the detailed header information.

If, in addition to the predefined properties, you need to create your own custom properties, these can be entered directly in the dialog.

Dynamic values can also be applied here, in place of static values, for example, from the shared state of the processing context. The following prefixes are supported: In a precise example, e.g. within a Groovy action or filter condition, the code
def strValue = g_record["5A1D3EC0DB71BE6B6BC4F83BECCE85ACD22F82E6"].value
g_sharedState.customValue = strValue
is used to define a SharedState-Variable named customValue and fill it with a specified value, e.g. the value from a data field. In a subsequent Email action, the value that has been set in the SharedState can be read again. Here you use the prefix urn:sharedState: referred to above, followed by the name of the variable customValue defined in the Groovy action.

When using an entry from a system data group, the value will be setup as follows:
Enter the GUID of an application, in which the system data group has been setup, here, and the GUID of the data field from the system data group whose value is to be used, e.g.: