Teams Message Action
You can use the "Teams Message Action," for example, in a project context to send messages to a Teams channel associated with the project. Event-based messages, for example, are useful in this context:
-
From production, when errors are reported, to a person or a channel
-
When an investment request is received—whether via a channel or from a person—with a link to the Intrexx record
-
From Sales, when a visit report is entered, to a channel
To use this process action, it must be preceded by a switch user action in the Microsoft Teams messaging action. Alternatively, the process can be triggered from the web by a logged-in user.
Create a Teams Message Action
You can find the Teams Messages action in Processes under "Items." It belongs to the "Promotions - Microsoft 365 and Teams" category. From there, it can be dragged and dropped into the desired location in the process chain and then configured. General information on creating process elements can be found here.
Once you've created the Teams message action on the workspace, double-click the item to open the Properties dialog box.
General
You can find all the information about the settings in this dialog box here.
Click "Next."
Message to one or more users
Depending on the selection made in this dialog, messages can be sent to one or more users or to a Microsoft Teams channel. Select the desired option and click "Next."
Message to one or more users: Recipients
Static Users
Enter the users' email addresses here exactly as they are stored in Entra ID (formerly Azure AD) as the "Principal User Name." Email addresses can be entered separated by commas or semicolons. Alternatively, you can enter one email address per line.
User from data field
This setting is available when the action has a data group context, for example, when a data group event handler has been defined as the event source. Here, you select a data field from the data group that contains the email addresses. The type specifies how the data is formatted for collecting email addresses (e.g., semicolon-separated, GENERIC (which extracts email addresses from free text according to RFC 5322), distribution list selection (pipe-separated list of organizational structure GUIDs), and double-pipe-separated.)
Users from a data group query
Here, a data field is selected from a published application that contains the data, just as in the "User from Data Field" setting.
Clicking "Filter" at 
opens a dialog box where you can create a filter to narrow down the data.
Here, too—just as with the "User from Data Field" setting—you must select the type of formatting.
System value
With this setting, email addresses are determined using a session variable, a request value, a variable in the processing context, or a system data field.
Clicking "Edit System Value" at 
opens a dialog box where you can define the system value.
Click "Next."
Message to one or more users: Content
The content of the message can come from four different sources.
Static value
You can easily enter your message here. If the message is to be sent as a card, a valid JSON format must be entered here. Otherwise, the dialog box cannot be closed.
Text from data field
This option is available when the action has a data group context. The message content will then be retrieved from the data field you select here.
Text from System Value
This option reads the message content from a system value.
Clicking "Edit System Value" at opens a dialog box where you can define the system value.
Generate from Velocity
Here, you can open the Velocity Editor to generate the message content using Velocity script.
Text Formatting
Plain text
With this setting, the message is sent as plain text without any formatting.
Send as a map (requires text in JSON format)
Specifies that the message will be sent as a card.
HTML
HTML in the text defined as the source is interpreted as HTML.
Message to One or More Users: Options
Jump to
If the message is to contain a link, it is defined here using the link target. Clicking "Edit Jump Target" at opens a dialog box where you can define the jump target.
Message to one or more users: Jump to
You can also find this dialog in the properties of the "Push Notification Action" and "Create Teams/Channel Action" process elements.
Portal Home Page
The portal's home page is loaded as the destination.
Page
Here, you can select an application page as a link destination.
Edit Parameters
Opens a dialog box where you can configure the parameters required by the embedded page.
Go to an existing record
This option is available when an input page is selected. The input page loads with the data from the current record.
Create a new record
This option is also available when an input page is selected. The input page loads blank. A new record can be entered.
Static URL
You can enter a static jump destination URL here.
URL from data field
Here, you can select a data field that contains the jump destination URL.
URL from System Value
This option allows you to use system values that provide a URL as a destination. The currently selected system value type is displayed here.
Edit System Value
Opens a dialog box where the system value can be defined.
Click "OK" to save your changes and close the dialog box.
Microsoft 365 Configuration
Here, you must select an existing configuration that uses the system user to send messages.
Messages to a Microsoft Teams channel: Channel selection
Select the Microsoft 365 configuration here. You can then select the desired team and channel. You can either select from the list of existing teams and channels or specify a team and channel directly from the processing context.
Messages to a Microsoft Teams channel: Content
You can find all the information about the settings in this dialog box here.
Messages to a Microsoft Teams Channel: Options
Jump to
If the message is to contain a link, it is defined here using the link target. Clicking "Edit Jump Target" at opens a dialog box where you can define the jump target.
Exception Handling
Exception handling can only be configured in the Properties dialog for process elements that have already been created. This setting determines whether the transaction should be canceled or continued if there is no recipient, no content, or no title (only for push notification actions). To do this, click "Configure Exception Handling" under " " for each one.
Cancel Transaction (Default)
Causes the entire process to be terminated if an error occurs—for example, if a data field relevant to shipping does not contain valid data.
Continue the transaction
The error is ignored. No message will be sent. The process continues with the next step.
More Information
Connector for Microsoft 365 and Teams