---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Map functions w/push actions

# Map functions with push actions on the actionable push notification {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Associate functions to the actions in your notification so the instance uses the
correct function for each action.

## Before you begin

Role required: admin

## Procedure

1. System MobileMobile Push NotificationsPush Notifications, and open the notification you created in previous steps.
2. In the Push Action Instances related list, click New.
3. In the Push action instance form, fill in the fields.  
   {#actionable-push-notification-4__table_b2g_ct1_zlb__entry__2}

   | Field | Description |
   |-|-|
   | Push Notification | Push notification associated with this push action instance. This is automatically filled in with your push notification. |
   | Application | Scoped application associated with this record. This is automatically filled in with the current application. |
   | Push Action | Push action from your push notification record. Select one of the available actions. |
   | Button | Function to associate with the push action. Select an action you created in previous steps. This action will trigger when a user uses the action listed in the Push Action field. |
   [Table 1. Push action instance form]

   {#actionable-push-notification-4__table_b2g_ct1_zlb}
4. **Optional:** Add a push parameter to your push action instance.  
   If your push action receives a value from your user, you need to configure a push parameter to pass this value to your record. For example, if you create a reject action that requires your user to enter a reason for the rejection, the action must have a parameter to pass that text value to your approval record.
   1. Verify that your push action requires a parameter.  
      In the push action instance form, click the preview icon (![Preview icon]()) next to the Push action field. If the push action has a value of <kbd class="ph userinput">Text Response</kbd> in the Response type field, you must create a push
      parameter.
   2. Find the button parameter by clicking the preview icon (![Preview icon]()) next to the Button field.
   3. In the function pop up click Open record to open the function form.  
   4. In the function form, note the parameter that appears in the UI Parameters related list at the bottom on the form.  
      You will need this value in later steps.
   5. Click the back button to return to the push action instance form.
   6. In the Push Parameter Values related list, click New.
   7. In the push parameter value form, select your parameter in the Parameter field.  
      This is the parameter you noted from the function form in step d.
   8. Click Submit to save your push parameter value.
   {#actionable-push-notification-4__substeps_crr_2vx_qmb}
5. In the push action instance form, click Submit.

## Example

This example notification uses accept-rejectwcomments-back in
the Category field. If you click the preview icon (![Preview icon]()), you can see that this category uses two actions:
Accept and Reject.  

In the push action instance shown here, the <kbd class="ph userinput">Approve</kbd> push
action is selected in the Push Action field, and the
<kbd class="ph userinput">Approve REQ /w comments</kbd> function is selected in the
Button field. The instance executes this function when a
user taps the Approve button in their notification.

*[\>]: and then