Tips & Tricks - Setting header information

Header information can be added to emails sent via an email action in a process. By setting these properties, messages can be made more specific and categorized, e.g. with a specific priority or confidentiality level. In addition, Intrexx users can define and set their own header properties in order to control their own workflows based on this information. Add an email action to any process. Switch to the "Content" tab of the properties dialog. Switch to the "Content" tab of the properties dialog.

In the "Options" section, click on "Edit message header" to configure the message headers.

Click on "Add message header".

Some properties are predefined. If one of these 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 your settings by clicking on "OK". If an email is subsequently sent, the properties are reflected in the email client as well as in the detailed header information.

In addition to the predefined properties, you can also create your own properties. these can be entered directly in the dialog by entering the property and value.

Dynamic values can also be applied instead of static values, for example from the sharedState. The following prefixes are supported:

  • urn:sharedState:

  • urn:request:

  • urn:session:

  • urn:user:

  • urn:systemDataGroup:

In a specific example within a Groovy action or filter condition,

def strValue = g_record["5A1D3EC0DB71BE6B6BC4F83BECCE85ACD22F82E6"].value
g_sharedState.customValue = strValue

can be used to define a shared state variable with the name "customValue", which will be filled with a specific value, such as the value from a data field. In a follow-on email action, the value set in the shared state can be read out again. For this, use the prefix named above: urn:sharedState: followed by the name of the variable defined in the Groovy action "customValue"

When using an entry from a system data group, the value is put together as follows:


Enter the application GUID here where the system data group was created, and the GUID of the data field from the system data group, the value of which should be used, e.g.: