Notifications

5min

You can send Notifications using or programmatically in your solutions, see Notifications. Notifications can be configured to be sent to a single user, the entire organization, users of a specific solution, and even users of a specific in a specific solution.

In-app & push notifications
In-app & push notifications


Configuration options

Core structure



function

Define a function in the Functions folder of your solution. The function has input parameters such as the notification title, the notification text and requires a accessToken or personal access token (PAT) .



s will invoke the function for sending notifications either via submitting form values to the function or by using an execute-entity action for invoking the function.



Examples and code snippets

In the code examples below replace YOUR_ORG_ID with your actual Organization Id. You can find it in the Organization Settings section of the or use the expression [email protected].

Click here to go there directly: https://manage.jigx.com/settings/org-details

In this example we are using hidden form components (e.g. organizationId) to pass required parameters to the function. The emails field contains a comma-separated list of recipients. You could also use Expressions to create that comma-separated string dynamically at runtime.

Once you submitted the form, the recipients should receive both a push notification and an in-app notification. You can also check the delivery status of your notification in the Notifications section of the .

Add a function definition called send-notification.jigx to the functions folder of your solution and copy & paste the following snippet into it. Replace the {organizationId} in the url with your organization's Id.

Submit form to send notification
Submit form to send notification


See the code sample in GitHub.

send-notification
Send-submit-form.jigx


You can also send notifications using an execute-entity action if you want to have more control over what's being sent to the function.

In this example we are using state to access the two form fields title and text. All other function parameters are set in the execute-entity action. Note that you don't have to use form fields as you could also assign all function parameters in the action itself.

Notification sent with execute entity
Notification sent with execute entity

send-notification.jigx (function)
send-execute-entity.jigx


You can also target a specific with input parameters from your push notification. An example of this would be a notification about a new product promotion with the promotion detail as the target. When the user taps on the notification (either on the native push notification or the in-app notification), the app will navigate to the specific promotion

Target a jig with a notification
Target a jig with a notification

Push Notification
Push Notification

Target Jig
Target Jig


For this, you need an adjusted REST function definition (see 1), a Jig that invokes the REST function (see 2), and a target that will be displayed when the user taps on the notification (see 3).

Replace the {organizationId} in the url with your organization's Id.

See the code sample in GitHub.

1-send-notification-target-jig.jigx (function)
2-view-promotion-details.jigx (sending jig)
3-view-promotion-details.jigx (target jig)