Push Notification Campaign
This action allows you to send a push notification to users. A prerequisite for this is the use of the Intrexx Mobile app. In the action's properties, you can define the sender, recipient, content, and destination.
Create a Push Notification Campaign
You can find the push notification action in Processes under "Elements." It belongs to the "Promotions" 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 have created the push notification action on the workspace, double-click the element to open the Properties dialog box.
General
You can find all the information about this dialog here.
Click "Next."
Sender
Use Sender
If this setting is not enabled, no sender will be displayed in the mobile app. If this setting is enabled, you can specify a sender here.
Current User
Uses the logged-in user who triggers the push notification action.
Static User
Displays the path and name of the user selected from the "Users" module.
Select a user
Opens a dialog box from which a user can be selected.
User from data field
Here, you can select a data field that contains the sender's information. String data fields must contain user GUIDs, container GUIDs, or set GUIDs. If the field contains, for example, the GUID of a user group, all users who are members of that user group are treated as senders. Integer data fields must contain user IDs. The generated push notification contains the user's GUID and qualified login name (a combination of the login name and login domain).
User from System Value
This option allows you to use system values provided by a user. The currently selected system value type is displayed here.
Edit System Value
Opens a dialog box where the system value can be defined.
Click "Next."
Recipient
Static Users
Displays the user selected from the "Users" module.
Add a User Object
Opens a dialog box in which an object (e.g., user group) can be selected from the "Users" module.
Remove User Object
Removes the currently selected user object from the list.
User from data field
Here, you can select a data field that contains the recipient's information. String data fields must contain user GUIDs, container GUIDs, or set GUIDs. If the field contains, for example, the GUID of a user group, all users who are members of that user group are included as recipients. Integer data fields must contain user IDs. The generated push notification contains the user's GUID and qualified login name (a combination of the login name and login domain).
Users from a data group query
Application, Data Group, Data Field
Here, you can select a data field from an application and data group that contains the recipient data. String data fields must contain user GUIDs, container GUIDs, or set GUIDs. If the field contains, for example, the GUID of a user group, all users who are members of that user group are included as recipients. Integer data fields must contain user IDs.
Edit Filter
Opens a dialog box where the address list can be narrowed down in advance using filter criteria.
Current User
Uses the logged-in user who triggers the push notification action.
Supervisor / Deputy of the Current User
This setting retrieves the user GUID of the current user's supervisor or deputy.
System value
This option allows you to use system values. The system value must contain recipient data (user GUIDs, container GUIDs, set GUIDs, or user IDs).
Edit System Value
Opens a dialog box where the system value can be edited.
Recipients must have registered their mobile device with the portal using the mobile app. Push notifications are not sent to recipients who are not registered.
Click "Next."
Title
Static Text
You can enter a specific text here as the title of the push notification.
Text from data field
Here, you can select a data field that provides the title.
Text from System Value
This option allows system values to be used as the source for the title.
Edit System Value
Opens a dialog box where the system value can be edited.
Click "Next."
Contents
Static Text
You can enter a fixed text here as the content of the push notification.
Text from data field
Here, you can select a data field that provides the content.
Text from system value
This option allows system values to be used as the source of the content.
Edit System Value
Opens a dialog box where the system value can be edited.
Generate from Velocity
With this option, Velocity script can be used to generate the content.
Open the Velocity Editor
Opens the Velocity Editor.
Click "Next."
Options
Jump to
Jump to this section (mobile/desktop view)
With these settings, you can specify a jump destination that opens when a push notification is tapped in the mobile app. Depending on the layout of the portal being used on the mobile device, either the mobile or the desktop landing page is loaded.
Edit Jump Target for Mobile / Desktop View
Each one opens a dialog box where you can specify the jump destination.
Additional Settings
Message lifetime for delivery
This setting determines how long the message is retained if a recipient's mobile device is offline. Enter the lifetime duration here. You can select the desired unit (seconds, minutes, hours, days) accordingly. If you do not enter anything here, the maximum lifetime is 28 days.
Use the current transaction to send the message
This setting causes the message to be sent internally in an asynchronous manner. This option is set by default—if an error occurs, no message will be sent.
Test Mode ("Dry Run")
With this setting, you can test the request to the notification service without sending the message.
Click "OK" to complete the configuration.
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. To do this, click "Configure Exception Handling" under " " in each case.
Behavior When an Error Occurs
You can also find this dialog in the properties of the following process elements: " Create MS365 Group," " Plugin Feed Action," " Text Feed Action," "Create Group," and "Manage Group."
Depending on the context, you'll find a description of the scenario for which the procedure should be configured in the upper part of the dialog box.
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. If any messages are affected, they will not be sent. The process continues with the next step.