Advanced Techniques - 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. 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 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 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 instead of static values, for example from the sharedState. The following prefixes are supported: In a more specific example, you could add the code
def strValue = g_record["5A1D3EC0DB71BE6B6BC4F83BECCE85ACD22F82E6"].value
g_sharedState.customValue = strValue
to a Groovy condition or filter condition to to define a SharedState variable called "customValue" and fill it with a specified value, e.g. the value from a data field. The value that has been defined in the SharedState can then be read in a subsequent email action. Use the prefix "urn:sharedState:" referred to above, followed by the name of the variable (e.g. "customValue") defined in the Groovy action.



If you want to add data from a system data group, the value can be defined as follows:
urn:systemDataGroup:APPLICATION_GUID:DATAFIELD_GUID
Enter the GUID of the application with the specific system data group and then the GUID of the data field whose value should be used, e.g.:
urn:systemDataGroup:D4D171F77327BB7D16B5D2B1EDF17BFFEBF1E11B:6F05E558E9BA291EE08DC9808EFF2BD36A80B3C2